Claude Code
JSONL sessions, local projects, worktrees, CLAUDE.md rules, and native resume whenever the thread still exists.
Local agents and web chats
Tramya never mistakes the model for the app. Every connector knows where each tool keeps its history, how to tie it to the repo, and what kind of resume is actually possible.
Code agents
Connectors read the supported local formats and watch for new sessions without ever asking for your passwords.
JSONL sessions, local projects, worktrees, CLAUDE.md rules, and native resume whenever the thread still exists.
Active and archived tasks, messages, working paths, and continuity built from verifiable context.
Local sessions, native identifier, and repo association.
Supported local history, linked workspace, and cross-source search.
Tasks, durations, tokens, and costs whenever the source actually provides them.
SQLite sessions read read-only, with tokens, costs, and cwd preserved. Native hermes chat --resume.
Reads the supported local histories while preserving their provenance.
Web chats
The Tramya extension captures a conversation with your consent and attaches it to the right project.
| Source | Capture | Sorting | Resume |
|---|---|---|---|
| ChatGPT | Extension or export | Chosen or detected project | Context to an agent |
| Claude | Extension or export | Chosen or detected project | Context to an agent |
| Gemini | Extension or Takeout | Chosen project | Handoff |
| Copilot, Perplexity, Mistral, Grok, Poe | Extension | Chosen project | Handoff |
No. Local agents already write their sessions to your computer. Tramya reads those files, while the web extension only saves the conversation you explicitly request.
Yes. Tramya gathers the repo, branch, worktree, rules, memories, and useful messages to prepare a handoff to Codex.
No. No provider gives access to its hidden internal reasoning. Tramya keeps the visible messages, tool outputs, memory files, and traces the source app actually writes.
Comparisons