Sorted by repo
The working path ties the task to the right project, even when a user has several accounts or worktrees.
Cline integration
Every Cline task.
In the right place.
Cline keeps rich tasks. Tramya sorts them by project and uses the messages, decisions, durations, tokens, and costs only when they are actually available.
Analysis
From an isolated task to project knowledge.
Actionable stats
The metrics Cline exposes power views of duration, volume, and cost with no misleading estimates.
Documented resume
The next agent receives the useful decisions and actions with a link back to the original task.
Getting started
Connect Cline to Tramya without leaving VS Code.
Cline drives tasks from VS Code and keeps their history locally. Tramya indexes it and makes each task reusable as project context. Here is how to connect it and what changes day to day.
Install and connect
Download the Tramya app (macOS, Windows, Linux) and click “Install in my agents”: the MCP server is registered for Cline. No manual configuration; from the next launch, Cline can query get_project_context and save a decision with save_memory.
What Tramya indexes
Tramya reads Cline's tasks — active and archived — sorts them by repo, branch and worktree, and extracts decisions, touched files and executed commands. A finished task is no longer lost: it becomes a queryable source, without mixing with the others.
One context, every agent
What Cline learns about a project is available in Claude Code, Codex or Cursor, with its provenance. You start a Cline task with decisions already made elsewhere, and hand its result to the next agent with no manual copy-paste.
Cline and Tramya
Can Tramya pull Cline costs?
Yes, when they appear in the task files. Missing data is never reconstructed arbitrarily.
Does the connector work with multiple VS Code profiles?
The detected locations can be declared as separate profiles, then monitored individually in the diagnostic.