Your plan is a star-map.
Your agents fly it.
Chart a map of the work, then drive it to completion. Pick tickets off the frontier and run agents with the necessary context fully loaded.
Visible plan, actionable tasks.
Work with an agent on your plan, written as markdown. chartr renders the star-map automatically. Get a bird's-eye view of the frontier of your work.
-
01
chart — the plan draws itself
Plan your work with the included skills. It interviews you, writes the map, and the stars appear as the files land.
-
02
spawn — the frontier is the runnable work
Every ticket with no blockers are on the frontier. Click spawn, and a session opens with full instructions and context already loaded.
-
03
resolve — answers unblock the map
A ticket resolves when its answer lands in the file. The star turns; whatever it blocked joins the frontier.
Never brief an agent again.
Pick a ticket and chartr provides the complete brief: the plan, the questions, and every decision it rests on. The session spawns with all of it loaded.
- the mapthe plan this ticket belongs to
- the ticketthe one question it has to answer
- the answers behind iteach decision it depends on, verbatim
- the chosen skillgrill, research, prototype, implement, and more
It knows where the work sits, what it is here to settle, and what has already been decided.
zero re-explaining or catching up.
built from your files on each spawn · no drift, the map stays the source of truth
Your agents, not chartr's.
chartr ships no models and no agent CLIs. It drives the ones you already pay for.
Register your agents
If it's in PATH, you can run it. Multiple entries
supported. Control how your agents are launched with arguments and
environment variables.
Right brain for the job
Grill a spec with one model, implement the ticket with another. The agent is your call, per spawn.
Nothing your agents can't do
Sessions open in each agent's own TUI — not a rebuilt chat view. Real processes, real PTYs, your keybindings, your themes.
Fully local and hackable. No lock-in.
chartr writes the plan and skills into your repo in plain Markdown. Hackable by design, you may edit or extend chartr to fit your workflow. There is no such thing as "ejecting from chartr" - just stop using it.
One markdown file per ticket. Read, edit or grep it with no chartr in sight.
Plain SKILL.md files. Your copy shadows the shipped one, per repo or per machine.
Claim and answer commits, written in ordinary git. Never an amend, a rebase or a push.
Built on a proven workflow.
The maps chartr drives are wayfinder maps — plan by interview, break the work into tickets with blocking edges, resolve it one question at a time. The method comes from mattpocock/skills; chartr gives the workflow a cockpit.
Download for your platform.
Linux Desktop app and Binary
AppImage on x86_64 or arm64, or unpack the tar archive.