pickfit

BrowseLocal AI tools

Moose

Native Linux app for chatting with local Ollama models or optional cloud providers.

Use it

Before you install: known vulnerabilities

pickfit found 2 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:quinn-proto 0.11.14 Quinn: Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly (GHSA-4w2j-m93h-cj5j, high, fixed in 0.11.15)
See 1 more

Linux x86_64

  1. add flathub user remote

    flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
  2. install Moose flatpak as user

    flatpak install -y --user flathub io.github.moooossee.Moose

Open Moose from your applications menu, or run flatpak run io.github.moooossee.Moose in a terminal.

What it does

  • Chat with local or cloud AI models
    Not tested
  • Browse and download AI models
    Not tested
  • Chat with files attached
    Not tested
  • Search your document library for use in chats
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Opens to its setup screen
  3. 0 of 4 features work
  4. Works offline

Good for

  • Browse and download AI models without leaving the app
  • Chat with attached images, PDFs, text, Markdown or code files
  • Search document library and use documents in conversations
  • Edit messages, retry answers or branch conversations
  • Use managed Ollama, existing Ollama or cloud providers

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

It opens to its first-run screen

  • Replayed from scratch
  • Checked on 1 Nov 2026
  • Version 0.7.5

When pickfit opened it, its first-run (setup) screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: flatpak install flathub io.github.moooossee.Moose
    In the test: first add flathub as user remote and install with --user flag (no root): flatpak remote-add --user --if-not-exists flathub ... && flatpak install -y --user flathub io.github.moooossee.Moose
  • README: Attach images, PDFs, text files / Keep a document library
    In the test: Flatpak file chooser Import button never opened a dialog here (no desktop portal), so file-based features cannot be exercised

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.