Practical overview
When it fits
Use Engrim when coding-agent context needs to persist between sessions or move with a project across supported assistants.
Who it is for
- Developers who want project decisions and constraints to persist across coding-agent sessions.
- Teams or individuals switching among supported coding assistants on the same codebase.
Documented uses
- Keep architectural decisions, user constraints and project state available after a session reset.
- Share a project's stored context across supported coding assistants.
- Configure agent hooks and MCP connections for memory capture and recall.
Requirements & limits
Engrim is available as a Python package and is identified by its public repository as MIT-licensed open-source software. The README requires Python 3.10 or later.
- Engrim is a local CLI and SQLite memory layer, not an AI coding assistant or model.
- Setup differs by assistant: integrations include lifecycle hooks, guidance files and MCP, and MCP is optional for Codex CLI.
- The documented workflow uses Python 3.10 or later.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Engrim and configure detected agent environments
Install the CLI and run its documented automatic setup for agent environments detected on the machine.
Before you start
- Python 3.10 or later
- A command-line environment
- One or more supported agent environments installed
Steps
Install Engrim with the command below.
pip install engrimRun
engrim setupwithout arguments to detect and configure supported environments.
Expected outcome
Engrim is installed and its setup process configures detected supported agent environments.
Guide limitations
- Automatic setup covers environments detected from their documented configuration directories; the exact integration differs by assistant.
- This guide covers installation and setup, not verification that an integration works in a running assistant.
Configure Engrim for Codex CLI
Set up Engrim's Codex CLI hooks and guidance, with MCP available as an additional configuration.
Before you start
- Engrim installed
- Codex CLI
Steps
Run
engrim setup --codexto configure Codex hooks and managed guidance.If MCP tools are wanted, run
engrim setup --codex-mcporengrim setup --codex --codex-mcp.For MCP, use
/mcpto check the server and open a new Codex session so hooks and guidance load.
Expected outcome
Engrim's documented Codex hooks and guidance are configured; the optional MCP server can expose Engrim tools.
Guide limitations
- Codex hooks must be reviewed and trusted with Codex's
/hookscommand before they run. - The
/mcpcheck and new-session instruction apply when enabling MCP.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Engrim | Keep architectural decisions, user constraints and project state available after a session reset. | CLI, Self-hosted | Engrim is available as a Python package and is identified by its public repository as MIT-licensed open-source software. The README requires Python 3.10 or later. |
| Continuum — pouyahasanamreji | Store project lessons so coding agents can retrieve them across conversations. | CLI, Self-hosted, Server | The repository documents local Docker Compose and bare-metal development setups. Bare-metal startup requires Node 22.12.0 or later and pnpm 10.33 or later; the Compose path skips these host prerequisites. |
| Haft | Record the problem a project is solving and the options considered. | CLI, Self-hosted |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 12 October 2026
- Original website title
- timgordontg/engrim · Official homepage title · retained in its source language

