Project-aware routing
Reads CLAUDE.md, AGENTS.md, .mcp.json, slash commands, subagents, skills, hooks. Routes each turn to whichever CLI fits.
Get more out of your coding-agent subscriptions
The local app does the work. Your CLIs use their own auth. Your project's config decides the routing.
Klimand skill library
The orchestrator has its own playbook — 12 base skills for decomposition, routing, prompt composition, evaluation. Override per project under .klimand/skills/.
Goal mode
State an outcome; Klimand decomposes it into sub-tasks, drives them across Claude and Codex, evaluates each one by verification check, and shows live progress in the tracker.
BYOK · Apache-2.0
Bring your own OpenAI / Anthropic key for the orchestrator. Claude Code and Codex use their own auth. Source available on GitHub.
Goal mode
State an outcome. Klimand turns it into a plan, runs each step against your real project, and decides what to do next.
Decompose
The orchestrator turns your outcome into an ordered list of verifiable sub-tasks, with a single CLI per task and explicit dependencies.
Dispatch
Each sub-task runs against your real project — same auth, same CLAUDE.md and AGENTS.md rules as a chat turn.
Evaluate
A verification check decides pass / partial / fail. Pass moves on; partial retries with feedback; fail escalates and pauses the run.
Pro
Klimand stays free and open source. Pro adds the convenience features solo devs want off their plate — for the price of a coffee subscription.
Hosted scheduling
Cron-fired runs that don't depend on your laptop being open.
GitHub-backed sync
Your own private repo holds state. Cross-device works without us hosting your data.
Push notifications
Web Push when a run finishes, needs approval, or hits a budget limit.
Hosted LLM gateway
No API key to paste. Capped monthly budget for the orchestrator's routing calls.
Cancel any time from the Stripe portal link in your license email. BYOK still works on the free tier — Pro is for the hosted conveniences.
Questions
Why do I need an OpenAI key?
Klimand routes locally. Your keys, your usage, your control — Klimand never proxies your traffic on the free tier. The router model (gpt-5.4-mini) is the only thing that calls OpenAI; Claude Code and Codex use their own auth.
What's the difference between free and Pro?
Free is the full local app — multi-CLI routing, threads, scheduling on your machine, GitHub/Linear ingest. Pro adds the hosted conveniences: schedules that run on Cloudflare while your laptop's closed, Web Push notifications when runs finish, GitHub-backed sync across devices, and a hosted LLM gateway so you can skip pasting an OpenAI key.
Can I cancel?
Yes. Every license email includes a Stripe Customer Portal link — click it to cancel, switch plans, or update your card. Cancellations take effect at the end of the current period.
Do you store my prompts?
No. The only data we keep is routing metadata: which CLI handled which step, duration, and the per-license token counter for the hosted LLM gateway. Prompt content stays on your machine; the orchestrator model gets it but doesn't persist it.
Is the source code open?
Yes. The local app is Apache-2.0 on GitHub. The hosted Pro infrastructure (Worker, license issuance, Stripe glue) lives in a separate repo and is not open source — that's the part Klimand sells.
How it compares
| If you currently use… | Klimand adds |
|---|---|
claude CLI alone |
Multi-CLI routing, thread history, project view, scheduling |
codex CLI alone |
Same — plus Claude Code as a peer when the task calls for it |
| Cursor / Cline / aider | A CLI-agnostic orchestrator that lives outside your editor |