🖥️ Terminal UI Framework: Interactive Coding Shell

[yacosta738]

Summary

Evaluate and implement the terminal UI path required for Corvus to approach Claude Code-class interactive terminal behavior.

Why this matters

A code agent at Claude Code level is not only runtime logic; it is also a high-quality interactive terminal experience. This is currently one of the largest parity gaps in Corvus.

Current reality in Corvus

Already present:

• runtime, gateway, web, and mobile surfaces

Still missing for parity:

• dedicated terminal UI framework
• terminal layout/rendering model
• rich interactive session UX comparable to Claude Code

Scope

• choose the terminal architecture path:
  • build with Rust TUI libraries
  • or define a thinner bridge/wrapper strategy around an existing surface
• document rendering, state, and interaction model
• implement the first usable terminal shell for coding-agent workflows

Non-goals

• reproducing Ink internals one-to-one unless that is the chosen architecture
• bundling every optional feature into the first terminal version

Dependencies

• Depends on decisions from roadmap restructuring and product direction
• Benefits from ⌨️ Slash Commands: Command Registry Implementation #527 command registry and 🤖 Coordinator Mode: Multi-Agent Orchestration #525 coordinator mode but does not strictly require them for an initial shell

Acceptance criteria

• terminal architecture choice is documented with tradeoffs
• first usable interactive terminal workflow exists
• rendering/input loop is stable under long-running agent sessions
• tests or validation strategy exist for rendering and input handling

References

• tmp/CLAUDIO_ROADMAP.md
• tmp/claurst-main/spec/08_ink_terminal.md
• tmp/Product Requirements Document (PRD) _ Specifications for Replicating Claude Code.md §9

[linear]

DALLAY-274

[github-actions]

This issue was marked as stale due to inactivity. It will be closed automatically if there are no updates.