Problem
When multiple agent terminals are open (builder-1, builder-2, builder-3, reviewer-1, milestone-reviewer, tester, validator, etc.), it's hard to tell which terminal window belongs to which agent role at a glance.
Desired Behavior
Each terminal window should make its agent role immediately obvious. Options to consider:
- Terminal title — set the terminal title via ANSI escape sequence (
\033]0;builder-1\007) or shell prompt before launching the Copilot subprocess
- Banner on launch — print a prominent ASCII/box-drawing banner at the top of each terminal (e.g.,
═══ BUILDER-1 ═══) before the agent starts
- Shell prompt prefix — set
PS1 or equivalent to include the agent role
- Window title via terminal.py — pass a title argument when spawning terminal windows (platform-specific: iTerm2/Terminal.app on macOS, Windows Terminal, GNOME Terminal, etc.)
Context
The terminal spawning happens in src/agentic_dev/terminal.py. Each agent is launched via _spawn_terminal_*() functions that open new terminal windows. The agent role and builder ID are known at spawn time — they just need to be surfaced visually in the terminal itself.
Problem
When multiple agent terminals are open (builder-1, builder-2, builder-3, reviewer-1, milestone-reviewer, tester, validator, etc.), it's hard to tell which terminal window belongs to which agent role at a glance.
Desired Behavior
Each terminal window should make its agent role immediately obvious. Options to consider:
\033]0;builder-1\007) or shell prompt before launching the Copilot subprocess═══ BUILDER-1 ═══) before the agent startsPS1or equivalent to include the agent roleContext
The terminal spawning happens in
src/agentic_dev/terminal.py. Each agent is launched via_spawn_terminal_*()functions that open new terminal windows. The agent role and builder ID are known at spawn time — they just need to be surfaced visually in the terminal itself.