pickfit

BrowseLocal AI tools

OpenJet

Offline coding agent that sets up and runs local models on your own GPU.

Tested on Linux

Use it

Linux x86_64

You need first

  • System packages: CUDA toolkit
  • A GPU is optional
  1. Install open-jet via uv tool

    uv tool install open-jet

Check that it works

openjet --help 2>&1

The output should contain “offline agentic terminal UI”.

First thing to try

openjet --status 2>&1

Run openjet --status first to check your setup.

What it does

  • Run a coding agent in the terminal
    Not shown working
  • Run four coding agents at once on one GPU
    Not tested
  • Plan with a frontier model and code with a local one
    Not tested
  • Embed a local model in a Python app
    Not shown working

How far pickfit got

Linux x86_64

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

Good for

  • run a coding agent in the terminal
  • run 4 coding agents at once on one GPU
  • have a frontier model plan while local model codes
  • ship a local model inside a Python app
  • read repo, edit files and run tests locally

An alternative to llama.cpp, Ollama and LM Studio.

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 0.5.4

Differences the test machine hit

  • README: pipx install open-jet / pip install open-jet
    In the test: uv tool install open-jet isolates the package; system python cannot import openjet
  • README: openjet setup downloads a model and configures the agent
    In the test: on this small CPU-only box setup --dry-run exits 1 with 'No selected model fits available memory with runtime headroom'

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.