Karmas Coder documentation
Learn how to install Karmas Coder, connect coding-agent runtimes, run durable tasks, verify results, and recover safely.
Karmas Coder is a free, local-first desktop workspace and control plane for coding agents developed and maintained by Arvind Codex (arvindcodex.in). It brings provider sessions, tasks, terminals, browser work, diffs, Git worktrees, handoffs, automations, and pull-request delivery into one application.
New in 0.9.2
Karmas Coder Beta installs alongside Stable with separate data and updates. On macOS, open Settings → General to install Beta or copy Stable data into it.
New in 0.9.0
Computer Use beta lets Karmas Coder work with Mac apps and browsers. It is macOS-only for now; Linux is coming soon. Project import brings local Codex and Claude Code conversations into your workspace. Provider guides cover Claude cache review and Artifacts and Codex question cards and banked resets.
Editing and browser work in 0.8.4
Read Workspace editor & diffs for autosave, conflict recovery, revision comparison, and partial diffs. Composer & attachments covers selection-to-new-chat and AppSnap window capture; Browser verification covers shared browser verification. Browser logins & sessions explains account storage, cookie import, and optional Safari setup.
What is Karmas Coder?
Karmas Coder is the workspace around coding-agent runtimes such as Claude Code, Codex, OpenCode, Cursor, Antigravity, Grok Build, Devin CLI, Pi, Oh My Pi, and Factory Droid. The provider still owns its account, models, tools, permissions, and service. Karmas Coder owns the durable task, working environment, transcript, review surfaces, and delivery workflow around that provider session.
What does Karmas Coder control?
- Projects and tasks: keep several repositories and durable conversations available without mixing their context.
- Provider runtimes: select supported coding agents, models, and provider-specific options from one interface.
- Development surfaces: use terminals, browser tabs, files, diffs, and Git tools beside the conversation.
- Git environments: work in the local checkout or isolate concurrent tasks in linked worktrees.
- Review and delivery: inspect changes, verify behavior, commit, push, and create pull requests.
- Orchestration: use provider handoffs, automations, Studio, Agent Gateway, and restricted External MCP access where appropriate.
Does Karmas Coder include model access?
No. Karmas Coder uses the provider runtimes, accounts, subscriptions, and API credentials already configured on your machine. Model availability and usage limits remain provider-owned.
Start with Installation and the Provider guides.
Does Karmas Coder upload code to its own cloud?
Karmas Coder stores its workspace data locally and does not require a Karmas Coder cloud account. The provider selected for a task still receives the prompts, file snippets, diffs, terminal output, or tool results needed for that provider session. Karmas Coder is the control surface; it is not a proxy for normal provider traffic.
See Privacy for the public data boundary.
How should I run my first task?
Use one clean Git repository, one provider you have already verified, and one bounded objective. Follow the transcript, inspect the complete diff, run the relevant checks independently, and commit only the changes you understand.
Use the Quickstart for the shortest path or Your first task for the complete walkthrough.
How do I run several agents safely?
Give each body of work one owner and use separate worktrees for concurrent writers. Keep objectives independently reviewable, preserve Git state before integration, and assign one integration owner.
Continue with Parallel agents and Worktrees.
Where do I go when something fails?
Start with the symptom-specific Troubleshooting hub. Preserve work before restarting or cleaning up, identify the failing layer, change one variable at a time, and collect the smallest useful diagnostic bundle.
Most pages describe stable behavior. Features available only on the active application main
branch are identified as preview behavior where that distinction matters.
Explore 1.0.0 Stable
Start with Inbox and Kanban, provider accounts, and terminal panels. The Beta guide explains which features require the separate Beta app and how its data stays isolated.
Latest Beta workflows
Karmas Coder 1.0.1-beta.2 adds multi-folder projects, message-content search in Organize & navigate, and independent right-dock terminals.
1.0.2 Beta workflows
Read the subagent guide, history and reload guide, and queue pause controls. Tasks is available in Stable 1.0.1; Hubs are available in Stable 1.0.2 and Beta.