Cross-cutting search
One query surfaces the Hermes sessions, the Claude Code conversations and the memories from the same project, each with its provenance.
Hermes Integration
Every Hermes session.
Matched to the right project.
Tramya reads the local Hermes database, files every session by repository and lets you resume it natively or hand its context to another agent.
Continuity
Hermes joins the same working memory.
Repository and branch preserved
Hermes records the folder, the branch and the Git root of every session. Tramya uses them to attach the thread to the right project.
Real tokens and costs
Input, cache and output usage as well as the estimated cost are read straight from the Hermes database.
Native resume
Reopen the original Hermes session with its native command, or start a fresh thread with verified continuity context.
MCP
Hermes already queries Tramya’s memory.
| Capability | Detail |
|---|---|
| Local database reading | Sessions, visible messages, tokens, costs, repository and branch |
| Native resume | hermes chat --resume <session> in the right folder |
| Handoff to another agent | Compact context passed to Claude Code, Codex or Gemini CLI |
| Two-way MCP | Hermes reads Tramya via the local MCP server; Tramya reads Hermes via its SQLite database |
Questions about the Hermes integration
Does Tramya read Hermes passwords?
No. Tramya only reads the local database of sessions already recorded by Hermes, without touching credentials or secrets.
Can a Hermes session be resumed in Claude Code?
Yes. Tramya gathers the repository, the branch, the rules, the memories and the useful messages to prepare a handoff to Claude Code.
Does the Tramya MCP kit install into Hermes?
Yes. The setup assistant declares the Tramya MCP server to Hermes just as it does for Claude Code and Codex.