One workspace for all your AI CLIs.
A local-first desktop cockpit for the coding CLIs you already subscribe to. Folder-bound projects, native session per provider, chat, email, calendar, Kanban, usage analytics and durable memory — without asking for a second API bill or sending your code through an intermediary cloud.
1.0.1-beta · Electron · Local-first · 8 runtimes
Five open terminals is not a workflow
Developers already paying for several AI subscriptions shouldn't need to keep five terminals and desktop apps open — or pay a second API bill — just to use the right model for each job.
OkamiCode provides one visual workspace around the CLIs and subscriptions already on your machine. Each project stays attached to its folder, each provider keeps its native session, and switching models doesn't silently make one paid agent drive another.
What OkamiCode does
Folder-bound projects
Persistent provider lanes with native session continuity, runtime and model selection right in the composer, plus integrated Git, diff viewer, file explorer, terminal and browser preview.
No access granted silently
Explicit permission modes: OkamiCode does not silently grant an agent broader access. Approvals, errors, timing and token telemetry are rendered as structured output.
Context that survives provider changes
A shared conversation history, explicit task-state handoff and deterministic compaction keep relevant context available without replaying the whole transcript to every model.
Subscription economics, no fabricated zeros
Native quota windows when the provider exposes reliable data, equivalent-cost estimates from OpenRouter price metadata and a subscription-versus-API comparison — with source, freshness and coverage indicators.
Encrypted local memory, no upload
Encrypted local SQLite with FTS5 full-text search, explicit read-only indexing of selected Markdown/Obsidian folders, with provenance and sensitive-line redaction. The indexed vault is not uploaded to a hosted service.
Email, calendar and Kanban in one place
Multiple IMAP/SMTP accounts plus Gmail OAuth, day/week/month views, and a Kanban where delegated tasks stay attached to their source conversation and wake the right lane when state changes.
OkamiCode specs
When to use OkamiCode
If you subscribe to three or more AIs
Use each subscription through the cockpit, with native sessions preserved, instead of switching terminals and losing the thread of context on every change.
Code that can't leave the machine
Being local-first, the cockpit doesn't put an intermediary cloud between you and the provider you already use — and indexed memory stays encrypted on your disk.
Work that arrives by email and task
Turn an email into a delegated task that already carries objective, instructions, source context, workspace, provider and activation policy.
OkamiCode FAQ
Does OkamiCode install the CLIs for me?+
No. You install each provider CLI separately and sign in through its official flow. In Settings, OkamiCode verifies which binary, version and capabilities were detected on the machine.
What happens if I remove a CLI?+
Removing an executable marks that runtime unavailable — without deleting the project, task, conversation, worktree, database or native-session reference.
Are the cost figures exact?+
They're estimates, not invoices. When a provider exposes no native token counter, the data stays unavailable — OkamiCode never fabricates zero usage to fill the screen.
Want OkamiCode running in your context?
The product is open and you can run it yourself. Rolling it out in your environment, with integration and a documented hand-off, is the consulting.