// how relai works
One place to follow your AI coding work.
Claude Code, Codex and other coding agents each keep their own session history. Relai reads those local records and turns them into one searchable workspace for the work you want to continue.
How an AI coding session flows through Relai
Claude Code writes its own session file. Relai reads the local record; the coding agent keeps running in its own tool.
01 / read
Your agents write the sessions
Relai reads supported session files created by Claude Code, Codex, opencode, Gemini, Cursor, Kiro, Cline, Pi, Aider and Qwen. It does not intercept prompts or take over the coding tools.
02 / understand
Build a local work history
Browse sessions by project and tool, search transcripts, inspect token usage and estimated cost, and see which work is active. Session parsing, search indexing and cost estimates run on your device.
03 / continue
You choose the next move
For example, carry session context from Claude Code into Codex. Relai prepares the handoff for you to review; it does not silently prompt or steer the receiving agent. Optional issue scans start with Jev and can send uncertain excerpts to your configured AI provider.
Keep the context. Choose the tool.
Find a past decision, reopen the right session, or carry a focused handoff into your next coding assistant.