Make your own pet. It watches your agents and keeps the receipts.

Drop in a photo — Kobun draws your animal as a pixel pet, on your machine, no upload. Then it watches Claude Code and signs a record of every decision.

Get KobunMake a pet, free$19 launch · one-time · 14-day full trial
claude — ~/src/api
receipts
No receipts yet — nothing has happened.

The cat is clocking in…

01

Make it look like your animal.

Drop in a photo. Kobun reads its colours and markings and dresses a hand-drawn rig in them — locally, deterministically. No upload, no account, no AI service. Cut the network and it still works.

It stays out of the way once it's there: under 1% CPU idle, and frames only move when something is actually happening.

live · click a state

I sat on the keyboard once. It was load-bearing.

02

It watches Claude Code, deeply.

Every session reports in over hooks. One glance and you know who's working, who's done, and who's stuck waiting on you — and the approval lands in a bubble instead of a terminal you aren't looking at.

One agent, properly. Everything else is watched at the process level: running, or gone.

sentinel · three live sessions
claude…/src/apiwaiting approval · 8s
claude…/siteworking · 2m
claude…/infradone · 21m
03

It'll remember the thing you keep forgetting.

Reminders, Pomodoro, a pinned note, small questions. Bring your own key — and without one, everything except the chatter still works.

Every errand it runs writes a receipt, so “I set that for you” is checkable rather than trusted.

familiar · with a key
remind me to rotate the staging key at 4
Noted — I'll fetch you at 16:00. Receipt below.
reminder15:00:04reminder created: rotate the staging API key (16:00)8c21f0aa
receipts

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.

a day, in receipts (demo data)
status09:12:31claude: working in ~/src/api1fa2c9d4
approval09:14:02approved Bash: npm install express-rate-limitb8e07713
status09:21:47claude: done — 3 files changed40cc19be
reminder11:00:00reminder fired: stand up, stretch77d3a2f1
approval14:37:19denied Bash: rm -rf node_modules/.cachee12b90c5
anchor18:00:00anchor: chain head seq 214 cross-signed0a9f44d2

I write it down because you won't.

Everything on this page is the product running. None of it is a screenshot.

Including me. Hello.

pricing

Buy it once. It's yours.

No subscription, no seat math, no account. Kobun talks to the models with your API key, so the only recurring bill is the one you already have.

And paid means paid: a valid license keeps working offline, forever. The app never phones home to decide whether you deserve to use it.

launch price
$19 $24
one-time · 3 machines · yours forever
  • 14-day full trial — every feature, no card
  • Bring your own API key (BYOK)
  • All 1.x updates included
  • macOS · Windows · Linux

Checkout isn't connected in this preview build (no store configured).

Checkout and license delivery by Lemon Squeezy.

privacy

Nothing you do here leaves this machine. There's nowhere for it to go.

Everything on your disk

One SQLite file holds the receipts, reminders, and notes. There is no server side, because there is no server.

No telemetry

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 verification loop.

Your key stays home

Your API key lives in the OS keychain and goes only to the model provider you chose. It never touches us — we couldn't see it if we wanted to.

faq

Things you'd want to know before trusting it.

Which agents can it watch?

Claude Code, deeply — over its hooks API, including the approval relay. That is the one integration we go all the way on at launch. Any other agent is watched at the process level only: running, or gone. We would rather be excellent at one than shallow across five, and we would rather say so than imply more.

What does “bring your own key” mean?

The cat's own brain talks to a model with an API key you provide (an Anthropic key at launch). Without one, the watching, approvals, reminders, and receipts all still work — the cat just parks its chattier self.

What exactly is a receipt?

One row in a hash-chained, locally stored audit log — who did what, when. Rows the pet authors are signed with a keypair minted on your machine. The chain is re-verified every launch, so tampering or truncation shows up loudly.

What happens when I'm offline?

Everything except the model calls. Licensing is fail-open: once a license is validated, it stays valid with no network, indefinitely. Only a refund or chargeback revokes it.

How does the trial work?

14 days, every feature, no card. The trial clock is anchored in the same signed receipt chain the rest of the app uses — and if the clock looks tampered with, Kobun pauses politely instead of accusing anyone.

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.