Your coding agent just got a face.
When Claude Code wants to run something, your pet shows it in a speech bubble. Click Approve or Deny and the terminal gets your answer. Anything else on your Mac can talk through it with 1 command — and every action gets a signed receipt.
14-day free trial, no card · $19 launch price, one-time · macOS today, Windows and Linux next
0 accounts · 0 API keys · 0 model calls · any avatar · everything on your machine
The pet is clocking in…
Watch. Approve. Receipt.
It watches.
Kobun connects to Claude Code over its hooks — one click, with a timestamped backup of your settings and a byte-identical revert. A glance at the pet says who's working, who's done, who's stuck waiting on you.
It fetches you.
Permission prompts stop dying in terminals you aren't looking at. The ask lands in the pet's bubble; you click Approve or Deny; the terminal continues. The pet can never answer for you — silence never means yes.
It writes it down.
Every decision and every inbound event becomes a signed, hash-chained receipt in a local SQLite file. kobun receipts verify re-checks the chain whenever you doubt it.
I sat on the keyboard once. It was load-bearing.
Upload anything. That's your pet now.
Your cat, your dog, your face, a potato — whatever you drop in becomes the avatar, styled four ways, entirely on your device. No upload, no account, no lock-in: the old-school pixel factory is still right there if chunky is your thing.
Plug anything into it.
Claude Code is built in. Everything else comes through the open door: a local socket, a one-line CLI, and a standard MCP server — so agents get the pet as a tool, and your shell scripts get a human in the loop.
Claude Code
Approvals + status, built in. Pet tools over MCP with one line.
$ claude mcp add kobun -- kobun mcp
Any script
One line puts you in the loop. Exits 0 yes · 1 no · 2 timeout · 3 not running.
if kobun ask "Deploy to prod?"; then …
Any MCP client
A standard stdio server. The full connectors wall — verified badges and all — lives on its own page.
See the wall →Ask the cat what happened.
Every decision Kobun touches — an approval you clicked, a reminder it fired, a status it saw — lands as one entry in a hash-chained audit log, and pet-authored actions are cryptographically signed. Not a text file. A chain.
Edit a row and the chain breaks loudly at launch. Delete one and the gap shows. The receipts are also the trial clock's anchor — the trust story and the anti-tamper are the same mechanism.
Export is one click, verification runs on every launch, and it all lives in a single SQLite file on your disk.
I write it down because you won't.
Buy it once. It's yours.
No subscription, no seat math, no account — and in v0.1, no API key to bring. Download it, and the pet is working within the minute.
Paid means paid: a valid license keeps working offline, forever. The app never phones home to decide whether you deserve to use it.
- 14-day free trial — every feature, no card
- Claude Code approvals + the open door
- Avatar studio + the classic pixel factory
- Signed receipts, verify + export
Checkout and license delivery by Lemon Squeezy.
Nothing you do here leaves this machine.
Everything on your disk
One SQLite file holds the receipts and reminders. There is no server side, because there is no server.
No telemetry in the app
Kobun sends no analytics, no crash reports, no usage pings. Nothing to opt out of.
No account
A license key from checkout is the whole relationship. No sign-up, no email loop.
No API key
v0.1 makes no model calls at all. Nothing to configure, nothing to leak, no usage bill riding along.
Everything on this page that looks like the product is the product's code, running in your browser.
Including me. Hello.
Things you'd want to know before trusting it.
Which agents can it watch?
Claude Code, deeply — hooks, live session status, and the approval relay, connected from one click with a timestamped backup and byte-identical revert. Codex CLI can report “done” through its notify hook (Codex doesn't expose approvals externally). Everything else talks through the open door: kobun say, kobun state, kobun ask, or MCP. See /integrations.
Can my avatar really be anything?
In the studio, yes — whatever image you drop in becomes the pet, styled on your device, downloadable as a PNG. The desktop overlay ships with the classic pixel pet today; bring-your-own avatar in the app is in flight, and we'd rather tell you that than pretend.
Do I need an API key?
No. v0.1 makes no model calls. There is no key to configure and no usage bill. If a future version adds model-powered features, they'll be bring-your-own-key and optional.
What exactly is a receipt?
One row in a hash-chained, locally stored audit log — who did what, when — signed with a keypair minted on your machine. The chain is re-verified every launch, and kobun receipts verify checks it on demand; kobun receipts export gives you the whole log as JSON.
What happens when I'm offline?
Everything. v0.1 has no network features to lose. Licensing is fail-open: once validated, a license stays valid with no network, indefinitely. Only a refund or chargeback revokes it.
Can an agent approve its own commands?
No. Approval decisions come only from a human click on the bubble, every failure path falls back to asking in your terminal, and each decision writes a signed receipt. Silence never means yes.
Is any of this open source?
Kobun is built on block/buzz (Apache-2.0), vendored at a pinned commit with change notices; the required LICENSE and NOTICE ship in the app. Kobun itself is a commercial product.