TL;DR: I built chat-history , a fast Rust CLI to search and share context across your Cursor and Claude Code sessions. If you use both tools, you already know how painful this is. Here is exactly what kept happening to me: I’d be deep in the zone in a Claude Code session, hit a rate limit, manually paste my context over to Cursor, and keep going just to maintain momentum. But a few days later, I’d need to reference a specific fix or piece of logic and I couldn’t remember which tool I used to write/brainstorm it. I would end up wasting time blindly scrolling through dozens of vaguely titled chat tabs across both apps. To fix this, I built (vibe-coded) chat-history : a fast Rust CLI that unifies your Claude Code and Cursor history. It lets you search, inspect, and import/export sessions from one place. Using it as an Agent Skill: If you run chat-history install-skill , it exposes the search tool directly to your agents. You can prompt your current agent with something like: “Find the session where I fixed the database auth issue.” It will pull the exact context from either platform directly into your active chat. Ways it speeds up your workflow: Recover lost fixes: “Where did I fix that bug?” (Sub-second scored search across both tools) Track progress: “What did I work on last week?” (Filter by date, project, or branch) Audit AI logic: “What was decided in that session?” (Inspect files touched, tools used, and decisions made) Pick up the pieces: Resume or export any session right where you left off. Deep search parses full transcripts in parallel, weighs recency, and deduplicates results. Because it’s Rust, it’s instant. Try it out: 📦 cargo install chat-history 🔗 https://github.com/ay-bh/chat-history Feedback is highly appreciated! Let me know if you run into any issues or have ideas for features you’d like to see. submitted by /u/Geeky_Cool
Originally posted by u/Geeky_Cool on r/ClaudeCode