KeepContext

· Changelog · AGPL-3.0

One self-hosted memory for every AI app you use. Tell ChatGPT an idea, and Claude Code, Cursor and Gemini know it too. Start a task in Claude Code, and when it hits its usage limit, Codex continues from where it stopped.

KeepContext is a small server with a web dashboard and one MCP endpoint. ChatGPT, Claude (web, desktop, Claude Code), Gemini (web, CLI), Cursor, Codex, GitHub Copilot and Antigravity all connect to it. Your data stays on your machine or server.

What it does

• One memory for all your AI apps. Ideas, decisions, todos, notes, standing instructions ("keep answers short") and facts about you. Every connected app loads them with get_context and adds to them with save_entry.

• Continue anywhere. For multi-step coding work, apps start a task and save a short checkpoint after each step on the task's git branch. When one app hits its limit, another says "resume my task" and gets the goal, the next steps, the branch and the history. Later, the first app can review what the others did.

• Know which app did what. Each app and account gets its own token, so the dashboard shows verified badges (ChatGPT · personal, Claude Code, Cursor…) instead of trusting what a model says about itself. Rotate or revoke one app without touching the others.

• Private by design. Self-hosted, with private entries and tasks that never go to apps connected by URL. Tokens are stored only as hashes, there are rate limits, and GitHub access is read-only.

• Your work log (optional). Connect GitHub (read-only) to see commits and pull requests per day in an activity log, ready to copy into a status report or CV notes.

Related MCP server: samskriti-project

Quick start

Docker

docker run -d --name keepcontext -p 8787:8787 -v keepcontext-data:/data ghcr.io/darshanbajgain/keepcontext:latest
docker logs keepcontext      # shows a one-time setup code

Open http://localhost:8787, enter the setup code, and choose a password. That's all the configuration there is.

Want to look around first? docker run --rm -p 8787:8787 -e DEMO=1 ghcr.io/darshanbajgain/keepcontext:latest starts a demo with a fictional developer (the password is on the login page).

Reach it from ChatGPT, Claude and Gemini on the web

Web apps need a public HTTPS address. The compose file has two built-in options:

Or put it behind your own domain with Caddy or Nginx (self-hosting guide). Coding apps on the same machine work with plain http://localhost:8787.

Without Docker

Node 22.13 or newer: npm install && npm start, then open http://localhost:8787. The setup code is printed in the terminal.

Connect your apps

In the Apps tab, Add a connection for each app (and account). It shows that app's setup once:

Step by step, with troubleshooting: docs/CONNECT_APPS.md.

Tell your apps to use it

Connected isn't the same as used. Add this once to each app's personal instructions:

## KeepContext: my shared memory across AI apps
- At the start of a task, call `get_context` from the keepcontext MCP server (pass `repo` = the repository name) and follow its standing instructions.
- Before asking me for background, use `search_context`.
- Save new ideas, decisions, todos and notes with `save_entry`.
- For multi-step work, `start_task`, then `checkpoint_task` after each step, so another app can continue with `resume_task` if you stop. At the start, check `list_open_tasks`.
- Never print tokens or the secret `/mcp/k/…` URL.

This lives in your home folder, so every project is covered and nothing is committed to any repo. For a single repo, the Repo files tab generates AGENTS.md / CLAUDE.md / GEMINI.md / Cursor rule files instead.

MCP tools

Security and privacy

• Your server, your data. Everything is in one SQLite file in the data volume. Nothing is sent anywhere except to the AI apps you connect, to GitHub's API if you connect it (read-only), and to one Google Doc if you turn on the optional mirror (never private entries).

• Tokens: each app has its own token, stored only as a SHA-256 hash and shown once. The admin password is hashed with scrypt. A one-time setup code stops anyone else from claiming a freshly started server.

• Private entries and tasks stay in the dashboard. Apps connected by a secret URL (the web apps) never receive them; header-based apps only when you allow it per connection. Tasks for repos KeepContext doesn't sync (for example work repos) are private automatically.

• Rate limits on failed logins, wrong tokens and requests per app.

• Treat secret URLs like passwords. If one leaks, rotate that connection in the Apps tab.

Details: docs/ARCHITECTURE.md §6. To report a vulnerability, see SECURITY.md.

Configuration

Nothing is required. The setup page and the Settings tab cover the password, your name, timezone and GitHub. Every setting can also be set as an environment variable or in .env; those win over the UI. See .env.example and docs/ARCHITECTURE.md §7. Backups, updates and running without Docker: docs/SELF_HOSTING.md.

FAQ

Does it need GitHub? No. Without it, KeepContext is a shared memory with tasks. GitHub adds the activity log and the Projects tab.

Does it work on the ChatGPT free plan? Yes, as a custom plugin (checked November 2026). Set the plugin to "Allow all tools", or ChatGPT asks before every save.

Can I run it on a Raspberry Pi? Yes. The image is published for arm64 too.

How is this different from each app's own memory? Each app's memory stays inside that app. KeepContext is one memory that every app reads and writes, on your own server, and it can hand a task from one app to another.

Contributing

Issues and pull requests are welcome; see CONTRIBUTING.md. Run npm test before opening a pull request.

License

AGPL-3.0. You can use, self-host and modify KeepContext freely. If you offer a modified version to others as a network service, you must publish your changes under the same license.