Cron
Shipping digest
Yesterday’s releases and new public repos, mailed only when the list is not empty.
The Home Your Agents Share
For all the agents you use today,
and the ones you'll use tomorrow
- Zed
- Cursor
- Codex
- Grok
- Devin
- Grok Bot
- Claude Code
- ChatGPT
232,579code runsSandboxed executes
Not sure yet? Ask the agent you already use whether Kody would help. No account necessary.
Leave Ogygia
Calypso keeps a lovely guest. She does not send you home.
Claude, ChatGPT, Cursor — each one is a beautiful island. The work stays in that chat, and tomorrow's agent cannot find the door.
Nothing new
to learn
Kody isn't another assistant to talk to. It plugs into the agent you already use, so the same conversation you're having today can now reach your real accounts.
Because your agent does the thinking, Kody gets better every time your agent does.
From ad hoc prompts to durable software
Stop burning your tokens on the same thing over and over again. Turn any process into durable software you can trigger on a schedule, notification, or anything else without expensive inference.
For example
Webhook
Issue triage
A new issue hits the webhook and your triage package kicks off a cloud agent. No manual trigger.
Invoke
Livestream archive
A Worker posts to the invoke URL. The export locks the VOD and files it. No model in the loop.
Ask once. Save it. Trigger it.
Kody has the primitives for your agent to build you pretty much anything. What will you build?
Watch some example conversations
Choose three agents you use:
I use for daily coding, for phone chat, and sometimes for coding too.
Example conversation with your agents and KodyExample conversation
You start on the computer with OpenCode.
Ask once
What did my favorite bot ship recently on GitHub?
What early builders say
A few notes from people already putting Kody to work with the agents they use every day.
The agent reasons.
Kody keeps it honest.
Your agent does the thinking. Kody holds the result so it does not have to think it again.
- Ask again tomorrow
- A saved export. No model in the loop.
- A key in chat or a .env
- A secret the agent never sees.
- Re-run the agent on a timer
- A job that runs while you are offline.
- Context stuck in one host
- Memories that follow the account.
Your own git and npm.
Kody gives you a personal software ecosystem. Your agent creates repositories and publishes packages, all in your own isolated environment. You can also publish your package to the community to allow others to fork and you can even use public packages on npm as well!
Then your agents can use your packages to streamline ad hoc work or you can trigger a package to execute in response to a webhook, cron, authenticated HTTP call, or even a Kody-hosted application.
Bring your own keys
Keys the agent never sees. You create the connection yourself, with your agent walking you through it: your app, your scopes, revocable anytime. Secrets never enter the prompt (as opposed to the .env file your agent happily reads).
Need your own scopes, or a provider we don't host? Your agent registers the app with you. No shared app sits between you and your accounts.
It already speaks your stack
Public packages cover the tools you live in. Browse what other people built, fork it with your agent, and make it yours.
- …and one thermostat
Check out Kody's Source on GitHub
Kody's source is open — read it, fork it, self-host it.
Make it permanent
Invite-only while we grow the eucalyptus. Join the waiting list, or jump the queue with a code.