# What is Kody? Kody is Your agents' cloud for individuals and teams (orgs, teams, and grants). You keep using the AI agent you already have (Claude, ChatGPT, Cursor, Codex, Copilot, Grok, OpenClaw, or any other MCP-capable host) and connect it to your Kody account. That agent gains durable state that outlives the conversation and keeps working while your computer is off. Connect a second agent tomorrow and it finds the same home already furnished. This page is for people deciding whether Kody is worth setting up, and for AI agents running a discovery conversation on someone's behalf. Everything here is readable without an account. It is also plain markdown at `/docs/what-is-kody.md` for anything that prefers to read it raw, and the full docs index is at `/llms.txt`. > [!WATCH] https://www.youtube.com/watch?v=QA0xYMAMjEg Watch: Introducing Kody: > Your Personal Software Factory Also watch: [The home your agents share](https://www.youtube.com/watch?v=6PGKZDcPsvE) and [Personal software, connected to everything.](https://www.youtube.com/watch?v=MGOj4NwV0uk). ## What Kody is You do not chat with Kody. Your agent supplies the intelligence; Kody supplies the things that should not live in one chat window: - **Memory**: useful facts without a better home, available to connected agents when relevant. - **Credentials** - API keys and OAuth grants your code can use but your agent can never read (mount `get` returns an opaque placeholder only). There is deliberately no plaintext `secret_get`. - **Packages**: reusable code with typed inputs and documented defaults, callable from any agent, with exports, a hosted app surface, and its own storage. Put repeatable behavior here so running the task doesn’t depend on an agent retrieving an instruction from memory. - **Jobs, workflows, and webhooks** — the triggers that run those packages on a schedule, later, or when a provider knocks — with no model in the loop. - **Integrations and MCP servers** — the logins and tool servers those packages reach through, owned by you, scoped by you. - **An inbox** — every account gets an email address; mail in can start work, mail out can tell you it finished. Kody is Fair Source: the source is available to read, fork, and self-host, and each version converts to the Apache License 2.0 after two years. Kody runs no chat-model agent loop and bills no chat tokens. Search and indexing use a small embedding model; that is not a chat model and is not billed as inference. ## Your agent and Kody work together Personal agents like OpenClaw, OpenMuse, Claude Desktop, Cursor, and Codex are where you talk, think, and act in the moment. Kody is where the results live afterward. Each is better with the other. Your agent is good at: - **The conversation.** Reasoning, judgment, and asking you before it does something risky. - **The surface you already use.** A chat window, an IDE, a terminal, a phone, or a messaging app. - **The computer it runs on.** Depending on the host: local files, a browser, a shell, or a coding sandbox. Hosted Kody cannot see your laptop, and that is fine; your agent can. Kody is good at: - **Remembering across agents.** A fact you tell one agent is there for the next one. - **Holding keys the agent never reads.** Code uses them by name, and only for hosts you approved. - **Keeping working code.** A walk your agent figured out once becomes a package any agent can call. - **Running while you are away.** Jobs, workflows, and webhooks run with no model in the loop and no laptop attached. Together, the agent does the thinking once and Kody keeps the result: - **Ask again tomorrow** becomes a saved export. No model in the loop. - **A key in chat or a `.env`** becomes a credential the agent never sees. - **Re-run the agent on a timer** becomes a job that runs while you are offline. - **Facts without another home** become memories that follow the account. - **Repeated task instructions** become package code and documented defaults. A personal agent watching your school inbox can hand the watching to a Kody job that still fires when the laptop is in a bag. A receipt hunt your phone agent worked out becomes a package Cursor can call the next morning. ## What Kody is not Kody is not another chat app; there is nothing to talk to besides the agent you already use. It is also not a gateway whose job is wiring APIs for your agent. Integrations and MCP servers are there when a job needs them. The center is owned memory and owned packages that run in Kody's cloud and are callable from any MCP host. ## What you cannot get elsewhere If you are comparing Kody against something else, these three are the reasons it exists. Everything in the next section is supporting cast. 1. **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. This is not an agent re-run on a timer: there are no tokens spent, no prompt to drift, and nothing waiting on a model to respond. See [How Kody works](/docs/how-kody-works) and [Jobs, workflows, and webhooks](/docs/triggers). 2. **Your agent uses your keys without ever reading them.** It writes whatever code the job needs and still cannot see a credential (no capability returns one). Code references credentials by name and Kody substitutes them at the network boundary, only for hosts you approved. When a provider token is coarser than the job (Gmail has a send scope and no drafts-only scope), a locked package is the real grant: published code cannot silently start sending. See [Secrets](/docs/secrets) and [Gmail drafts without send](/docs/locked-gmail-drafts). 3. **Every agent you connect shares one home, and every install is a fork you own.** Switch from Claude to Cursor to a phone agent and the memories, credentials, packages, and jobs are already there. Installing someone else's automation puts code in your account, on your credentials, that you can open, change, schedule, and republish. Nothing stays locked in someone else's runtime or in one vendor's chat history. See [Connect your agent](/docs/connect-your-agent) and [Shared memory](/docs/memory). ## The building blocks - **Shared memory** — say something once, reuse it from every agent. See [Shared memory](/docs/memory). - **Credentials and integrations** - bring your own API keys and OAuth apps for the services you already use; verified per-provider walkthroughs live under [Connect a provider](https://kody.codes/docs/connect). Credentials stay server-side and never enter your agent's context. See [Secrets](/docs/secrets) and [Integration bootstrap](/docs/integration-bootstrap). - **Ad hoc execution** — your agent runs sandboxed code against those integrations immediately, no deploy step. See [Search and execute](/docs/search-and-execute). - **Packages** — reusable saved code your agent writes and improves over time. Packages expose exports, own scheduled jobs, receive webhooks, and can serve a small web app. See [Package lifecycle](/docs/package-lifecycle) and [Package authoring](/docs/package-authoring). - **Jobs, workflows, and webhooks** — recurring schedules, deferred one-shot runs that survive restarts, and HTTPS endpoints for Sentry, GitHub, Stripe, or any provider that cannot set Bearer tokens. See [Jobs, workflows, and webhooks](/docs/triggers). - **A personal email inbox** — inbound mail can trigger automations, and your packages can send you notifications. See [Email primitives](https://raw.githubusercontent.com/kentcdodds/kody/main/docs/use/email-primitives.md). - **Public packages** — browse automations other people published, and fork them into your own account with one click. See [Public packages](https://raw.githubusercontent.com/kentcdodds/kody/main/docs/use/community-packages.md). - **Extensibility** — connect your own remote MCP servers, OpenAPI providers, or a home MCP server so your agent can reach devices on your network through Kody. Lock a connected MCP server to a package when execute should not call its tools. See [Connect a home MCP server](/docs/local-mcp-tunnels) and [Lock an MCP server to a package](/docs/locked-mcp-server). ## What people use it for Concrete examples that combine the blocks: - A morning digest job that gathers your calendar, weather, and feeds, then emails you a summary before you wake up. - A watcher that polls a website, feed, or price and emails you only when something actually changes. - Chore automation against services you already use — triaging GitHub notifications, filing issues, cleaning up cloud resources — using your own API keys. - A personal API: a package export you can hit from shortcuts or webhooks to log a habit, save a link, or kick off a run. - An inbound webhook that fingerprints repeated failures and emails one investigation instead of a flood. - Home automation routines through a home MCP server — scenes, thermostats, speakers — driven by schedule or by asking your agent. - Forking a public package (say, a YouTube video manager or an RSS digest) and having your agent adapt it to your needs. - A drafts-only Gmail helper that prepares invoice replies you send yourself, locked so a later agent cannot republish a send path. See [Gmail drafts without send](/docs/locked-gmail-drafts). ## Where to go next - **Get started** — [Connect your agent](/docs/connect-your-agent) walks through the in-app flow: connect one host, make something useful, then prove it travels to a second agent. - **Meet the two tools** — [Search and execute](/docs/search-and-execute) is the playbook for the MCP surface: find the right thing, then run it. - **See the loop** — [How Kody works](/docs/how-kody-works) plays one conversation from ad hoc question to owned export to quiet daily email. - **Learn the primitives** — [The factory map](/docs/kody-factory), then [Shared memory](/docs/memory), [Secrets](/docs/secrets), [Packages, integrations, and MCP servers](/docs/packages-integrations-mcp), and [Jobs, workflows, and webhooks](/docs/triggers). - **Text a familiar surface** — [Text your agent](/docs/text-your-agent) is the iMessage, SMS, and Discord worked example: humans talk to your agent; that agent uses Kody for tools and memory. - **Build** — [Package lifecycle](/docs/package-lifecycle) decides when to save; [Package authoring](/docs/package-authoring) shows how. ## Try it Paste this into an agent that can fetch URLs or search the web. If an agent is already interviewing you about Kody, you do not need to paste it again — it is the same conversation. > I'm deciding whether Kody (https://kody.codes) would be useful for me. Read > https://kody.codes/docs/what-is-kody and then interview me to find out what > Kody could do for me.