# Kody

> Kody is Your agents' cloud for individuals and teams (orgs, teams,
> grants): connect the AI agent you already use over MCP and it gains
> durable memory, credentials it never reads, saved packages, jobs,
> workflows, webhooks, and apps that keep running while you are offline,
> and every other agent you connect reuses the same home.

Start with [What is Kody?](https://kody.nafigroup.app/docs.md). Each documentation link below is
plain markdown; the same content is available to connected agents as
`search({ entity: "guide:{id}" })`.

No account yet? Pick Try it out on the Kody sign-in screen and claim the account later by telling your agent.

## Kody Open API

Call Kody over HTTPS (OpenAPI 3.1). Available to every signed-in account.

- [Interactive docs](https://api-docs.kody.codes/) — Scalar UI at api-docs.kody.codes
- [OpenAPI description](https://api.kody.codes/openapi.json) — machine-readable service description
- [Kody Open API guide](https://kody.nafigroup.app/docs/open-api.md) — how to mint tokens and call `/v1`
- [API versioning and deprecation](https://kody.nafigroup.app/docs/api-versioning.md) — additive `/v1`, phased migrations

## Introduction

What Kody is, the two MCP tools, and the loop those tools run.

- [What is Kody?](https://kody.nafigroup.app/docs/what-is-kody.md) — Start here. Kody is Your agents' cloud for individuals and teams. Connect the AI agent you already use over MCP and it gains durable memory, credentials it never reads, saved packages, and jobs that keep running while you are offline. Covers what Kody is, how it pairs with the agents you already use, what you cannot get elsewhere, the building blocks, real uses, and notes for an agent running a discovery interview. Nothing here requires an account.
- [Search and execute](https://kody.nafigroup.app/docs/search-and-execute.md) — Search finds capabilities, guides, packages, integrations, and secrets. execute runs an ephemeral module that calls what you found. Covers how they work together and the inputs an agent actually passes. The MCP api tool is documented separately.
- [How Kody works](https://kody.nafigroup.app/docs/how-kody-works.md) — The factory loop as a conversation: ask what your favorite bot shipped, save the answer as an export you can invoke from any agent, then a daily email that stays quiet until something actually ships.
- [The Kody factory map](https://kody.nafigroup.app/docs/kody-factory.md) — Map Kody's discovery, credentials, integrations, packages, storage, schedules, hosted surfaces, and memories—and know where the boundary is.

## Get started

Connect the agent you already use, make one useful thing, then reuse it from a second agent.

- [Connect your agent](https://kody.nafigroup.app/docs/connect-your-agent.md) — The three-step Get started flow for people: connect the agent you already use over MCP, paste one prompt so that agent makes something useful in your account, then connect a second agent from another ecosystem and watch it reuse the same memory and package. Includes what approving access means, verified-email requirements, and which agents suit building versus using.
- [First run: the onboarding briefing](https://kody.nafigroup.app/docs/onboarding.md) — First-run guide for a connected agent. Teach lightly what Kody is and is not, offer six concrete first-win choices, help them take one small win from their pick, and set up integrations with clear difficulty. Then Step 3.
- [First build: ad hoc execute, then persist](https://kody.nafigroup.app/docs/quick-example.md) — Agent playbook after Make something useful (`/onboarding/step-2`) or Connect your agent (`/onboarding/step-1`): run one useful ad hoc execute, show the result, persist that working code as a package they own, and offer optional triggers without recommending one.
- [Second agent: reuse what already exists](https://kody.nafigroup.app/docs/portability.md) — Second-agent proof after a first win. Find what the account already has, reuse it once, and stop. Retrieved as guide:portability from Step 3.
- [Email and memories: the welcome-email loop](https://kody.nafigroup.app/docs/first-win.md) — Optional agent playbook: send a welcome email, point the person at their own inbox to reply, look the reply up when they say it is sent, save what matters as memories, then offer a next step. After Connect your agent (`/onboarding/step-1`), Step 2 is Make something useful (`/onboarding/step-2`) and Step 3 is Connect a second agent (`/onboarding/step-3`); the optional climax guide is quick-example. Load this when someone wants the email loop. Includes the no-polling rule and troubleshooting for missing mail and unbound tools.

## Concepts

The primitives every connected agent shares: memory, credentials, packages, triggers, and the runtime.

- [Shared memory](https://kody.nafigroup.app/docs/memory.md) — What a Kody memory is (personal-only), why it follows the person instead of one host's chat or a team org, how memories surface automatically on search and execute, the verify-first rule for writes, and what does not belong in memory (package state, config, credentials, shared org knowledge). Load this when someone asks what their agents remember about them or how memory travels between agents.
- [Where agent guidance lives](https://kody.nafigroup.app/docs/agent-guidance.md) — Progressive disclosure for agent guidance across MCP server instructions, package docs (README.md and AGENTS.md), export JSDoc, and memories. Load this when deciding where a fact or instruction should live, or before calling metaMemoryUpsert or metaSetMcpServerInstructions. Search phrases such as "where should this guidance live" should find this page.
- [Credentials](https://kody.nafigroup.app/docs/credentials.md) — What a Kody credential is and every kind it comes in (Key, OAuth, MCP server, URL, login, signing), how `{{secret:name}}` placeholders and scoped `credential(key)` clients place a value at the network boundary, how packages declare needs in `kody.credentials` (including publisher and executor credential needs that app visitors fill with `credential.visitor(key)`), how callers pick between credentials with names and call maps, the `credential_ambiguous` / `credential_unbound` errors, and webhook verification. Load this when someone asks how credentials work, which kind to use, or why a credential did not resolve.
- [Secrets](https://kody.nafigroup.app/docs/secrets.md) — How Kody lets your agent use your API keys, tokens, and private keys without ever reading them: the no-secret_get rule, `{{secret:name}}` placeholders resolved at the network boundary, host approval, package approval (website Allow links via `resourceLock`), and expiry. Keys are one credential kind; the Credentials guide covers every kind. Load this when someone asks whether the agent can see a key.
- [Custom secret providers](https://kody.nafigroup.app/docs/secret-providers.md) — Use credentials from an external vault in secret-aware fetch without the agent ever reading them.
- [Packages, integrations, and MCP servers](https://kody.nafigroup.app/docs/packages-integrations-mcp.md) — Packages are saved behavior. Integrations are account-owned logins. MCP servers are how agents connect. Use this when those three look interchangeable.
- [Organizations](https://kody.nafigroup.app/docs/organizations.md) — Personal vs team orgs, invite links, who automation runs as, the org-wide execute pool, connecting one client to several orgs, free-org limits, and paid seats.
- [Text your agent](https://kody.nafigroup.app/docs/text-your-agent.md) — How to let a spouse or friend talk to *your agent* over a familiar chat surface (iMessage worked example). Surface vs brain vs home: the agent holds the conversation; Kody is the home it reaches into for memory, secrets, packages, and jobs. Covers OpenClaw/Bezalel/Grok Bot patterns and a simpler SMS path with Twilio.
- [OpenMuse and Kody](https://kody.nafigroup.app/docs/openmuse.md) — How and why to use OpenMuse, CopilotKit's open-source, self-hostable personal agent, alongside Kody. OpenMuse is the personal-agent app (phone and web chat, an agent computer, goals, reviewed actions); Kody is the home that agent shares with your other agents (memory, credentials it never reads, packages, jobs, webhooks, inbox). Covers what each is good at, what to put where, and how to connect OpenMuse's agent harness to Kody over MCP.
- [Jobs, workflows, and webhooks](https://kody.nafigroup.app/docs/triggers.md) — How work runs when nobody is in the chat. Package-owned jobs for recurring schedules, workflows for deferred or long one-shot runs, inbound webhooks for provider events, subscriptions for events inside Kody, and the inbox — which to pick, how each is declared, and how to test one safely before enabling it. Load this when someone asks how to run something later, on a schedule, or when a provider knocks.
- [Runtime and efficiency](https://kody.nafigroup.app/docs/platform-efficiency.md) — How unique Dynamic Worker days work across execute, jobs, package exports, and other surfaces, and how the acting user plus a stable module graph reuse one isolate per UTC day.
- [Local CLI execute](https://kody.nafigroup.app/docs/local-execute.md) — Prefer @kodycodes/cli execute --local when Node ≥22 and the CLI are available. Orthogonal to Open API: use this guide for CLI setup and --local usage; see guide:open_api for HTTPS / MCP api fallback.
- [Execution contexts](https://kody.nafigroup.app/docs/execution-contexts.md) — Run execute and automations on your own laptop or build server instead of Kody cloud. Credentials stay in Kody cloud; the machine adds host folders, LAN, and (after a local opt-in) shell commands via kody.command.run / kody.command.start, from execute or saved packages, with the execution_context:command grant. An experiment you turn on at /account/experiments.
- [Profiles](https://kody.nafigroup.app/docs/profiles.md) — Give an agent or bot its own scoped identity in an org, with a snapshot of your access, an expiry that only shortens, and sub-profiles for the agents it starts. An experiment you turn on at /account/experiments.
- [Git credential helper contract (setup-git)](https://kody.nafigroup.app/docs/auth-setup-git.md) — Server contract for `kody auth setup-git`: user-owned CLI tokens, `?org=`, and persistent HTTPS git auth with a long-lived `kody_at_…` on `https://kody.codes/@owner/name.git` (clone, fetch, and push).
- [Kody Open API](https://kody.nafigroup.app/docs/open-api.md) — Call Kody over HTTPS at api.kody.codes. MCP api runs one operation (operationId + params), including tokenCreate / tokenList / tokenRevoke. Available to every signed-in account.
- ['API tokens (API keys): list, revoke, delete, rotate'](https://kody.nafigroup.app/docs/api-tokens.md) — List, inspect, rotate, and revoke your Kody API tokens (kody_at_ API keys) with tokenList / tokenGet / tokenRotate / tokenRevoke. These are Open API operations, reachable from the MCP api tool, HTTPS, or `kody api`, not from execute.
- [API versioning and deprecation](https://kody.nafigroup.app/docs/api-versioning.md) — How Kody versions the HTTP Open API under /v1, signals deprecations, and migrates without breaking people and their packages.

## Examples

Homepage trigger cards as worked examples: cron, webhook, email, and event.

- [Flake Hunter](https://kody.nafigroup.app/docs/flake-hunter.md) — Homepage cron example: a package-owned daily job that scans CI for flaky end-to-end runs, stays quiet on a clean day, and only acts when a flake signal is present. Load this when someone asks how Flake Hunter works or how to hang a schedule on a package they own.
- [Sentry Issues](https://kody.nafigroup.app/docs/sentry-issues.md) — Homepage webhook example: a package-owned inbound URL that accepts a Sentry issue POST, verifies HMAC on the platform, and starts triage without a model in the request path. Load this when someone asks how Sentry Issues works or how to hang a vendor webhook on a package they own.
- [Agent inbox](https://kody.nafigroup.app/docs/agent-inbox.md) — Homepage email example: every account has a platform inbox, inbound mail emits email.message.received, and a package can wake work from a plus-tag without a model reading the mailbox. Load this when someone asks how Agent inbox works or how to treat email as a trigger.
- [Purchase thanks](https://kody.nafigroup.app/docs/purchase-thanks.md) — Homepage event example: a verified purchase becomes a fact your factory already knows, and a package drafts a thank-you without anyone typing. Load this when someone asks how Purchase thanks works or how to react to an event Kody (or a package you own) already emitted.

## Packages

Turn working code into a package you own, then grow it.

- [Package lifecycle: reuse, execute, fork, or create](https://kody.nafigroup.app/docs/package-lifecycle.md) — Choose between invoking existing behavior, temporary execute exploration, forking a close public package, deferred workflows, and creating a durable repo-backed package; session/tool-only lane validates with `repoRunChecks`, git lane with local checks plus `packagePublishExternalPush`; when the host can run the CLI use `kody dev` / mocks / `--local` before publish.
- [Package authoring](https://kody.nafigroup.app/docs/package-authoring.md) — START HERE when creating or materially changing a Kody package: shape, required README.md and AGENTS.md, README Intent, per-export JSDoc, runtime input checking, public-visibility hygiene, and secret-using approvals.
- [Share a package and manage access](https://kody.nafigroup.app/docs/package-sharing.md) — Give a person or team Read, Use, Contribute, or Manage on one package with a grant, invite someone who is not in your organization yet, share private source with one person (Read, then they fork it), and know what each side can run, read, and pay for. Also covers unmappable credentials: share-time warnings, the owner-only change lock, and the per-grant "allow changes despite unmappable credentials" option.
- [Shared packages for many accounts](https://kody.nafigroup.app/docs/shared-packages.md) — Build one package that many callers import, each with its own account of the same provider. Declare the need once, let each caller map it on its own package, pick per run, open several accounts with multiple, or pass a client in.
- [Ship Agent Skills in a package](https://kody.nafigroup.app/docs/package-skills.md) — Put skills/<name>/SKILL.md in a package, publish, and expose them over MCP to hosts that support Skills-over-MCP.
- [Package apps](https://kody.nafigroup.app/docs/package-apps.md) — Give a package a hosted Worker app on `*.kody.run`. Covers the fetch-handler contract, mount-stripped URLs, `packageContext` / `kody:runtime`, the platform-built browser client (`kody.app.client`) and static assets directory (`kody.app.assets`), session handoff, optional CLI local testing with `kody dev` when available, MCP-only validate via `repoRunChecks`, smoke tests with packageAppFetch, a Remix recipe (Example A), the same-origin proxy, lean forks, compiled clients, and listing verification.
- [Custom domains](https://kody.nafigroup.app/docs/package-app-custom-domains.md) — Serve an app on a domain you own. Covers which hostnames are allowed, the exact DNS records (DNS only, proxy off), how Kody checks status and emails you, and what pending, active, and needs attention mean.
- [Package subscriptions and events](https://kody.nafigroup.app/docs/package-subscriptions.md) — Use package.json#kody.subscriptions for package-owned event handlers; discover subscribers with packageSubscriptionsList; smoke-test one handler from interactive MCP with packageSubscriptionDispatch; follow metadata-first email, run.error.recorded activity notifiers, integration.auth.failed / integration.auth.succeeded reconnect notifiers, mcp.server.disconnected / mcp.server.reconnected connection episodes, follow.published / follow.pushed follow notifiers, community.fork.upstream_updated fork notifiers, resource change events (credentials, packages, jobs, triggers, membership, memories), and repo / package lifecycle topics.
- [MCP Events from packages](https://kody.nafigroup.app/docs/mcp-events.md) — Opt a package topic into MCP Events so ChatGPT (and other webhook-capable MCP clients) can subscribe. Delivery reuses the same package event bus as kody.subscriptions. Behind the mcp-events-extension flag.
- [Wake your agent](https://kody.nafigroup.app/docs/wake-your-agent.md) — Recipe for waking a connected agent when something happens in Kody (a failed run, a package event, inbound mail). Lead with MCP Events when the MCP client supports the events extension (behind the mcp-events-extension flag; ChatGPT today). Otherwise use a package subscription or job that POSTs to the agent's webhook URL, or the email-wake pattern. Pick by what the client supports.
- [Offload work that does not fit a Worker isolate](https://kody.nafigroup.app/docs/heavy-work-offload.md) — When package checks or publish rebuilds exceed isolate memory or CPU — usually a large npm graph such as PDF.js — keep the Kody package as a thin orchestrator and run the heavy work in a process the owner operates (Cloudflare Container, Fly machine, or similar). Do not provision paid infra without asking.
- [Publish packages too big for Kody cloud](https://kody.nafigroup.app/docs/publish-large-packages.md) — When a publish hits the worker's memory, CPU, or payload limits, build the package on your own machine (`kody package publish --build local`) or on an execution context you operate (`--build context`). The CLI pushes HEAD first; Kody checks the upload against that commit, links any `kody:@` packages it imports, and writes the registry itself.

## Integrations

Bring your own keys, OAuth apps, OpenAPI documents, and MCP servers — and lock them to the code that should use them.

- [Integration bootstrap](https://kody.nafigroup.app/docs/integration-bootstrap.md) — START HERE when a third-party integration must work before saving a dependent package or package app: inspect integration/secret state, stop for setup, run an authenticated smoke test, then communitySearch before building from scratch.
- [OAuth: bring your own app](https://kody.nafigroup.app/docs/oauth.md) — START HERE for third-party OAuth: hosted /connect/oauth, the exact redirect URI (https://kody.codes/connect/oauth), required query params, PKCE vs confidential, the post-connect copyable agent prompt, and how it differs from MCP OAuth.
- [Google OAuth walkthrough](https://kody.nafigroup.app/docs/google-oauth.md) — Interactive transcript of a coding agent walking a naive user through Google OAuth for Gmail inbox reading: official guides first, one console step at a time, prefilled /connect/oauth, refuse secrets in chat, then a Gmail profile smoke test.
- [Secret-backed integrations](https://kody.nafigroup.app/docs/secret-backed-integration.md) — Default non-OAuth recipe for secret-backed integrations: research auth, collect secrets through /connect/secret-set, run a smoke test, build the downstream package, then surface package secret approval links (prefer bulk) before calling the work complete.
- [Secret setup URL reference](https://kody.nafigroup.app/docs/account-secret-setup.md) — Hosted /connect/secret-set URL shape, query params, approval policy for API keys and PATs, and post-hoc package approval URLs including bulk approve.
- [OpenAPI integrations](https://kody.nafigroup.app/docs/openapi-integrations.md) — Prefer a close community helpers package, then fork `@kody/openapi` to bind and call selected operations.
- [Connect a home MCP server](https://kody.nafigroup.app/docs/local-mcp-tunnels.md) — Run an MCP server beside a vault, CLI, or home device, publish it with Cloudflare Tunnel and Access, and connect its HTTPS URL to Kody.
- [Lock an MCP server to a package](https://kody.nafigroup.app/docs/locked-mcp-server.md) — Connected MCP servers expose every discovered tool to execute and every package. Lock the server to a thin package so only that published surface can call it.
- [Gmail drafts without send](https://kody.nafigroup.app/docs/locked-gmail-drafts.md) — Google has gmail.send but no drafts-only scope. gmail.compose can manage drafts and send. Publish a drafts-only package, lock it, then resourceLock the connection so execute cannot use the token.

## Connect a provider

Verified, console-by-console walkthroughs for connecting a specific service.

- [Connect Discord](https://kody.nafigroup.app/docs/discord.md) — Verified walkthrough for connecting Discord to Kody: the OAuth user-token lane for identity and server membership, the bot-token lane required for reading or posting in servers, 7-day rotating tokens, prefilled connect links, and users/@me smoke tests for both lanes.
- [Connect Dropbox](https://kody.nafigroup.app/docs/dropbox.md) — Walkthrough for connecting Dropbox to Kody with your own Dropbox app: app console setup, the PKCE connect link with offline refresh tokens, the three Dropbox API hosts (api, content, notify), and a smoke test through @kentcdodds/dropbox.
- [Connect Figma](https://kody.nafigroup.app/docs/figma.md) — Verified walkthrough for connecting Figma to Kody (BYO OAuth or personal/plan access token), then using @kody/figma over Figma REST, not Figma's remote MCP.
- [Connect GitHub](https://kody.nafigroup.app/docs/github.md) — Verified walkthrough for connecting GitHub to Kody: fine-grained personal access tokens, bring-your-own OAuth Apps, scope choices, prefilled connect links, and copy-paste smoke tests.
- [Connect Google (Gmail, Calendar, Drive)](https://kody.nafigroup.app/docs/google.md) — Verified walkthrough for connecting Google to Kody: bring-your-own OAuth client, Google Auth Platform console steps, the Testing-status 7-day refresh-token trap, and a Calendar or Gmail smoke test.
- [Connect Notion](https://kody.nafigroup.app/docs/notion.md) — Verified walkthrough for connecting Notion to Kody: the personal internal connection token lane (fastest), the public connection OAuth lane, the page-picker access model (Notion has no OAuth scopes), prefilled connect links, and a users/me smoke test for both lanes.
- [Connect Origin](https://kody.nafigroup.app/docs/origin.md) — Verified walkthrough for connecting Cursor Origin to Kody: Origin Apps with Ed25519 signing keys, installation access tokens, the community helpers package, and a rate-limit smoke test. Cloud Agents API keys are not Origin credentials.
- [Connect Salesforce](https://kody.nafigroup.app/docs/salesforce.md) — Verified connect walkthrough for Salesforce: bring-your-own Connected App or External Client App, the exact /connect/oauth callback, production vs sandbox login hosts, scopes, prefilled connect links, and a smoke test.
- [Connect Slack](https://kody.nafigroup.app/docs/slack.md) — Verified walkthrough for connecting Slack to Kody with a user-token Slack app, then calling it from `@kody/slack`.
- [Connect Spotify](https://kody.nafigroup.app/docs/spotify.md) — Verified walkthrough for connecting Spotify to Kody: dashboard app creation, the Development Mode Premium requirement and endpoint limits in force since February 2026, the PKCE public-client connect link, listening and playback scopes, and a profile smoke test.

## Help

When Kody gets in the way.

- [Sign in to an app from an e-reader or older browser](https://kody.nafigroup.app/docs/limited-browser-sign-in.md) — Sign in to a Kody package app from a browser that cannot run Kody's page JavaScript (e-readers, older Chromium, JavaScript off) with your email and password, or with Sign in on another device (short code plus QR code).
- [If you can't open kody.codes or get mail from us](https://kody.nafigroup.app/docs/cant-open-or-get-mail.md) — Unblock NextDNS and similar DNS filters for kody.codes, and recover missing signup or verification mail when a provider is blocking our domain.
- [Report friction](https://kody.nafigroup.app/docs/platform-friction.md) — Use for meaningful Kody friction, bugs, poor experiences, or suggestions: show the exact proposal and account-identity notification disclosure before asking for explicit approval, and write one actionable issue per submission (repro steps, expected vs actual, impact).

## Website

- [What will you build with Kody?](https://kody.nafigroup.app/use-cases): Build reusable tools, automate inbox work, share context across your agents, and run workflows on a schedule with Kody.
- [n8n alternatives for developers](https://kody.nafigroup.app/compare/n8n-alternatives): Build reusable workflows with your agent in Kody. Compare its packages, connected accounts, and schedules with n8n and other automation tools.
- [An MCP gateway for your personal agents](https://kody.nafigroup.app/use-cases/mcp-gateway): Understand direct MCP connections, gateways, and Kody. Connect agents to shared tools, accounts, memory, and saved workflows.
- [Shared memory for Claude Code, Cursor, and Codex](https://kody.nafigroup.app/use-cases/shared-agent-memory): Share useful facts between Claude Code, Cursor, and Codex. Keep repeatable behavior in packages, and use Kody memory for facts without a better home.
- [Gmail automation with Claude and MCP](https://kody.nafigroup.app/integrations/gmail): Connect Gmail to your agent and build an inbox workflow you can use again, with drafts to review and control over what gets sent.
- [Build reusable custom tools for Claude Code](https://kody.nafigroup.app/use-cases/claude-code-custom-tools): Turn a repeated Claude Code task into a Kody package. Keep the code and connected accounts ready for your other agents to use.
- [Composio alternatives for personal agent workflows](https://kody.nafigroup.app/compare/composio-alternatives): Explore Kody as a Composio alternative for personal agent workflows, with connected accounts, reusable packages, memory, and schedules in one place.
- [Slack automation that keeps track of the work](https://kody.nafigroup.app/integrations/slack): Build reusable Slack workflows with Kody. Connect your services, keep track of what’s been posted, and review messages before putting them on a schedule.
- [Schedule reusable workflows built with Claude](https://kody.nafigroup.app/use-cases/scheduled-workflows): Run saved code on a schedule with Kody. Automate reports, keep track of progress, and use AI where your workflow needs it.
- [Claude integrations you can keep using across agents](https://kody.nafigroup.app/integrations/claude): Connect Claude to Kody and reuse your accounts, memory, and tools beyond one conversation. Build workflows you can run from any connected agent.
- [AI workflow automation for developers](https://kody.nafigroup.app/use-cases/ai-workflow-automation): Choose visual workflows, agent routines, or reusable code. Build automation in Kody with connected accounts, saved packages, memory, and schedules.
- [The cloud for your team’s agents](https://kody.nafigroup.app/): One place for the credentials, tools, and workflows for every agent your team members use.
- [Public packages — Kody](https://kody.nafigroup.app/community): Browse public packages shared by Kody users.
- [Blog — Kody](https://kody.nafigroup.app/blog): Essays, how-to guides, release notes, and customer stories about Kody, from Kent C. Dodds.
- [Kody features for your AI agents | Kody](https://kody.nafigroup.app/features): Memory, packages, triggers, credentials, and apps for your connected AI agents.
- [Shared memory for your AI agents | Kody](https://kody.nafigroup.app/features/memory): Save facts and preferences in Kody and use them with agents connected to your account.
- [Reusable packages for your AI agents | Kody](https://kody.nafigroup.app/features/packages): Save reusable code, review its source, publish changes, and share access to your packages.
- [Triggers and automation for your AI agents | Kody](https://kody.nafigroup.app/features/triggers): Start saved packages from schedules, webhooks, incoming email, and package events.
- [Credentials for your AI agents | Kody](https://kody.nafigroup.app/features/credentials): Keep API keys and OAuth connections out of the conversation. Anything that speaks OAuth can connect, and Kody sends credentials only to hosts you approve.
- [Package apps for your AI agents | Kody](https://kody.nafigroup.app/features/apps): Build browser interfaces backed by saved packages and durable package storage.
- [AI Agent Cloud for Business and Agencies | Kody](https://kody.nafigroup.app/for/business): Give your teams and AI agents a shared home for tools, data, and automations. Run work across departments and client organizations with clear ownership.
- [Pricing — Kody](https://kody.nafigroup.app/pricing): Every plan is the whole factory. You pay for volume. Paid plans raise the caps.
- [FAQ — Kody](https://kody.nafigroup.app/faq): Common questions about what Kody is, what it is not, and how your assistant stays yours.
- [Case studies — Kody](https://kody.nafigroup.app/case-studies): Longer notes from people using Kody — how it shows up in their work.
- [What we believe: Kody](https://kody.nafigroup.app/believe): The beliefs behind Kody, each tied to how the product behaves today.
- [Support — Kody](https://kody.nafigroup.app/support): Contact support for the hosted Kody service at kody.codes.
- [About Kody](https://kody.nafigroup.app/about): Kody is Your agents' cloud for individuals and teams. Built by Kent C. Dodds at kody.codes.
- [Brand guide — Kody](https://kody.nafigroup.app/brand-guide): Download the Kody koala mark as SVG or PNG, and see light and dark treatments.
- [Contact Kody](https://kody.nafigroup.app/contact): Email support@kody.codes, join Discord, or open a GitHub issue for the hosted Kody service.
- [Privacy — Kody](https://kody.nafigroup.app/privacy): How Kody stores your data and what a deployment admin can see.
- [Terms — Kody](https://kody.nafigroup.app/terms): Terms and acceptable use for this Kody deployment.
- [Discord — Kody](https://kody.nafigroup.app/discord): Join the official Kody Discord and connect your account so we can assign member and plan roles.
- [Get started — Kody](https://kody.nafigroup.app/onboarding): Connect your AI agent host and set up Kody for you or your team.
- [Kody for Cursor](https://kody.nafigroup.app/with/cursor): Keep building in Cursor. Kody gives it your team’s credentials, packages, and workflows, and anything it saves runs from every other agent your team uses.
- [Kody for Claude Code](https://kody.nafigroup.app/with/claude-code): Claude Code writes the package. Kody keeps it, runs it on a trigger, and shares it with the rest of your team.
- [Kody for Codex](https://kody.nafigroup.app/with/codex): Let Codex build tools your whole team can run, with credentials it uses but never sees.
- [Kody for ChatGPT](https://kody.nafigroup.app/with/chatgpt): Use your team’s packages and connected accounts from a ChatGPT conversation, on the web or on your phone.
- [Kody for Claude](https://kody.nafigroup.app/with/claude): Bring your team’s tools and connected accounts into Claude conversations on desktop, web, and mobile.
- [Kody for GitHub Copilot](https://kody.nafigroup.app/with/copilot): Give Copilot in VS Code or the terminal the same credentials and packages the rest of your team uses.
- [Kody for Devin](https://kody.nafigroup.app/with/devin): Let Devin use your team’s credentials and packages without pasting a single key into a session.
- [Kody for Gemini](https://kody.nafigroup.app/with/gemini): Run your team’s packages from the Gemini app, with credentials Gemini never sees.
- [Kody for Grok](https://kody.nafigroup.app/with/grok): Bring your team’s tools into Grok conversations through one custom connector.
- [Kody for Grok Bot](https://kody.nafigroup.app/with/grok-bot): Start from the Kody Bot template and Grok Bot works on your Kody repos and packages through the Kody CLI and git.
- [Kody for OpenCode](https://kody.nafigroup.app/with/opencode): Point OpenCode at Kody, and every package it writes becomes something your whole team can run.
- [Kody for OpenClaw](https://kody.nafigroup.app/with/openclaw): Give your local-first OpenClaw agent the shared credentials and workflows your team keeps in Kody.
- [Kody for Hermes Agent](https://kody.nafigroup.app/with/hermes): Give Hermes the shared credentials and packages your team keeps in Kody, from the terminal or any chat app it runs in.
- [Kody for Muse](https://kody.nafigroup.app/with/muse): Connect Muse Code to Kody so the tools it builds outlive the session and reach the rest of your team.
- [Kody for Amp](https://kody.nafigroup.app/with/amp): Let Amp build packages your whole team can run, with credentials it uses but never sees.
- [Kody for Warp](https://kody.nafigroup.app/with/warp): Give Warp’s agents the same credentials, packages, and workflows the rest of your team uses.
- [Kody for Goose](https://kody.nafigroup.app/with/goose): Point Goose at Kody, and the tools it builds stay around for the rest of your team.
- [Kody for Zed](https://kody.nafigroup.app/with/zed): Bring your team’s credentials, packages, and workflows into Zed’s agent panel.
- [Kody for Pi](https://kody.nafigroup.app/with/pi): Give Pi the shared credentials and workflows your team keeps in Kody.
- [Kody for Wajo](https://kody.nafigroup.app/with/wajo): Reach your team’s packages and connected accounts from Wajo, wherever you chat.
- [Kody for Cue](https://kody.nafigroup.app/with/cue): Let your Cue agents use your team’s tools and connected accounts without ever seeing a key.
- [Kody for OpenMuse](https://kody.nafigroup.app/with/openmuse): Wire Kody into your OpenMuse harness so the work it does reaches the rest of your team.
- [Kody for Dots](https://kody.nafigroup.app/with/dots): Bring your team’s tools and connected accounts into Dots through one MCP connection.
- [Kody Docs](https://kody.nafigroup.app/docs): Learn how to use Kody.
- [Connect a provider](https://kody.nafigroup.app/docs/connect): Set up connections to your accounts.
- [Connect your agent](https://kody.nafigroup.app/auth.md): OAuth and MCP endpoint details.

## Blog posts

- [Every personal agent needs a cloud](https://kody.nafigroup.app/blog/every-personal-agent-needs-a-cloud): Personal agents build software to solve their users’ problems, and that software needs storage and an execution context
- [Three ways to share an AI-built app, and whose keys each one uses](https://kody.nafigroup.app/blog/three-ways-to-share-an-ai-built-app): Fork it, grant it, or let people sign in. How to share an AI-built app by deciding whose credentials it runs on and who pays for the work.
- [How to set up a team org for your AI-built apps](https://kody.nafigroup.app/blog/set-up-a-team-org-for-ai-built-apps): Your personal Kody org stays yours. Create a separate team org, decide what moves into it, set member permissions, and invite people with links.
- [Read, Use, Contribute, or Manage? Picking the right access for each teammate](https://kody.nafigroup.app/blog/read-use-contribute-manage-app-access): What each Kody access preset lets a teammate run, read, change, and publish, what no preset grants, and how to check the access you gave.
- [This is better than a skill, how ship-pr ships a pull request the same way every time](https://kody.nafigroup.app/blog/ship-pr-better-than-a-skill): A long PR-shipping skill became one Kody package export. What maintained code handles that instructions alone cannot, with a real read-only run.
- [Whose credentials does this app use? How to audit an app before you share it](https://kody.nafigroup.app/blog/whose-credentials-does-this-app-use): Before you share an AI-built app, check five things. Which org owns it, who it runs as, which credentials fill it, who can open it, and who pays.
- [Your first useful Kody workflow, an air quality and daylight check](https://kody.nafigroup.app/blog/first-useful-kody-workflow): Find a public Kody package, read it before you run it, and get a real air quality and daylight report for your city. No keys, no migration.
- [How to give staff and their bots access to your Kody org](https://kody.nafigroup.app/blog/give-staff-and-their-bots-access-to-your-kody-org): You built the packages. Now staff who will never build anything need to ask a bot for answers. How Kody accounts, orgs, seats and bot connections fit.
- [Kody weekly: Local secret reads, an Apps page, and profiles](https://kody.nafigroup.app/blog/kody-weekly-2026-11-06): Local secret reads, an Apps page, usage warnings, and 6 more features, plus fixes and 2 dated credential changes.
- [How to roll out AI agents to your team when it isn't AI-forward yet](https://kody.nafigroup.app/blog/how-to-roll-out-ai-agents-to-your-team): Not everyone on your team wants an AI agent. A practical rollout plan that starts small, keeps keys safe, and lets skeptics adopt at their own pace.
- [Why "just use AWS Lambda" breaks down for teams using AI agents](https://kody.nafigroup.app/blog/why-aws-lambda-breaks-down-for-ai-agent-teams): Lambda can run the code your agents write. The trouble is everything around it, like IAM, secrets, deploys, and review. Here's where it breaks for teams.
- [Kody weekly: Apps run as their publisher, and more for teams](https://kody.nafigroup.app/blog/kody-weekly-2026-10-30): Apps run as their publisher, public team org pages, org-wide grants, and 11 more features, plus 5 breaking changes.
- [Internal tools built with AI that reuse your team's credentials](https://kody.nafigroup.app/blog/internal-tools-built-with-ai-team-credentials): Agents can build an internal dashboard in an afternoon. The hard part is auth, keys, and hosting. How to ship one on credentials you already have.
- [How to avoid AI assistant lock-in, build once and use from any agent](https://kody.nafigroup.app/blog/avoid-ai-assistant-lock-in): Workflows built inside one AI assistant are stuck there. How to keep your team's agent tooling portable across Claude Code, Cursor, Codex, and ChatGPT.
- [Kody weekly: Team orgs, CLI sign-in, and shorter app URLs](https://kody.nafigroup.app/blog/kody-weekly-2026-10-23): Team orgs, CLI OAuth sign-in, shorter package app URLs, and 7 more features, plus smaller updates and fixes.
- [Why AI agent costs keep growing (and how deterministic tools cut tokens)](https://kody.nafigroup.app/blog/why-ai-agent-costs-keep-growing): Agents re-reason the same tasks every day, and you pay for every token. How saving repeated work as deterministic code cuts AI agent costs.
- [AI agent skills vs packages, turning prompts into reviewable code](https://kody.nafigroup.app/blog/ai-agent-skills-vs-packages): Agent skills tell a model what to do; packages are code that does it. When to use each, and how to turn a fragile prompt into reviewable code.
- [Kody weekly: Manage your organization on the web](https://kody.nafigroup.app/blog/kody-weekly-2026-10-16): Org settings and members pages under /@slug/-/, plus 7 more updates to triggers, credentials, MCP servers, and packages.
- [When an engineer quits, their AI workflows break or keep running on their keys](https://kody.nafigroup.app/blog/team-ai-workflows-when-someone-quits): When an engineer leaves, their agent workflows often leave with them or keep running on their keys. How to make AI workflows survive offboarding.
- [The hidden cost of AI tooling for engineering teams when everyone builds their own](https://kody.nafigroup.app/blog/ai-tooling-for-engineering-teams-hidden-cost): Five engineers, five private scripts doing the same job. Why duplicated agent tooling costs more than it looks, and how to build it once for the team.
- [Kody weekly: See where your credits went](https://kody.nafigroup.app/blog/kody-weekly-2026-10-09): Usage and package pages break down where compute went, plus 5 more updates to secrets, packages, and tokens, and 2 breaking changes.
- [How to share AI workflows with your team](https://kody.nafigroup.app/blog/share-ai-workflows-with-your-team): "Copy my prompt" doesn't scale. A concrete way to share AI agent workflows with teammates, teams, and contractors without sharing anyone's keys.
- [AI agent guardrails for your team, without killing autonomy](https://kody.nafigroup.app/blog/ai-agent-guardrails-for-teams): How much should your team's AI agents do without asking? A practical way to set autonomy guardrails that are enforced by the platform, not the prompt.
- [Kody weekly: Call Kody over HTTPS with the Open API](https://kody.nafigroup.app/blog/kody-weekly-2026-10-02): A JSON HTTP API on api.kody.codes with scoped tokens, plus 7 more updates to credits, webhooks, imports, and git, and 2 breaking changes.
- [An AI agent audit log for production access](https://kody.nafigroup.app/blog/ai-agent-audit-log-for-production-access): When an AI agent touches production, can you say who ran what, through which client, and what happened? How to get an agent audit trail you can use.
- [An MCP security checklist for engineering managers](https://kody.nafigroup.app/blog/mcp-security-checklist-for-engineering-managers): A practical MCP security checklist for engineering managers. What to ask about every MCP server your team's AI agents use, and what good looks like.
- [Kody weekly: Smoke-test webhooks without public traffic](https://kody.nafigroup.app/blog/kody-weekly-2026-09-25): webhookSyntheticDispatch sends a test event to your package webhook, plus 5 more updates to Activity, search, and files, and 1 breaking change.
- [How to revoke AI agent access in one place](https://kody.nafigroup.app/blog/revoke-ai-agent-access): When an agent misbehaves or a laptop goes missing, how many places do you revoke? Here's how to make agent access something you can cut off fast.
- [Bring your own key, letting each teammate run shared tools as themselves](https://kody.nafigroup.app/blog/bring-your-own-key-for-shared-team-tools): Shared agent tools shouldn't run as whoever built them. How to let each teammate run the same tool under their own account, with no keys shared.
- [Kody weekly: Manage webhook URLs from your account](https://kody.nafigroup.app/blog/kody-weekly-2026-09-18): Mint, reveal, rotate, and disable webhook URLs at /account/webhooks, plus 7 more updates to connections, email, and package apps.
- [Sharing credentials across Claude Code, Cursor, and Codex without copying secrets](https://kody.nafigroup.app/blog/claude-code-cursor-and-codex-shared-credentials): Your engineers use Claude Code, Cursor, and Codex, each with its own copy of every key. How to give every assistant the same access with zero copies.
- [Least privilege for AI agents, a practical setup](https://kody.nafigroup.app/blog/least-privilege-for-ai-agents): A layer-by-layer least-privilege setup for AI agents: provider scopes, host allowlists, fill placement, package-only keys, locks, and expiry.
- [Kody weekly: Anyone can sign up for Kody](https://kody.nafigroup.app/blog/kody-weekly-2026-09-11): Signup is open with no waitlist or invite, plus 7 more updates to docs, referrals, agents, email, and packages, and 1 breaking change.
- [AI agent GitHub access without handing over your token](https://kody.nafigroup.app/blog/ai-agent-github-access-without-your-token): Let an AI agent read repos, open PRs, and check CI without ever seeing a GitHub token. A step-by-step setup with fine-grained tokens and Kody.
- [Case studies](https://kody.nafigroup.app/blog/early-kody-users): Longer notes from people using Kody — how it shows up in their work, in their words.
- [Where to store API keys for AI agents (not in agent configs)](https://kody.nafigroup.app/blog/where-to-store-api-keys-for-ai-agents): MCP configs and .env files spread API keys across every laptop and agent. Here's how to connect agents to services without putting keys in config files.
- [Kody weekly: Lock integrations, secrets, and MCP servers to packages](https://kody.nafigroup.app/blog/kody-weekly-2026-09-04): Lock grants to named packages and gate publishes, plus 8 more updates and 4 breaking changes to OAuth, OpenAPI, visibility, and hosts.
- [A team lead's guide to AI agent credentials](https://kody.nafigroup.app/blog/ai-agent-credentials-guide-for-team-leads): Who owns the keys when your team's AI agents call real services? A practical model for team, personal, and shared credentials.
- [Your engineers are handing private keys to AI agents. Here's what that means.](https://kody.nafigroup.app/blog/engineers-are-handing-private-keys-to-ai-agents): Every agent your team connects ends up holding real API keys. Here's where those keys hide today and how to keep them out of the model's context.
- [OpenClaw 2 needs a home](https://kody.nafigroup.app/blog/openclaw-2-needs-a-home): OpenClaw 2.0 is a personal AI that lives on your machine. Kody is the runtime that keeps its memory, keys, packages, and jobs running when that machine sleeps. Here's how they stack.
- [How to turn agent work into software you own](https://kody.nafigroup.app/blog/how-to-turn-agent-work-into-software-you-own): Ask once in the agent you already use, persist the working code as a package you own, then trigger it — invoke, job, webhook, or app — without paying the model again.
- [Kody weekly: Choose the OAuth scopes a connection requests](https://kody.nafigroup.app/blog/kody-weekly-2026-08-28): Pick providers and OAuth scopes from /connect/oauth, plus 5 more updates and 2 breaking changes to package composition and jobs.
- [Kody weekly: Browse a package's files before you install it](https://kody.nafigroup.app/blog/kody-weekly-2026-08-21): A read-only files explorer for published packages, plus 7 more updates and 4 breaking changes to connectors, services, values, and tokens.
- [Kody weekly: Connect GitHub, Google, and Slack with built-in OAuth](https://kody.nafigroup.app/blog/kody-weekly-2026-08-14): Built-in OAuth integrations connect providers without your own OAuth app, plus 7 more updates and 2 breaking changes to domains and limits.
- [Kody weekly: Plain repos, with packages as an opt-in](https://kody.nafigroup.app/blog/kody-weekly-2026-08-07): Create plain repos with repo_create and promote one to a package when you need it, plus 7 more updates to onboarding, plans, and status.
- [Kody weekly: Packages can receive webhooks](https://kody.nafigroup.app/blog/kody-weekly-2026-07-31): Packages declare kody.webhooks and you mint a URL per webhook, plus 8 more updates to run history, account pages, billing, and email.
- [Kody weekly: Free and Pro plans with Stripe billing](https://kody.nafigroup.app/blog/kody-weekly-2026-07-24): Pick a Free plan or upgrade to Pro for $5 a month, plus 8 more updates to profiles, search, email, and package storage.
- [Your agents' cloud](https://kody.nafigroup.app/blog/your-assistants-home): Your AI assistant accumulates things worth keeping. Memory, keys, code, scheduled jobs, an inbox. Those things should live somewhere durable that you own, no matter which agent you talk to this year.
- [Gateways connect. Homes accumulate.](https://kody.nafigroup.app/blog/gateways-connect-homes-accumulate): MCP gateways and Kody get compared a lot, but they solve different problems. A gateway is a catalog of tools with pluggable ways to call them. Kody is a runtime where your assistant's stuff lives and keeps running. The difference shows up the moment you try to toggle code mode off.
- [The personal assistant that can't leak your keychain](https://kody.nafigroup.app/blog/the-assistant-that-cant-leak-your-keychain): My assistant's account holds 51 secrets. Here's the security architecture that makes the scary failure modes structurally impossible instead of policy-discouraged.
- [Why Your agents' cloud should make zero inference calls](https://kody.nafigroup.app/blog/zero-inference-calls): Kody makes zero inference calls. That's not a limitation, it's the business model, and it changes who your assistant platform is actually working for.
- [Every install is a fork you own](https://kody.nafigroup.app/blog/every-install-is-a-fork-you-own): In most ecosystems, installing someone's automation means renting a black box. In Kody's community, one-click install creates a fork you own. Here's why that changes how you treat other people's code.
- [The automations you never got around to building](https://kody.nafigroup.app/blog/the-automations-you-never-built): Your real competitor for automation isn't a better tool, it's not automating at all. Why the activation energy of hosting and credentials killed your automations, and what changes when your agent has a durable home.
- [Self-service means ownership](https://kody.nafigroup.app/blog/self-service-means-ownership): Why Kody makes you create your own OAuth apps and bring your own keys, framed honestly. A few minutes of setup buy you your own app, your scopes, your rate limits, and no middleman between you and your data.
- [Kody weekly: Install community packages in one click](https://kody.nafigroup.app/blog/kody-weekly-2026-07-17): Community listings install into your account as live packages in one click, plus 7 more updates to packages, onboarding, and email.
- [Kody weekly: Share packages with the community](https://kody.nafigroup.app/blog/kody-weekly-2026-07-10): Publish packages as public MIT listings others can fork and rate, plus 8 more updates and 3 breaking changes to email, UI, and secrets.
- [Kody weekly: Package tokens carry your remote connectors](https://kody.nafigroup.app/blog/kody-weekly-2026-07-03): Package invocation calls can use your attached remote connectors, plus 3 fixes to jobs and account security.
- [Kody weekly: Repo sessions work on branches in your package repo](https://kody.nafigroup.app/blog/kody-weekly-2026-06-26): Repo sessions now use sessions branches in the source repo, plus 3 more updates to package tokens and errors, and 2 breaking changes.
- [Kody weekly: Manage package invocation tokens in your account](https://kody.nafigroup.app/blog/kody-weekly-2026-06-19): Create, list, and revoke package invocation tokens from your account, plus 1 more update and 1 fix to integrations and secrets.
- [Kody weekly: small fixes and maintenance](https://kody.nafigroup.app/blog/kody-weekly-2026-06-12): package_save spells out its source safety policy, and package remotes and sessions fail clearly on empty sources.
- [Kody weekly: small fixes and maintenance](https://kody.nafigroup.app/blog/kody-weekly-2026-06-05): Generated UI shows real tool errors and next steps, and package sources recover from missing repos.
- [Kody weekly: Read what each package publish recorded](https://kody.nafigroup.app/blog/kody-weekly-2026-05-29): Publishes record Kody publish notes you can read with repo_show_publish_note, plus 1 more update to package and account cleanup.
- [Kody weekly: OAuth reconnects keep working after reauth](https://kody.nafigroup.app/blog/kody-weekly-2026-05-22): Authenticated fetch uses your saved access token and keeps your refresh token name after reauth, plus no other updates this week.
- [Kody weekly: Packages can call each other at runtime](https://kody.nafigroup.app/blog/kody-weekly-2026-05-15): packages.invoke and packages.invokeChecked call another package's current export, plus 8 more updates and 4 breaking changes.
- [Kody weekly: Schedule durable workflows from any code](https://kody.nafigroup.app/blog/kody-weekly-2026-05-08): workflows.create runs code or a package export on a delay from any Kody runtime, plus 8 more updates and 4 breaking changes to review.
- [Kody weekly: Your agent can send and receive email](https://kody.nafigroup.app/blog/kody-weekly-2026-05-01): Kody inboxes store inbound mail and send replies, and packages can react to new mail, plus 8 more updates to packages and secrets.
- [Kody weekly: Skills, apps, and jobs become packages](https://kody.nafigroup.app/blog/kody-weekly-2026-04-24): Saved skills and apps now run as repo-backed packages, plus 8 more updates to jobs, repo editing, search, and realtime.
- [Kody weekly: Schedule code with one jobs system](https://kody.nafigroup.app/blog/kody-weekly-2026-04-17): A unified job_* surface runs your code on cron, interval, or one-time schedules, plus 8 more updates to storage, apps, memory, and repos.
- [Kody weekly: Search finds your saved values and connectors](https://kody.nafigroup.app/blog/kody-weekly-2026-04-10): Search now returns saved values and connectors, plus 2 more updates to outbound email and generated UI rendering.
- [Kody weekly: Connect OAuth providers from a hosted page](https://kody.nafigroup.app/blog/kody-weekly-2026-04-03): A hosted /connect/oauth page stores and refreshes provider tokens, plus 8 more updates to secrets, skills, search, and memory.
- [Kody weekly: Secrets only go to the hosts you approve](https://kody.nafigroup.app/blog/kody-weekly-2026-03-27): Codemode fetch fills in secrets only for approved hosts, plus 6 more updates to saved UI apps, integrations, and fixes.
- [Kody weekly: Saved skills now take parameters](https://kody.nafigroup.app/blog/kody-weekly-2026-03-20): Saved skills can declare typed parameters, plus 3 other updates: GitHub GraphQL access, skill run hints, and mobile layouts.
- [Kody blog: Essays](https://kody.nafigroup.app/blog/category/essays): Why Kody works the way it does, and opinions on agents, ownership, security, and cost.
- [Kody blog: How-to](https://kody.nafigroup.app/blog/category/how-to): Step-by-step setups, checklists, and playbooks for running AI agents with real access.
- [Kody blog: Updates](https://kody.nafigroup.app/blog/category/updates): Weekly release notes and product announcements.
- [Kody blog: Customer stories](https://kody.nafigroup.app/blog/category/stories): People using Kody, in their own words.
- [Kody blog series: Agent credentials for team leads](https://kody.nafigroup.app/blog/series/agent-credentials-for-team-leads): Giving a team’s AI agents real access without handing them the keys: storage, scopes, revocation, audit, sharing, and rollout.
- [Kody blog series: Sharing apps with your team](https://kody.nafigroup.app/blog/series/sharing-apps-with-your-team): Sharing an AI-built app with teammates, contractors, and clients: forks, grants, sign-in, access presets, who an app runs as, and who pays.