Find
Search for a decision or a referenced file without manually reopening every Cursor workspace.
Cursor integration
Your Cursor chats.
Finally findable.
Tramya queries the local history Cursor supports, identifies the workspace, and makes the conversations searchable alongside the project's other sessions.
Why it helps
Never lose a decision in an old composer again.
Hand off
Prepare a sourced summary to keep the same topic going in Claude Code, Codex, or Copilot.
Keep it local
Local mode does not automatically copy your conversations in cleartext to Tramya servers.
Getting started
Connect Cursor to Tramya in a few minutes.
Tramya sits beside Cursor without changing your editor: it reads the local history read-only, indexes it, and makes the context available over MCP. Here is how to connect it and what it actually pulls in.
Install and connect
Download the Tramya app (macOS, Windows, Linux) and click “Install in my agents”: the MCP server is registered in Cursor's configuration. No JSON to edit by hand; the connection is live on the next launch, and Cursor can call get_project_context and save_memory.
What Tramya indexes
Cursor keeps its chat per workspace. Tramya reads that history, ties it to the repo, branch and Git worktree, then extracts the decisions, cited files and code blocks — all queryable from any agent, without reopening each workspace one by one.
One context, every agent
A decision made in Cursor becomes available in Claude Code, Codex or Gemini CLI, with its provenance. You switch tools by task without losing the thread, and you resume in Cursor work started elsewhere — memory follows the project, not the editor.
Cursor and Tramya
Does Tramya modify the Cursor database?
No. The connector reads the supported structures carefully and never writes to Cursor's data.
Is it compatible with every future Cursor format?
The diagnostic checks the detected structure. If Cursor changes its storage, Tramya flags the connector as incompatible instead of inventing a result.