pickfit

BrowseDeveloper CLIs

vincent

Local-first daemon plus TUI and CLI to run and supervise AI coding-agent tasks.

Tested on Linux

Use it

Linux x86_64

You need first

  • System packages: git
  1. download Linux amd64 release archive and install vincent to ~/.local/bin

    mkdir -p ~/.local/bin /tmp/vincent-dl && curl -fSL -o /tmp/vincent-dl/vincent.tar.gz https://github.com/lezli01/vincent/releases/download/v0.11.0/vincent_0.11.0_linux_amd64.tar.gz && tar -xzf /tmp/vincent-dl/vincent.tar.gz -C /tmp/vincent-dl && cp /tmp/vincent-dl/vincent ~/.local/bin/vincent && chmod +x ~/.local/bin/vincent && ~/.local/bin/vincent version
Where the README and reality differ
  • README: `vincent config get` as a plain example command
    What worked: run `vincent daemon start` first; `vincent config get` then prints the config with exit 0

Check that it works

vincent version

The output should contain “vincent version 0.11.0”.

First thing to try

vincent version

Start the background service with vincent daemon start, then check it with vincent daemon status.

What it does

  • Monitor and manage many agent tasks
    How to use it
    1. Start the daemon with vincent daemon start.
    2. Register a repository and add a task with vincent project add <repo path> and vincent task add --project 1 --workflow <workflow> --title "<your text>".
    3. List tasks with vincent task ls and view one with vincent task show <task id>.
    Tested
  • Write reusable workflows in validated YAML
    How to use it
    1. Write a workflow YAML file, for example in .vincent/workflows/ in your repository.
    2. Check it with vincent workflow validate <file>.
    Tested
  • Run Claude Code, Codex, or Cursor
    Not tested
  • Run tasks in isolated git worktrees
    Not shown working

How far pickfit got

Linux x86_64

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

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

Good for

  • monitor and manage many agent tasks from one central place
  • register local git repositories and author reusable workflows
  • run tasks each isolated in its own git worktree
  • start a chat with an agent in its own worktree and branch
  • inspect diffs and retry blocked steps

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.11.0 (commit babc995, built 2026-10-02T06:26:41Z)

Differences the test machine hit

  • README: go install github.com/lezli01/vincent/cmd/vincent@latest / mise use -g github:lezli01/vincent
    In the test: skipped go install (no Go toolchain in box, must not install one) and mise (mise binary not installed); downloaded the README Archive asset vincent_0.11.0_linux_amd64.tar.gz from GitHub releases and copied vincent to ~/.local/bin

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.