OpenContext CLI
A local context store for coding agents that captures project knowledge and reuses it across Codex, Claude Code and OpenCode
- 1,281 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads and writes project files and agent settings
- Deploys MCP and commands into the agent configuration
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/opencontextDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads and writes project files and agent settings
- Deploys MCP and commands into the agent configuration
This is third-party code. Review the repository files before installing.
What it does
OpenContext installs as the oc CLI and layers on top of an agent you already run rather than replacing it. It gathers notes, decisions and project knowledge into a local store and exposes them to the agent through built-in skills and MCP. The oc init command wires commands, skills and an MCP entry into Cursor, Claude Code, Codex and OpenCode. A Tauri desktop app is available for people who prefer a visual interface. Everything stays on the user's machine.
Who it is for. For developers who work across several agents and want context to persist between sessions and repositories.
Good fit when
- You want the agent to remember decisions and project details between sessions
- You use several agents and want a shared knowledge store
- You want context stored locally, without a cloud
Not a fit when
- You need a networked team knowledge server
- One agent's built-in memory is enough
Example request
Save this project's architecture decisions to context and recall them in the next sessionLimitations
It runs on top of your agent and its model and ships no LLM of its own. The desktop app and MCP require Node.js 18 or later.
How to disable. Remove the package with npm uninstall -g @aicontextlab/cli, then delete the opencontext entries from your agents' skill directories and mcp.json.
FAQ
Do I need a separate agent subscription?
No, OpenContext reuses the CLI you already have and its model access.
Where is data stored?
Locally on your machine; there is no separate cloud service.
Discussion
No questions or reviews yet.
Related
CLI toolsUltraContext collects Claude Code, Codex and OpenClaw sessions in one place so agents can see each other's context.
A context database for agents: cross-session memory, documents and skills in one viking:// file tree, reachable through MCP and hooks
An open source coding agent for the terminal and desktop with build and plan modes
Orchestrator plugin for OpenCode and Codex CLI: multiple agents, hooks, built-in MCPs, ultrawork mode and hash-anchored edits
OpenWolf
openwolf
A shared local project memory for Claude Code, Codex and OpenCode: task context, a project map, token accounting and a localhost dashboard
ContextLattice: a local context layer for agents
ContextLattice
A local memory and context layer: a session's goal, decisions and evidence are gathered into a compact packet an agent reopens
README in short
The README presents OpenContext as persistent memory for an assistant: install the CLI, run oc init, and the tool adds commands, skills and an MCP entry to Cursor, Claude Code, Codex and OpenCode. Besides the CLI there is a desktop app for working with the knowledge base visually. The project is written in JavaScript and Rust and ships under the MIT license.