-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Problem statement
Tau TUI is still fundamentally an operator/debug shell and log renderer instead of a modern transcript-first terminal agent interface. It uses space poorly, exposes low-level runtime detail instead of task context, and does not yet deliver the interaction quality expected from tools like Claude Code, Codex CLI, or OpenCode.
Acceptance criteria
- Interaction model defined
- Define transcript-first layout, compact status context, approvals, slash commands, interrupts, retries, tool/task visibility, and artifact/memory/cortex access.
- Layout/system behavior defined
- Define resizing, focus, scroll, expansion, keyboard shortcuts, status line behavior, and command discoverability.
- Progress and failure UX defined
- Define how in-flight model/tool/task activity is shown in-place, and how failures/recovery actions are rendered without collapsing into log spam.
- Shared-state dependency honored
- TUI redesign must explicitly consume the shared operator turn/task state protocol rather than inventing a separate UI-only event model.
- Test plan defined
- Define PTY/TUI regression and interaction tests for input, cancel, approvals, retries, tool streaming, and resize behavior.
Non-goals
- Webchat redesign.
- Swarm orchestration UX beyond the hooks the TUI needs.
- Replacing TUI with a browser-only workflow.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels