kody

Kody is Your agents' cloud: the memory, keys, code, and automations your AIagent keeps, portable across every MCP host. Built on Cloudflare Workers and theModel Context Protocol (MCP), it ships a Remix UI, Worker-based request routing,package runtime plumbing, and OAuth-protected MCP endpoints. The project favorsa compact MCP surface with powerful search and Code Mode execute flows overa large static tool catalog.

Kody works for individuals and teams (orgs, teams, grants): each account holdsisolated packages, jobs, credentials, memories, and related state. Tests andfixtures may seed deterministic local accounts, but no account is privileged atruntime. The repo follows severalepicflare starter conventions.

The repo is organized as an Nx monorepo, with shared modules inpackages/shared (@kody-internal/shared), the origin app worker underpackages/worker, sibling workers under packages/platform-worker,packages/runtime-worker, and packages/jobs-worker, and mock Workers underpackages/mock-servers/*. Production topology lives indocs/contributing/architecture/index.md.

Quick Start

npm install
npm run dev

The dev server runs at localhost:3742 by default (the CLI picks the next freeport and prints the resolved URL). Wrangler handles the local Cloudflare Workersruntime and D1 database automatically.

To scaffold a new project from the epicflare template instead, runnpx create-epicflare.

Seedocs/contributing/getting-started.mdfor the full setup paths and expectations. Contributors and agents should startwith AGENTS.md for repo-specific guidance.

If you are trying to understand what this repository is for, start withdocs/contributing/project-intent.md.

Tech Stack

Scope

• Fair Source platform for individuals and teams, not a general-purpose agentharness
• 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 fromother MCP hosts where practical

How It Works

kody.codes  → kody-production (origin: Remix, /mcp HTTP, OAuth, email, queues)
                 ├─→ kody-platform  (MCP / mailbox / meter / repo-session DOs)
                 ├─→ kody-runtime   (package apps, invoke API, StorageRunner)
                 └─→ kody-jobs      (cron + JobManager; calls back via JobsHost)

kody.run    → kody-runtime (package-app zone routes)

• packages/worker/src/index.ts is the origin entrypoint; platform, runtime,and jobs have sibling entrypoints (seearchitecture)
• 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 theASSETS binding

Documentation

Contributing

Outside pull requests to this repository need a signed inboundContributor License Agreement.Public packages do not use that CLA.

See CONTRIBUTING.md anddocs/contributing/index.md.

License

Kody is licensed under theFunctional Source License, Version 1.1, ALv2 Future License(FSL-1.1-ALv2). You can use, copy, modify, createderivative works from, publicly perform, publicly display, and redistribute thesoftware for any purpose other than Competing Use. Competing Use means makingthe software available to others in a commercial product or service thatsubstitutes for Kody, substitutes for another product or service the licensoroffers using Kody that existed when the version was made available, or offersthe same or substantially similar functionality. Each version becomes availableunder the Apache License 2.0 on the second anniversary of the date that versionwas made available.

Public packages published through Kody do not use this repository's CLA and haveno license gate; that is separate from this repository's license.