pickfit

BrowseDeveloper CLIs

Podiom

Local-first workspace to manage Claude Code and Codex agents, sessions, projects, and goals.

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.

  • npm:dompurify 3.4.16 DOMPurify SAFE_FOR_TEMPLATES bypass: split template expressions survive in attached shadow root content on DOM output modes (GHSA-cg2g-xh64-v4q7, critical, fixed in 3.4.17)
See 1 more

Linux x86_64

  1. Download installer script

    curl -fsSL https://github.com/Podiom/Podiom/releases/latest/download/install.sh -o /tmp/install.sh
  2. Install Podiom via script

    bash /tmp/install.sh --no-onboard --autostart no

Check that it works

podiom --help

The output should contain “Available Commands:”.

First thing to try

podiomd
podiom status

Start the background service with podiomd, then run podiom status to confirm it is running.

What it does

  • Give agents long-term goals to own
    How to use it
    1. Start the service with podiomd and create an agent with podiom agents create <agent> --provider claude.
    2. Get your API token with podiom token show.
    3. POST a goal with a title, description, success_criteria and lead_agent to http://127.0.0.1:8787/api/goals using the token as a Bearer header.
    Tested
  • Schedule recurring routines and timed work
    How to use it
    1. Start the service with podiomd and create an agent with podiom agents create <agent> --provider claude.
    2. Add a Markdown file in ~/.podiom/schedules/ with front matter for agent, cron, enabled and run_permission, followed by the prompt.
    3. Run podiom schedules list to see the routine and its next run time.
    Tested
  • Chat with named agents that keep their context
    Not shown working
  • Keep a full history of every session
    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

  • chat with named agents with durable history
  • hand an outcome to a lead agent to own over time
  • schedule recurring routines and timed work

How pickfit tested it

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

Linux x86_64

Its service answers requests

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version v0.1.384 (67c8736)

Differences the test machine hit

  • README: curl -fsSL .../install.sh | bash
    In the test: ran bash /tmp/install.sh --no-onboard --autostart no after downloading and reading it

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.