Context Autopilot

What is Context Autopilot?

Automated context collection for coding agents. It mines real agent sessions — every instruction repeated, every correction made, every tool call rejected — and distills them into CLAUDE.md / AGENTS.md rules you approve. Runs 100% locally as a CLI and MCP server.

How to use Context Autopilot?

Install via npm install -g context-autopilot or use npx. Run ctxlayer scan to mine signals from local session transcripts (Claude Code and Cursor), ctxlayer distill to convert signals into proposals via your existing Claude CLI, and ctxlayer apply to review and write accepted rules. Also supports a Claude Code plugin and an MCP server for in-chat use.

Key features of Context Autopilot

• Mines session history for repeated instructions, corrections, and rejected tool calls.
• Distills signals into imperative, project-specific rules backed by verbatim evidence.
• Interactive approve/reject flow; never writes context files without your decision.
• Writes managed blocks into both CLAUDE.md and AGENTS.md.
• Global mode mines all projects for personal working preferences.
• Staleness check (ctxlayer stale) finds context file references the repo has outgrown.

Use cases of Context Autopilot

• Prevent re‑teaching agents the same conventions every session.
• Enforce project‑specific constraints (e.g., “staff login cannot access admin view”).
• Capture cross‑session patterns that no single live session can observe.
• Maintain a personal, cross‑project set of preferences for how you like to work.
• Add a CI step that flags stale context entries (missing files, removed npm scripts).

FAQ from Context Autopilot

How is this different from Claude Code's /insights?

/insights is a personal usage report with hand‑copy suggestions for Claude Code only. Context Autopilot provides a full pipeline: mines Cursor history too, attaches verbatim quotes as evidence, runs an approve/reject flow, writes managed blocks to both CLAUDE.md and AGENTS.md, offers global cross‑project rules, and includes a CI staleness check. Fully open source and local.

How is this different from Claude Code's auto‑memory?

Auto‑memory captures what the model notices live in a single session. Autopilot is retroactive and systematic: it mines months of existing history across tools and finds cross‑session patterns (e.g., you said it six times in four sessions) that no single live session can see.

Where does my data live?

Everything runs on your machine. Transcripts are parsed locally. Only extracted signals (short quotes of your own instructions) are sent to the model you already use for coding. Nothing is uploaded anywhere else.

What are the runtime requirements?

The CLI requires Node.js. Cursor session mining uses Node's built‑in node:sqlite (Node 22+; on older Node, the Cursor source is skipped gracefully). No external API key is needed for distillation—it uses your existing claude CLI.

How does the MCP server work?

Configure it in your MCP client with npx -y -p context-autopilot ctxlayer-mcp. It exposes tools like scan_context_signals, distill_context_proposals, apply_context_proposals, and find_stale_context. The approval loop closes entirely inside chat: the tool returns each proposal with evidence and asks you which to accept; apply_context_proposals writes only the ones you approve.