Everything that Matt said in this video is a good tip and https://t.co/lQ46MvjDGy will help you do this in a way that doesn’t lock you into any one agent ecosystem.

Your agents’ cloud

Source: https://kody.codes/ Keep your agent. Kody is what it plugs into.

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.

Primitivesfor your agents

• MemoryTeam context every agent can find.
• PackagesTools your whole team can run.
• TriggersWorkflows that run with no chat open.
• CredentialsConnect once. Every agent can use it.
• AppsA place your team opens to get work done.

Explore all features

What Kodyisandis not

• Not an agent. Kody does not reason, chat, or decide. Your agent does the thinking. Kody keeps what it needs between conversations.
• Not a chat app. There is no Kody chat window to learn. Your team keeps working in the agents they already use.
• Not tied to one agent. Cursor, Claude, ChatGPT, Codex, or any agent that speaks MCP. They all reach the same account.
• Kody is the shared layer behind them. The shared credentials, tools, and workflows behind every agent your team uses.

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

• Cursor
• Cue
• Claude Code
• Gemini
• Amp
• OpenCode
• ChatGPT
• Grok Bot

Choose three agents you use:

I usefor daily coding,for phone chat, and sometimesfor coding too.

Example conversation with your agents and KodyExample conversation

You start on the computer withCopilot.

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!

Before Kody, every new agent meant rebuilding the same setup. Instructions, memory, MCP servers, and skills stayed scattered, and something always got left behind. Now I connect one MCP, bring my packages with me, and say “Hey Kody…” wherever I’m working. Portability plus a feedback loop that shipped three of my bug reports in under an hour.

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 team’s owngitandnpm.

One workspace your whole team shares: repos any teammate’s agent can build in, packages the team publishes once, and triggers that run them for everyone.

1. Repos ### Team git Shared repos your agents write.
2. Registry ### Team npm Packages anyone can run.
3. Share ### Community Fork public, publish yours.

• Webhook
• Cron
• HTTP
• App

Watch SomeDemos

## Invisiblesoftware

People want problems solved, not another app. Kody stays out of sight, behind the agents your team already uses.

What we believe

Connect your agent

MEGA (@megadevhq): “look for opportunities for passing data to your agent that you’ve not explored yet” - @mattpocockuk

grab a coffee and spend an hour with Matt and @joelhooks: