@kentcdodds: Can you believe this was done in a single day by a solo dev? https://github.com/kentcdodds/kody/releases/tag/v2026.08.1…
Summary
Kody is a portable personal assistant platform for AI agents, built on Cloudflare Workers and Model Context Protocol, enabling memory, code, and automation management across hosts.
View Cached Full Text
Cached at: 08/19/26, 08:54 PM
Can you believe this was done in a single day by a solo dev? https://github.com/kentcdodds/kody/releases/tag/v2026.08.19… What a time to be building software!
kentcdodds/kody
Source: https://github.com/kentcdodds/kody
Your assistant's home — the memory, keys, code, and automations your AI agent keeps, portable across every MCP host. Built on Cloudflare Workers.
Kody is your assistant’s home—the memory, keys, code, and automations your AI
agent keeps, portable across every MCP host. Built on Cloudflare Workers and the
Model Context Protocol (MCP), it ships a Remix UI, Worker-based request routing,
package runtime plumbing, and OAuth-protected MCP endpoints. The project favors
a compact MCP surface with powerful search and Code Mode execute flows over
a large static tool catalog.
Kody is a multi-user personal assistant: each signed-in user gets a fully isolated assistant (packages, jobs, secrets, values, memories, and related state). Tests and fixtures may seed deterministic local accounts, but no account is privileged at runtime. The repo follows several epicflare starter conventions.
The repo is organized as an Nx monorepo, with shared modules in
packages/shared (@kody-internal/shared), the main app worker under
packages/worker, and mock Workers under packages/mock-servers/*.
Quick Start
npm install
npm run dev
The dev server runs at localhost:3742 by default (the CLI picks the next free
port and prints the resolved URL). Wrangler handles the local Cloudflare Workers
runtime and D1 database automatically.
To scaffold a new project from the epicflare template instead, run
npx create-epicflare.
See
docs/contributing/getting-started.md
for the full setup paths and expectations. Contributors and agents should start
with AGENTS.md for repo-specific guidance.
If you are trying to understand what this repository is for, start with
docs/contributing/project-intent.md.
Tech Stack
| Layer | Technology |
|---|---|
| Runtime | Cloudflare Workers |
| UI Framework | Remix 3 (beta) |
| Package Manager | npm |
| Workspace | Nx + npm workspaces |
| Database | Cloudflare D1 |
| Session/OAuth | Cloudflare KV |
| MCP State | Durable Objects |
| E2E Testing | Playwright |
| Bundler | esbuild |
Scope
- Fair Source personal assistant platform, not a general-purpose agent harness
- MCP-first architecture intended to work across compatible AI agent hosts
- Compact MCP surface area preferred over a large static tool inventory
- ChatGPT is a likely primary host target, while keeping the server usable from other MCP hosts where practical
How It Works
Request → packages/worker/src/index.ts
│
├─→ OAuth handlers
├─→ MCP endpoints
├─→ Static assets (`packages/worker/public/`)
└─→ Server router → Remix components
packages/worker/src/index.tsis the entrypoint for Cloudflare Workers- OAuth requests are handled first, then MCP requests, then static assets
- Non-asset requests fall through to the server handler and router
- Client assets are bundled into
packages/worker/public/and served via theASSETSbinding
Documentation
| Document | Description |
|---|---|
docs/contributing/getting-started.md | Setup, environment variables, deploy |
docs/contributing/environment-variables.md | Adding new env vars |
docs/contributing/cloudflare-offerings.md | Optional Cloudflare integrations |
docs/contributing/project-intent.md | Scope, goals, and non-goals |
docs/contributing/index.md | Developing and extending Kody |
docs/use/index.md | Using Kody over MCP |
docs/contributing/setup.md | Local development and verification |
Contributing
Outside pull requests to this repository need a signed inbound Contributor License Agreement. Community packages stay MIT and do not use that CLA.
See CONTRIBUTING.md and
docs/contributing/index.md.
License
Kody is licensed under the Functional Source License, Version 1.1, ALv2 Future License (FSL-1.1-ALv2). You can use, copy, modify, create derivative works from, publicly perform, publicly display, and redistribute the software for any purpose other than Competing Use. Competing Use means making the software available to others in a commercial product or service that substitutes for Kody, substitutes for another product or service the licensor offers using Kody that existed when the version was made available, or offers the same or substantially similar functionality. Each version becomes available under the Apache License 2.0 on the second anniversary of the date that version was made available.
Community packages published through Kody remain MIT-licensed; that requirement is separate from this repository’s license.
Similar Articles
@kentcdodds: This is now built into Kody to make setting up new integrations a lot more straightforward for your agents https://gith…
Kody is an experimental personal assistant platform built on Cloudflare Workers and MCP; a recent update simplifies integration setup for agents.
@kentcdodds: The questions I keep getting about @kodykoala: https://heykody.dev/guides/what-is-kody…
Kody is a Fair Source personal assistant platform that connects your existing AI agent to persistent memory, credentials, scheduled jobs, and reusable code, turning one-off agent work into permanent automations.
@kentcdodds: Man this is so clutch. I don't know how I ever would have figured out this friction agents are experiencing without the…
Kent C. Dodds highlights a debugging feature in Kody, an open-source AI agent platform built on Cloudflare Workers and the Model Context Protocol (MCP), designed to manage memory and automations for agents across hosts.
@kentcdodds: I made a Kody discord. Then I wired up Kody to manage it and goodness it's so much better telling an agent to do stuff …
Kent C. Dodds shares his experience creating a Discord server for Kody and using the AI agent to manage it, finding it more efficient than manual UI interaction.
@kentcdodds: I'm moving from heykody[.]dev to http://heykody.app because Kody is really for more than just devs.
Kent C. Dodds announces Kody is moving to heykody.app, positioning it as an AI agent that integrates with existing assistants like Cursor and Claude Code to securely access services and run automated jobs such as Slack catch-up, week planning, and GitHub triage.