Using Kody

Kody is the personal assistant platform for builders who would rather own their automations than rent them.

Kody gives your AI assistant secure, reusable access to your services and lets it run durable Worker-native automations while your computer is offline.

These docs are for people who connect their assistant to Kody over MCP. Setup and repository development live elsewhere (contributing docs). The in-app Get started page (/onboarding) connects a host, gives that agent access, then proves the same home works from a second agent. People with a Kody account can also join the Discord.

Read in order for a full tour, or jump to a topic.

Docs

The user-facing docs site is kody.codes/docs: an introduction, Get started, Concepts, Examples, Packages, Integrations, and per-provider connection walkthroughs. Every page is also raw markdown (/docs/<slug>.md), indexed at kody.codes/llms.txt, and available to connected agents as search({ entity: "guide:{id}" }). The pages below are the MCP-level reference detail those docs link into.

• What is Kody? — the introduction: what Kody is and is not, what you cannot get elsewhere, the building blocks
• Search and execute — the two MCP tools: find the right thing, then run it
• Connect your agent — the three-step Get started flow for people
• Shared memory, Secrets, Custom secret providers, and Jobs, workflows, and webhooks — concept docs for the primitives every connected agent shares
• Flake Hunter, Sentry Issues, Agent inbox, and Purchase thanks — homepage Trigger it cards as worked examples (cron, webhook, email, event)
• Connect a provider — verified walkthroughs for connecting Discord, GitHub, Google, and other providers to Kody
• How Kody works — ask once, save an export, daily email only when something shipped
• The Kody factory map — the primitives your assistant gets and the boundary around local files and processes
• Packages, integrations, and MCP servers — when those three look interchangeable
• Gmail drafts without send — lock a drafts-only package when Google cannot issue a drafts-only token
• Lock an MCP server to a package — keep kody.mcp["name"] off execute and other packages
• Connect a home MCP server — run a local MCP process (vault, CLI, or home devices), publish it with Tunnel and Access, and connect it to Kody. Starter: home-mcp-starter
• Connect your agent (host notes) — per-host install steps and the setup prompt. Machine-readable twin: /auth.md
• Connect remote MCP servers — add external MCP servers so Kody can call their tools (kody.mcp[...])
• First steps — what to ask Kody to do
• Search
• Execute and workflows — includes per-user MCP instruction overlays and package imports
• Workflows
• Packages
• Share a package — invite another paid account to use a package (accept required; pin or follow)
• Runtime and efficiency — unique Dynamic Worker days by surface, and how the acting user plus a stable module graph reuse one isolate per UTC day
• Offload work that does not fit a Worker isolate — large npm graphs (PDF.js-class libraries) stay out of the package isolate; the owner operates a container or machine and the package calls it
• Public packages — share, browse, and fork published packages on the same deployment; public catalogs live at /@username
• Repo-backed editing sessions
• Raw MCP content blocks
• Secrets and host approval — includes external provider placeholders ({{secret/<provider>:<ref>}}); usage: Custom secret providers
• Email primitives — the per-user inbox, verified destinations, notify-self sends, and replies
• Inbound webhooks — user-owned HTTPS endpoints that dispatch provider POSTs to a saved-package export
• Package apps — Worker fetch contract, session handoff, packageAppFetch smoke, Remix recipe, lean forks
• Package app fetch — platform-marked real-surface app_fetch smoke tests after publish
• Synthetic event dispatch — interactive MCP post-publish smoke test for one subscription handler
• Waiting — current-state items only you can clear (/account/waiting and waitingSummary)
• Activity — failures and recent runs for jobs, apps, webhooks, and other runtimes (/account/activity and the runs MCP capabilities)
• Plans and pricing — every plan is the whole factory; paid plans raise the caps
• Mutating actions and confirmations
• Privacy — what Kody stores, how connected accounts work, and what deployment admins can see (Terms and Acceptable Use are in-app at /terms)
• Troubleshooting — /support and common MCP issues
• Memory and conversation context
• Community Project mark — logo for unofficial integrations and community-built tools

Contributing to these docs

Authors and maintainers follow Documentation principles. Usage pages stay short; the MCP server favors concise tool descriptions and puts detail where it belongs after each tool runs.