ai-context-bridge
Stop re-explaining your code. Switch between AI coding tools in 10 seconds.
MCP server • Claude Code plugin • Session search • 11 AI tools • Zero dependencies
npm i -g ai-context-bridge
The Problem
You're deep in a coding session with Claude Code. Rate limit hits. You can't even run a save command — the session is dead. Switch to Cursor? You'd have to re-explain everything from scratch.
76% of developers now use 2+ AI coding tools (Stack Overflow 2025). If you switch 3-5 times a day, that's 45-75 minutes wasted re-explaining context every single day.
Working on multiple projects side by side? Every tool has its own config format. Context doesn't transfer.
The Solution
Three steps. Then it's autonomous forever.
# 1. Install
npm i -g ai-context-bridge
# 2. Initialize
cd my-project
ctx init # Private repos — stores context in .ctx/ inside the project
ctx init --external # Public repos — stores context in ~/.ctx-global/ (zero files in repo)
# 3. Work normally. Context auto-saves on every commit.
# When a rate limit hits, resume prompts are already waiting:
# .ctx/resume-prompts/cursor.md
# .ctx/resume-prompts/codex.md
# .ctx/resume-prompts/claude.md
See it in action
ctx init
ctx switch
How It Stays Autonomous
| Trigger | What Happens | You Do Nothing |
|---|---|---|
git commit | Auto-saves context, refreshes all resume prompts | Yes |
git checkout | Updates branch context, refreshes prompts | Yes |
git merge | Updates context with merge state | Yes |
ctx watch | Background watcher refreshes every 30s + on file changes | Yes |
| Rate limit hits | Resume prompts already in .ctx/resume-prompts/ | Just open & paste |
The Rate Limit Scenario (Solved)
Before ctx: Rate limit hits → session dead → open Cursor → re-explain everything → 15 min wasted
With ctx: Rate limit hits → open .ctx/resume-prompts/cursor.md → paste into Cursor → keep working in 10 seconds
Key Features
Autonomous Context Saving
Git hooks auto-save your session on every commit, checkout, and merge. Resume prompts for all 11 tools are pre-generated and always ready. Zero workflow change required — rate limit recovery is instant.
External Storage for Public Repos
ctx init --external stores all context data in ~/.ctx-global/ instead of the project directory. Zero ctx files in your repo — perfect for open-source contributors who don't want to push session data accidentally.
Multi-Project Dashboard
ctx projects list shows all your initialized projects with branch, task, and last activity. Track your entire dev workflow across repos from one place.
Projects (2)
project-a [feature/auth] (live)
~/project-a (git) — Implementing JWT auth
Last active: 5m ago
project-b [main] (live)
~/project-b (git) — Building dashboard
Last active: 2h ago
Session Search
ctx search <query> uses TF-IDF ranking to find any past session by keyword. Filter by branch, see relevance scores, and find exactly what you were working on last Tuesday.
MCP Server
ctx-mcp exposes 5 tools to any MCP client — Claude Desktop, Windsurf, or any app that speaks the Model Context Protocol. Save, switch, search, and check status without leaving your AI tool.
Claude Code Plugin
Install with claude plugin install ctx@ai-context-bridge to get /ctx:save, /ctx:switch, /ctx:status, and /ctx:search as slash commands inside Claude Code. Context portability without switching windows.