I have thoughts on the recent ai bot craze:

• Grok Bot
• OpenAI Dot
• Muse
• OpenMuse
• Cue
• Fo
• Instinct
• Gemini Spark
• Claude (agent mode)
• Microsoft Copilot Autopilot / Scout

They’re cool. It’s like hiring an employee, and firing them will be likewise painful unless you set yourself up right.

Each one of these products (and the others inevitably on their way) are going to do their best to make theirs the winner. But the fact is that they will continue to leap frog each other in capabilities. Not to mention some will be locked down to specific models.

There will be plenty of reasons you want to fire one and hire another. Or even hire multiple of them. But the thing is, they all want to drive their claws so deep into the flesh of your business (to be useful of course), that it will be a huge chore to get rid of them.

The integrations, automations, memories, secret tokens, etc etc etc. All of these will be locked into the assistant and they are not incentivized to make it easy for you to transfer these things to your “new hire.”

In fact, they’re incentivized to do the opposite. To become so core to the way you do business that you could never replace them.

This is why I think now more than ever http://kody.codes is filling in a critical gap. Instead of your agent putting everything inside its own home for the work it does for you, connect it to Kody and put it there. Then when you hire another agent, it can work off the same platform.

I think a lot of people are going to feel this pain in the coming months. When they do, Kody will be ready!

Don’t start over with every agent

Source: https://kody.codes/

You shouldn’t have to start over inevery agent.

Kody is thesoftware platformyour agents share

One home for packages, secrets, memory, and jobs, so what you build in Cursor still runs in Claude.

Without Kody

• Re-teach the agent each session
• Re-wire secrets per host
• Rebuild the same automation when you change agents

With Kody

• Memory and packages live in one home
• Secrets stay usable without landing in the prompt
• Trigger the same package from cron, webhook, email, or any connected agent

Ask once. Save it. Trigger it.

Kody gives your agents a shared set of primitives.

A lantern holding six glowing orbs, one for each Kody primitive.- Facts and context your agents can search later, across hosts. You stop re-explaining the same project every session.

• Keys and tokens the model never sees. Your agent can use a connection without reading the credential.
• Durable software you own. An agent writes it once; any connected agent can run it.
• Subscriptions, emails, webhooks, and schedules that wake packages you own — no chat left open.
• Signed-in connections to the tools you already use (GitHub, Discord, Google, and more), reusable from any agent.
• A hosted page a package serves, so the work is something you open instead of another turn in chat.

Want the full picture?What is Kody?

Not another chat. Not another gateway.

• Skills files and copy-paste. A skill in one agent stays stuck there. On Kody it becomes a package you run from Cursor, Claude, Codex, or ChatGPT.
• Multi-model tabs and routers. Switching models is not the same as keeping the work. Kody holds the memory, secrets, and packages those models call.
• MCP gateways. Great at connecting tools. Kody is where the useful work becomes software you own, schedule, and reuse.

From ad hoc prompts todurable software

Stop re-paying for the same answer. Save the process, then trigger itwithout expensive inference.

1. Today ### Ad hoc prompt Same question. More tokens.
2. Save it ### A package Durable software you own.
3. Trigger it ### No inference Cron, webhook, email, or event.

• CronFlake Hunter
• WebhookSentry Issues
• EmailAgent inbox
• EventPurchase thanks

Ask once.Save it.Trigger it.

A lantern of six glowing orbs, one for each primitive, with the agents it plugs into floating around it.A lantern holding six glowing orbs, one for each Kody primitive.

• Copilot
• ChatGPT
• Gemini
• Goose
• OpenClaw
• Grok
• Claude Code
• Grok Bot

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 withZed.

Ask once

You> What did my favorite bot ship recently on GitHub?

Read the walkthrough

What early builders say

A few notes from people already putting Kody to work with the agents they use every day.

Between my organization and myself we pay for six accounts over four providers. I don’t want personal tokens on work harnesses or work tokens on personal devices. Kody funnels everything into one secure MCP I manage myself. The interoperability is the real magic.

Kody gives our agents durable and credentialed access to infrastructure. Agents own deployment automation, while Kody owns the secure execution layer. In contested environments, that split keeps us moving when downtime isn’t an option.

Kody transformed how I work. Railway health checks land in Discord, a personal task list replaced the Notion notes I always lost, and everything I need lives in one place.

Kody rocks. Been a user for several hours now and will convert to paid.

For me, Kody is unbeatable. Being able to write custom pages from my phone using Claude (or any LLM) is crazy. I recently made a simple API wrapper for a product I’m working on that exposes a Scalar /api/docs page in about two minutes. Now I can just ask Claude “How many users logged in?” or “Reset user’s password.” It’s awesome!

Kody gives my agents one entry point with all my context and tools behind it. I’ve got into the habit of saying hey kody, so whatever agent I’m in knows to reach for it right away. It’s changed how I work with agents day to day.

Kody feels like the missing layer between my coding agents and the real systems I need them to operate. My agents still do the thinking and build the software, but Kody gives that work a durable home that isn’t tied to any one agent or tool.

Kody means peace of mind for me when working with agents. All of my tools, whether through MCP or a package I created on the fly, and my skills are always with me, no matter what agent harness I use.

Your owngitandnpm.

A personal software ecosystem: isolated repos, packages you publish, then trigger what you save.

1. Repos ### Your git Isolated, agent-written.
2. Registry ### Your npm Packages you can run.
3. Share ### Community Fork public, publish yours.

• Webhook
• Cron
• HTTP
• App

Watch SomeDemos

## Give your services ahome