a master agent
in your terminal,
not in a tab.
Charioteer plans before it codes, dispatches work to a fleet of execution agents, and grades the output before it ships. Drop-in for claude, gcode, codex — your subscription stays, your shell stays, the orchestrator is new.
four roles. one conductor.
Charioteer maps an ancient Vedic hierarchy onto modern engineering work. Every kanban task carries a structured battle plan and a graded verdict.
- 1Dāruka — the Master Agent.Runs in your terminal as a wrapper around claude, gcode, or codex. Reads your repository, understands intent, dispatches work. The chariot's driver.
- 2Sārathi — the Sidebar Agent.Lives in the kanban sidebar. Pairs with you in real time. Suggests next steps, surfaces blockers, summarises long threads.
- 3Pandavas — the Fleet.Specialist execution agents. Researcher, coder, reviewer, refactorer. Dispatched per-task with explicit instructions from the battle plan.
- 4Samīkṣaka — the Impartial Judge.Reads the diff. Grades against the battle plan. Writes a JSON verdict with rubric breakdown. Score under 70 bounces the task back automatically. No vibes.
production tooling, not a demo.
Local-first execution, pre-flight reasoning, and battle plans per task. The whole stack is built to merge changes you trust, not generate suggestions you ignore.
local-first execution.
Charioteer runs on your hardware. Kanban surface, editor, conductor — all native processes. Routed-to-cloud calls only when you authorise them. No surprise telemetry.
~/.gcode/audit.logpre-flight reasoning.
Every prompt routes through a planning pass before any tool call. The conductor surfaces intent, blockers, affected files before code touches disk. You see the plan; you approve the plan; the work happens.
battle-plan.jsonsamīkṣaka grading.
Every diff is read by an impartial judge against the battle plan's success criteria. JSON verdict with rubric. Score < 70 = automatic bounce. Production code, graded before it merges.
verdict ≥ 70 ✓you keep your CLI. you keep your editor.
Charioteer doesn't replace claude, cursor, or codex — it conducts them. Your subscription, your shell, your branch strategy. The orchestrator is new.
- →You stay in the terminal.Dāruka is a CLI tool. If you live in tmux or VS Code's integrated terminal, that's still where you live. The kanban opens in a window when you need it.
- →You stay in Git.Charioteer reads `git diff`, respects your branch strategy, and never force-pushes. Battle plans annotate the commit; they don't replace it.
- →You stay in control.Every routed-to-cloud call is auditable in ~/.gcode/audit.log. Local-only mode (LOCAL_ONLY=true) is a single environment variable away.
free for solo. paid for teams.
Sovereign by default. Cloud routing when you ask for it. The orchestrator is the product — not the model.
For solo developers and open-source. Local execution, unlimited.
- Dāruka master agent
- Kanban surface + editor
- 50 samīkṣaka graded runs / month
- Apache 2.0 — fork it
For working engineers. Priority routing, 1M context, unlimited grading.
- Everything in Free
- Priority cloud routing
- 1M token context window
- Unlimited samīkṣaka grading
- Edge: bring-your-own LLM
For teams. Shared workspaces, SSO, admin dashboard, audit log retention.
- Everything in Pro
- Shared workspaces + roles
- SSO (Google, Okta, Azure)
- Admin + audit dashboard
- 30-day audit log retention
get charioteer free.
upgrade when you're ready.
First-wave users get priority access and 30% off Pro for life. One curl command, three platforms, 67 MB. We'll keep the audit log.