A terminal agent becomes easier to supervise when tool activity, context pressure and session history stay visible together. This interface brings those controls into the terminal while retaining the selected backend's session machinery, so familiar interaction does not require a separate conversation store.
What Sets It Apart
- Streaming Markdown, structured tool cards and file completion keep the work readable and navigable in a terminal.
- Context, throughput and usage indicators help users follow long-running tasks; session controls support resume, fork and rewind.
- Event-driven rendering, virtualization and bounded caches target the overhead of long conversations.
- Experimental Claude and Codex adapters reuse the interface with their respective backends, broadening the choice of execution engine.
Who It Suits and the Trade-offs
A good fit for developers who prefer terminal workflows and want visible agent state alongside session navigation. The project is in public beta, and backend capabilities differ. Graphics and advanced input depend on terminal support; users needing consistent feature parity across backends should review the compatibility notes.
