Claude Code TUI Fixes Cross-Directory Session Resume
Key insights
- Claude Code's --resume flag only finds sessions in the current directory, causing context loss when developers switch between repositories.
- The open-source TUI scans machine-wide JSONL session logs, surfacing all past sessions regardless of the active working directory.
- Strong Reddit engagement confirms that cross-directory session discovery is a widespread pain point among active Claude Code users.
Why this matters
Persistent session context is one of the highest-leverage features in agentic coding tools, and any workflow break that forces developers to restart a session erodes trust in the entire system. The gap between Claude Code's --resume flag and machine-wide session discovery represents a class of DX limitation that community tooling fills faster than official release cycles can. Developer-built workarounds that reach this level of engagement tend to either get absorbed into the official product within a few release cycles or establish themselves as permanent third-party dependencies, shaping the long-term ecosystem around the tool.
Summary
A developer shipped an open-source TUI that scans all Claude Code JSONL session logs machine-wide and surfaces them in a navigable list, bypassing the current-directory constraint entirely.
Claude Code's --resume flag only finds sessions from the active directory, causing developers to lose conversation context when switching between repos mid-task. The new tool reads the central log store directly and surfaces every session regardless of where the terminal is open.
Essentially: (Claude Code users, Anthropic) a community developer patched a known workflow gap before the official client did.
- Sessions are stored as JSONL files in a central machine location; the TUI reads that store directly to build its full session list.
- The Reddit post drew strong engagement, confirming the --resume limitation is widespread friction across the Claude Code user base.
Community patches to core developer tooling are a reliable signal of where official investment should follow.
Potential risks and opportunities
Risks
- If Anthropic ships native machine-wide session discovery, users who built workflows around the community TUI face migration friction and potential breakage without a migration path
- Reading JSONL session logs machine-wide could expose sensitive conversation context if the TUI is deployed on shared or multi-user systems without access controls
- Multiple competing community session-management tools could emerge before Anthropic standardizes the approach, fragmenting developer attention and creating incompatible tooling choices
Opportunities
- Anthropic can absorb the TUI's approach into Claude Code's official --resume flag, closing a documented friction point before competitors like Cursor and Windsurf cite it as a differentiator
- Terminal vendors like Warp and Ghostty could build Claude Code session management natively into their interfaces, using the JSONL format as a documented integration point to deepen platform stickiness
- The open-source project could expand into a broader session analytics layer surfacing usage patterns across projects, creating an enterprise adoption path for teams managing multiple Claude Code agents
What we don't know yet
- Whether Anthropic has a roadmap item for machine-wide session discovery in Claude Code's official --resume flag as of mid-2026
- How the TUI handles performance and navigation when JSONL session logs span months of work across hundreds of sessions on a single machine
- Whether the tool supports filtering or searching sessions by project directory, date range, or conversation content keywords
Originally reported by reddit.com
Read the original article →Original headline: r/ClaudeAI: Developer Ships Open-Source TUI to Find and Resume Any Claude Code Session From Any Directory — Fixes Built-In --resume Limitation