Problem
When running several copilot sessions in parallel (multiple terminals, tmux/wezterm panes, different repos), there is no glanceable way to tell which session is which from the statusline. The cwd shows up, but two sessions in the same repo or two sessions for the same project look identical at a glance.
/rename already gives a session a human-readable name, and --resume works against those names. But the name only surfaces in the picker, not in the running session itself.
Proposal
Expose the current session name (and session ID) in the statusline payload so they can be rendered with statusLine.command.
Suggested fields:
session_name - the user-set name from /rename, or the auto-generated one
session_id - the UUID under ~/.copilot/session-state/
Example custom statusline:
[my-refactor] ~/src/repo (main) 120k/200k 18%
vs. today:
~/src/repo (main) 120k/200k 18%
Why this helps
Alternatives considered
Problem
When running several
copilotsessions in parallel (multiple terminals, tmux/wezterm panes, different repos), there is no glanceable way to tell which session is which from the statusline. The cwd shows up, but two sessions in the same repo or two sessions for the same project look identical at a glance./renamealready gives a session a human-readable name, and--resumeworks against those names. But the name only surfaces in the picker, not in the running session itself.Proposal
Expose the current session name (and session ID) in the statusline payload so they can be rendered with
statusLine.command.Suggested fields:
session_name- the user-set name from/rename, or the auto-generated onesession_id- the UUID under~/.copilot/session-state/Example custom statusline:
vs. today:
Why this helps
/renameto check--resume <name>flowAlternatives considered