Infernoflow MCP server

🔥 infernoflow

Every new AI session starts cold — the gotchas you found, the decisions you made, don't survive. infernoflow makes them stick.

Persistent memory for AI coding sessions. Captures the gotchas, decisions and dead ends your code can't tell an agent — and replays them into your next Cursor / Claude Code / Copilot chat so the same wrong turn never happens twice.

You spent 90 minutes yesterday teaching Claude that your auth API returns 200 even on errors — check the response body, not the status code. Today you ask the same kind of question and watch it write if (response.ok) { return data } all over again. The AI didn't get worse overnight. It just doesn't have memory.

infernoflow is a local-first CLI + VS Code extension + open protocol (AMP) that gives your AI persistent context across sessions. No SaaS. JSONL on disk. Three rule files your IDE already reads.

What's new in 0.46

• Fresh memory every Claude Code session — a SessionStart hook injects current memory (framed as information to verify, not instructions); CLAUDE.md no longer carries a copy that goes stale.
• infernoflow resume — "where were we?" in one call. Claude Code also leaves an automatic local resume point when a session ends.
• Stale and resolved entries — entries about a file that changed since are marked may be stale; infernoflow resolve retires one from AI context.
• Review what arrives through git (0.46.1) — memory added by teammates is listed until you review it, and the GitHub Action shows memory changes in each PR.
• Safer by default — only read-only MCP tools are pre-approved; the memory-keeper agent is limited to single infernoflow commands; secrets are redacted; MCP is registered per project.
• infernoflow doctor --e2e (0.46.3) — an end-to-end self-test in a throw-away sandbox: CLI, the MCP server with every tool called, the prompt and session hooks, git drift, attribution. Also: prompt hooks ignore agent/tool text, memory-mode projects aren't offered contract tools, git drift reports git failures, and every entry names who wrote it.

Full list: CHANGELOG.md.

Session bookmarks

Drop a named resume point mid-session. When the context window fills up or you're about to make a risky change, one command captures the current session's transcript and stores it as a jumpable checkpoint:

infernoflow bookmark "before the SP refactor"

Or just say it in chat — the Cursor beforeSubmitPrompt hook catches phrases like "bookmark this" / "mark this point" / "save this checkpoint" and drops the bookmark itself, no AI cooperation required. Or let the AI do it via the amp_bookmark MCP tool when it notices the session is getting long.

No --note? infernoflow reads Claude Code's own on-disk transcript (~/.claude/projects/…/*.jsonl), distills the last 40 turns to markdown, and stores it as the bookmark's context. Fully deterministic — no model call. Recall any time:

infernoflow bookmark list                # ● has context, ○ marker only
infernoflow bookmark show "SP refactor"  # jump back — see the whole snapshot

Bookmarks are never auto-pruned, and they surface in infernoflow switch under a ## 🔖 Bookmarks — Resume Points section so the next session opens right where work paused.

Shortened. The full README is on GitHub.