Conversation history
The .aider.chat.history.md file is parsed and indexed. Search "Postgres migration" across 30 repos and Tramya finds the right session.
Aider integration · Terminal
Aider has no native memory between sessions. Tramya reads the .aider.* files already sitting in your repos, sorts them by branch, and hands the context to Claude Code, Codex, or Cursor when the time comes.
What Tramya pulls from Aider
The .aider.chat.history.md file is parsed and indexed. Search "Postgres migration" across 30 repos and Tramya finds the right session.
Every commit Aider auto-generates is tied back to the conversation that produced it. You know why that diff exists.
The session's /add list is remembered: resuming means re-adding the same files, not today's.
How it works
One installer for macOS, Windows, or Linux. Nothing changes in your Aider setup.
Tramya automatically scans repos that contain .aider.* files. You confirm the list.
Filter "Agent = Aider", pick the session, click Resume: Aider restarts with the right context and the right files.
Aider alone vs Aider + Tramya
| Situation | Aider alone | Aider + Tramya |
|---|---|---|
| Resume a session from 2 weeks ago | Open the .md by hand | Instant keyword search |
| Move from Aider to Claude Code | Manual copy-paste | One-click handoff |
| Juggle 15 repos in parallel | One folder per repo | Unified view with branch filter |
| Find the commit that came from a conversation | Read through the logs | Direct commit ↔ prompt link |
No. Tramya reads the .aider.* files read-only; Aider works exactly as before.
Yes. Tramya relies on the conversation logs, not on the commits.
Yes. Tramya reads the histories no matter which model Aider uses.
Yes, anytime. Markdown + JSON format, no lock-in.