pickfit

BrowseDeveloper CLIs

apogee

Terminal AI coding agent that uses local LLMs or OpenAI-compatible APIs.

Tested on Linux

Use it

Linux x86_64

  1. Download prebuilt linux_amd64 archive and install to ~/.local/bin

    VERSION=$(curl -fsSL https://api.github.com/repos/airiclenz/apogee/releases/latest | sed -n 's/.*"tag_name": *"v\([^"]*\)".*/\1/p') && echo "VERSION=$VERSION" && PLATFORM=linux_amd64 && curl -fsSLO "https://github.com/airiclenz/apogee/releases/download/v$VERSION/apogee_${VERSION}_${PLATFORM}.tar.gz" && tar -xzf "apogee_${VERSION}_${PLATFORM}.tar.gz" && ls -la && mkdir -p ~/.local/bin && install -m 0755 "apogee_${VERSION}_${PLATFORM}/apogee" ~/.local/bin/apogee && ~/.local/bin/apogee --version

Check that it works

apogee --version

The output should contain “apogee version v0.29.0”.

First thing to try

mkdir -p ~/.apogee && printf 'servers:\n  - name: my-box\n    endpoint: http://127.0.0.1:1111\nserver: my-box\nupdate-check: false\n' > ~/.apogee/config.yaml && cat ~/.apogee/config.yaml
apogee probe

Run apogee probe first to check that it can reach your model.

What it does

  • Read code, edit files and run commands
    Not tested
  • Use local models or cloud APIs
    Not tested
  • Hand off work to sub-agents running in parallel
    Not tested
  • Add tools to the agent with MCP servers
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Windows and macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • read code and edit files via terminal agent
  • run commands, tests and git operations
  • delegate work to parallel sub-agents

How pickfit tested it

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

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version v0.29.0+4773.gcd926069e55f

Differences the test machine hit

  • README: go install github.com/airiclenz/apogee/cmd/apogee@latest and sudo install to /usr/local/bin/apogee
    In the test: used prebuilt linux_amd64 tarball from releases and installed to ~/.local/bin/apogee (no root, no Go toolchain)
  • README: apogee probe reports host/model/terminal without setup
    In the test: wrote minimal ~/.apogee/config.yaml with dummy server entry and update-check: false before probe would run

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.