The coding agent that does what it says.
A sovereign coding agent with capability parity across LLMs, self-improvement (skills, persona, memory) and mandatory design-system adherence. In the terminal, on Telegram, wherever you want — without locking your company to a single model vendor.
MIT · Python 3.11+ · v0.15-beta · 4.081 testes
The two pains that created Okami Agent
Unreliable harness: the agent says “I'll do it” and doesn't; when pushed, it says “hold on” and stalls. You lose the afternoon checking whether the work actually happened instead of reviewing the code.
Vendor lock-in: every provider has its own format, harness and account. Switching models means redoing the integration — and paying twice when one paid agent drives another paid agent.
What Okami Agent does
Same behavior on any LLM
Immutable runtime targets, one resolver and a transport registry. LiteLLM stays available as a compatibility adapter — not as the architecture. Switching models doesn't change what the agent can do.
Tool streaming with atomic history
Structured tool-call deltas, crash-safe resume and compaction that never separates a call from its result. History stays consistent even when the session dies mid-run.
Request-scoped cancellation
Total, TTFB and idle deadlines, cooperative abort and interruptible retry. After a terminal cancellation, no recovery work keeps running behind your back.
30+ built-in skills and self-improvement
The agent evolves through its own skills, persona and memory — and keeps mandatory adherence to the project's design system instead of inventing a new look on every task.
Model control straight from chat
Secure inline model picker, /providers command, persistent per-session selection, live heartbeat and generated media delivered in the chat itself.
Per-response cost footer
Every turn shows context, tokens and time. You know exactly what that response cost — instead of finding out at the end of the month.
Okami Agent specs
When to use Okami Agent
Small team with several AI subscriptions
You already pay for Claude, Codex and others. Okami Agent uses the subscription you already have, with behavior parity — instead of requiring a second API bill.
Project with a strict design system
Design-system adherence is mandatory, not a suggestion. The agent stops reinventing components and starts reusing what already exists in your repository.
Operating outside the editor
Fire and follow tasks from Telegram, with a model picker and heartbeat — useful when work arrives while you're away from the terminal.
Okami Agent FAQ
Do I need an API bill on top of my subscription?+
No. Okami Agent works with subscription-based auth (Codex/Claude via OAuth or CLI, local LMStudio, MiniMax/MiMo via Token Plan), with automatic fallback. Bringing your own API key is an option, not a requirement.
Is it production-ready?+
It's in public beta (v0.15-beta) with 4,081 tests passing. The command and config surface may still change before GA — before exposing it publicly, run `okami policy check --strict`.
How does it compare to running the provider CLI directly?+
The provider CLI gives you that provider. Okami Agent gives you consistent behavior across providers, with atomic history, deadline-based cancellation and its own skills — which an isolated CLI doesn't provide.
Want Okami Agent 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.