The Problem
You're deep into solving a problem with Claude Code. Credits run out — no warning, mid-sentence. You switch to Gemini. Now you have to explain everything again from scratch.
Session Bridge AI fixes this.
It maintains a running SESSION.md in your project — automatically capturing git diffs, open files, and your progress notes — always ready to hand off to any AI tool so you continue exactly where you left off.
Features
- 🤖 Multi-provider — works with Gemini, Claude, and OpenAI
- 📂 Git diff capture — automatically includes recent code changes
- 👁️ Open files capture — includes context from your currently open files
- ⚡ Auto-save — context saved automatically every N logged messages
- 💾 Manual save — save anytime via status bar button or command palette
- 🔒 Secure key storage — API keys stored in VS Code secret storage, never in plaintext
- 📦 Persistent buffer — context survives VS Code restarts
- ⚙️ Configurable threshold — set auto-save threshold to any value (minimum 2)
Setup
1. Install the extension
Search Session Bridge AI in VS Code Extensions or install from the Marketplace.
2. Get a free API key
3. Set your provider and API key
Ctrl+Shift+P → Session Bridge: Set Gemini API Key
Commands
| Command |
Action |
Session Bridge: Log Message |
Log what you're currently working on |
Session Bridge: Save Context Now |
Generate/update SESSION.md immediately |
Session Bridge: Set AI Provider & API Key |
Set provider and API key |
Session Bridge: Clear Buffer |
Clear the current message buffer |
Or click Save Context in the bottom right status bar.
Settings
| Setting |
Default |
Description |
session-bridge.provider |
gemini |
AI provider — gemini, claude, or openai |
session-bridge.messageThreshold |
5 |
Messages before auto-save (min 2) |
session-bridge.captureGitDiff |
true |
Include git diff in context |
session-bridge.captureOpenFiles |
true |
Include open files in context |
Workflow
- Start working with Claude Code / Codex / Gemini / Amazon Q
- Log progress every few exchanges:
- Ctrl+Shift+P → "Session Bridge: Log Message"
Credits die unexpectedly? → Open SESSION.md → Paste it as the first message to your next AI tool → Continue exactly where you left off
Example SESSION.md Output
## Problem
Implement JWT-based authentication for a REST API
## Approach
Express.js + PostgreSQL, bcrypt for password hashing, JWT for stateless auth
## Completed
- POST /register — complete
- POST /login — complete, returns access + refresh tokens
- DB schema — finalized
## In Progress
- GET /me endpoint — needs auth middleware
## Next Steps
- Complete auth middleware
- Add token refresh endpoint
- Write integration tests
## Key Decisions
- Chose JWT over sessions for statelessness
- Refresh tokens stored in DB for revocation support
## Files Modified
- src/routes/auth.ts
- src/middleware/authenticate.ts
- src/db/schema.sql
Requirements
Privacy
Session data is sent to Google's Gemini API to generate summaries. Your API key is stored securely using VS Code's built-in secret storage and never written to disk in plaintext.
Contributing
Pull requests are welcome. For major changes, please open an issue first.
- Fork the repo
- Create your branch (
git checkout -b feature/my-feature)
- Commit your changes (
git commit -m 'feat: add my feature')
- Push to the branch (
git push origin feature/my-feature)
- Open a Pull Request
Save, then push to GitHub:
git add .
git commit -m "docs: add README with badges and sponsor link"
git push
Support
If Session Bridge AI saves you time, consider sponsoring:
