Koed helps your AI coding tool remember useful context from previous work, so it can bring back project decisions, debugging history, and other details when you need them.
Important
Codex is currently the only supported AI Client integration for capture and recall. Claude Code can attach through an experimental recall-only setup; see Claude Code integration.
- macOS, Linux, or WSL.
- Node.js and pnpm.
- Homebrew for the source-checkout bundled-local runtime install. Packaged Desktop can use packaged native runtime assets; external dependency mode does not require Homebrew.
- Codex installed and signed in.
If you are on Windows, run Koed inside WSL as Linux tooling. Keep KOED_HOME
and checkout paths on Linux filesystem paths inside WSL; native Windows
packaged app support is not shipped in this build.
From a fresh clone, run:
pnpm install
pnpm local:setup
KOED_DEPENDENCY_MODE=bundled-local KOED_AUTO_PORTS=1 pnpm desktop:startpnpm local:setup prepares .env, builds the workspace, links the Homebrew-backed bundled-local runtime, and installs the default embedding model.
Koed Desktop opens when setup is complete and configures Codex automatically.
Packaged Desktop follows the same local-personal bundled-local flow, but it
starts its managed koed-server from the app bundle, prefers packaged native
runtime assets, and keeps KOED_HOME state outside the source checkout. See
Koed Desktop for packaged first-run,
signing/notarization, and smoke details.
If setup fails with a path like /path/to, unset any placeholder overrides
from previous experiments before restarting Desktop:
unset KOED_HOME KOED_EMBEDDING_MODEL_PATH KOED_RERANKER_MODEL_PATHTo stop Koed later:
node packages/koed-server/dist/cli.js stop --jsonThe README keeps to one basic local path. For other options, see:
- Running Koed for external dependency mode, manual server commands, alternate ports, smoke tests, packaged first-run notes, and desktop development.
- Configuration for environment variables, runtime modes, model overrides, logging, and production settings.
- Codex integration for manual Codex setup and recovery.
- Claude Code integration for the experimental recall-only Claude Code setup.
- Curated Memory for source-linked durable facts and recall behavior.
- Security, Backup and restore, and Upgrades for operational guidance.
For local Desktop, private VPS, Team Self-Hosted, and cloud deployment
language, use koed-server plus dependencies as the product boundary. API,
Worker, and Explorer remain useful implementation names for code, logs, and
troubleshooting.
Koed assumes the operator controls the deployment. The API supports bearer API
tokens for AI-client integrations. Local operators create tokens with
pnpm api-token:create, which uses trusted database access and stores only token
hashes. Postgres and Redis should stay on private Docker/internal networks in
production deployments. See docs/security.md.
Local personal deployments may keep operational Memory rows in Postgres unless app-layer encryption is configured. Private VPS, Team Self-Hosted, and Koed-managed cloud deployments should configure envelope encryption for human-readable Memory and evidence payloads; queryable vectors still remain sensitive trusted-boundary data. Protect the database, volumes, backups, and administrator access with deployment-level controls.
Report suspected vulnerabilities privately. See SECURITY.md for supported versions, the reporting channel, and guidance on not disclosing user Memory data publicly.
Use normal Postgres backups and restore into the same Koed version before upgrading. The API runs database migrations during startup.
Local Operators can also run the same Drizzle migration path manually with:
pnpm --filter @koed/db migrate:upSee docs/backup-restore.md, docs/hosted-backups.md, and docs/upgrades.md.
Koed uses one product release version for the self-hosted distribution. Add a changeset for release-noteworthy changes:
pnpm changesetSee docs/upgrades.md for upgrade guidance.
Koed is licensed under the GNU Affero General Public License version 3 only
(AGPL-3.0-only). See LICENSE, CONTRIBUTING.md,
and docs/license.md. See
Commercial Feature Boundary for the
launch recommendation on public distribution, Team Self-Hosted, hosted-only
services, and managed add-ons.