Gemini is excellent at exploration
Massive context window, fast responses. Ideal for brainstorming an architecture or scanning a large repository.
Gemini CLI Integration · Google
Google Gemini CLI restarts with nothing retained from your previous session. Tramya recovers the local traces of your Gemini sessions and lets you pick up right where you left off — in Gemini or anywhere else.
Why Gemini + Tramya
Massive context window, fast responses. Ideal for brainstorming an architecture or scanning a large repository.
Every session starts from scratch. Without an external tool, exploration is disposable.
Decisions, paths explored and files referenced are remembered on the project side, not the tool side.
How it works
The companion detects Gemini CLI automatically on macOS and Linux.
Tramya reads the default Gemini log directory and organizes sessions by git project.
A Gemini thread can be continued in Gemini (with context re-injected) or in Claude Code / Codex via handoff.
Typical use case
You use Gemini CLI to explore a major refactor — 2,000 files to scan, several directions on the table. Once you’ve chosen the path, you switch to Claude Code for precise implementation with its editing guardrails. Tramya hands Claude Code the summary of the rejected directions (with reasons), the chosen path, the list of affected files, and the invariants discovered during exploration. You save 30 to 60 minutes of re-explaining.
Both. Tramya reads the logs regardless of how you invoke it, as long as they’re written locally.
No. Tramya relays nothing to Google. The Gemini ↔ Google communication stays direct, handled by the official CLI.
Yes, as long as the traces are written to your disk in the standard format.