One source of truth, every agent.
Engrym gives Claude Code, Cursor, Codex, and Gemini the decisions and constraints relevant to their work — then records whether the code still honors them. Agents check code locally; Engrym keeps the verdict, never your source.
Stores your decisions, never your source.
The check in the loop, not another markdown file.The check in the loop, not another markdown file to keep in sync.
WORKS WITH
- CCClaude Code
- CuCursor
- CxCodex CLI
- GPChatGPT
- GmGemini
Every agent works from the same project decisions.
Your project decisions, available to every agent.
Engrym holds the decisions, conventions, constraints, and context that define your project. Each agent receives only what applies to the file, feature, or task in front of it — so no session starts from scratch, and no two agents work from a different version of the truth.
PROJECT KNOWLEDGE · 47
Use Hono for the public REST API
decision · upheld
Every table enforces row-level security
constraint · 1 violation
Responses use the {data, meta} envelope
convention · uncertain
Extraction runs on your own provider key
context · reference
LIGHTER CONTEXT
A smaller context pack, not the whole document.
When an agent asks Engrym what was decided, it gets just the relevant decisions and constraints — not a wall of source documents to wade through. On a live query against our own project, a typical context pack came back at about 2,721 tokens instead of ~45,000 — roughly 16.5× smaller, and about 8.6× lighter than having the agent read the source document the old way. Smaller packs cost less and leave more room for the work.
Obsidian vault (ZIP)
268 notes · imported
Markdown folder
50 files · extracting…
STEP 1
Write normal Markdown. Engrym structures it for agents.
Bring your existing project knowledge in by importing an Obsidian ZIP or a folder of Markdown files. Engrym reads it and organizes it into decisions, conventions, constraints, and context — using your own AI provider account for extraction. Nothing to re-key, no lock-in.
$ engrym sync
✓ Connected to your project
✓ 47 decisions and constraints available to agents
✓ Watching the docs folder — source code stays local
STEP 2
Change agents without losing project context.
Connect Claude Code, Cursor, Codex, Gemini, and other MCP-compatible agents to the same project knowledge. Each agent queries Engrym at session start and retrieves the decisions and constraints relevant to its task — so switching tools never means re-explaining the project.
architecture.md updated
re-read · 3s ago
New constraint proposed
“Freeze the SDK envelope” · awaiting review
STEP 3
Keep documented knowledge current as the work moves.
Engrym synchronizes your project documentation folder — not your source code. When a document changes, it re-reads the affected sections and surfaces new or updated knowledge for review. Approved knowledge is then available to every connected agent.