Skip to content

Latest commit

 

History

History
32 lines (19 loc) · 2.48 KB

File metadata and controls

32 lines (19 loc) · 2.48 KB

Agent TUI visual reference

The renderer does not clone product branding. It models the recurring visual grammar of credible coding-agent terminals while keeping each profile recognizably distinct.

Codex CLI profile

The primary profile follows the supplied real-session reference:

  • one continuous transcript, not a collection of fake terminal cards;
  • status dot plus a strong action verb (Ran, Running, Read, Update);
  • muted, indented tool output with and a collapsed-line affordance;
  • gray prose bullets, green approvals, yellow policy warnings, cyan values, blue paths;
  • full-width gray user turns and composer;
  • persistent model, effort, cwd, sandbox, and context footer.

The visual source is the user's own current Codex CLI capture. The official Codex repository is retained as the product reference.

Claude Code profile

The profile follows the terminal composition visible in the official Claude Code demo: light macOS title chrome around a deep teal canvas, a coral pixel identity, inline gray user prompts, green completed-tool bullets, white prose bullets, compact Read(...) / Search(...) / Bash(...) labels, a dim collapsed-thinking line, coral active work, a ruled composer, and a project footer. It is a separate DOM composition, not a recolored Codex transcript.

OpenCode profile

OpenCode follows the active-session layout shown on the official OpenCode site: a dense, nearly black main pane; a persistent right sidebar for context, integrations, todos, cwd, and version; side-by-side code diffs; and a wide bottom composer with a blue left rail and mode/model/provider metadata. agentSidebar supplies the optional session metadata instead of fabricating it inside the renderer.

Gemini CLI profile

Gemini follows the official Gemini CLI screenshot: a large gradient terminal wordmark, startup tips, purple star activity, outlined command/result cards, a blue-violet prompt border, the GEMINI.md/MCP row, and strongly separated cwd, sandbox, and model status metadata.

Rendering rule

Content chooses one profile. Features from other products remain available as semantic blocks, but the renderer does not mix every accent and layout into one generic “AI terminal.” This keeps the result credible in clean output and still legible after CRT treatment.