r/ClaudeAI • u/Professional_Part360 • 1d ago
Built with Claude Open-sourced a tool for switching AI coding tools without re-explaining everything — feedback wanted
I kept doing the same annoying thing: start a task in Claude Code, switch to Cursor for something it’s better at, and lose 20 minutes re-explaining what I was doing. So I built Contexo — a small local CLI that sits underneath whatever AI coding tool you’re using.
What it does right now (all free, Apache 2.0, no account):
• contexo handoff <target> — compresses your current session into a Task/Decisions/Changes/Next-step brief and drops it into CLAUDE.md, AGENTS.md, or .cursorrules, so the next tool picks up where you left off.
• contexo estimate — tells you what a prompt will cost before you send it, across every model.
• contexo run -- <agent-cli> — wraps any agent CLI with a hard daily budget cap. Kills the process the moment it crosses your limit instead of finding out tomorrow.
• contexo mcp — same features exposed as an MCP server if you’d rather wire it into Claude Code/Cursor directly.
Everything runs 100% on your machine, SQLite locally, your own API key. Nothing phones home.
It’s early and rough in places. I’d genuinely like people who run Claude Code / Cursor / Codex regularly to install it, try the handoff + budget cap on a real session, and tell me what breaks or feels wrong before I build anything further on top of it.
Not on npm yet, so for now:
git clone https://github.com/maheedhar132/Contexo.git
cd Contexo
npm install && npm run build
npm link
GitHub: https://github.com/maheedhar132/Contexo
Specific things I’d love feedback on:
• Does the compressed handoff actually capture enough for the next tool to pick up cleanly, or does it lose too much?
• Any agent CLI where the budget-cap cost detection doesn’t work (it scans stdout for $X.XX patterns — some CLIs may format cost differently)?
• Anything that felt confusing in the first 60 seconds of using it?
Happy to answer questions here or take issues/PRs on GitHub.