Kody augments your agent
It does not replace the assistant you already use. Connect Claude, ChatGPT, Cursor, or Codex, and it gains your keys, your saved code, and automations that keep running with your laptop closed.
connectsremembersactsKody never calls a model. It is your assistant's home — the memory, keys, code, and automations it keeps, no matter which agent you talk to.
Not sure what you'd use it for? Ask your agent with the discovery prompt— no account needed. Or see what you can't get elsewhere.
How it works
Add Kody to the assistant you already use through MCP. Two tools—search and execute—put a vast capability graph behind it.
01
Search
Discover packages, integrations, jobs, secrets, email, storage, and memories.
02
Execute
Run sandboxed code and explicit API calls with secrets kept server-side.
03
Build
Save reusable packages and schedule Worker-native jobs that run while your computer is off.
Three things you cannot get elsewhere
Kody also keeps your memory, keys, packages, scheduled jobs, a personal inbox, and durable storage. These three are the reasons it exists.
One-off agent work becomes permanent
Your agent explores against your real APIs, and the moment something works it saves as code that runs on a schedule with no model in the loop. Not an agent re-run on a timer—no tokens, no drift, no waiting on a model.
How packages and jobs workYour agent uses your keys without ever reading them
It writes whatever code the job needs, and still cannot see a credential. There is no capability that returns one. Your code references secrets by name and Kody substitutes them at the network boundary, only for hosts you approved.
There is no secret_get—check for yourselfEvery install is a fork you own
Install someone else’s automation in one click and it lands in your account as code you own, on your credentials. Open it, change it, schedule it, publish your version back. Nothing is locked in someone else’s runtime.
How community packages workCode runs in a sandbox. Secrets stay server-side and never enter prompts or your assistant's context. Every user is fully isolated.
Kody's source is open— read it, fork it, self-host it. Every claim above links to the code that proves it.