A dashboard rooted in ~/Tests/platform now has a session picker in its chat
panel's header: every conversation started in that directory, newest first, plus
New chat, rename and delete.
── Almost all of this already existed ──
`GET /chat/sessions?cwd=` returns conversations for a working directory, merged
across Claude and OpenCode. It is not a registry Officer maintains: Claude writes
每 transcript to `~/.claude/projects/<cwd-slug>/`, so "the conversations belonging
to this dashboard" is how they already sit on disk — the same ones the terminal
`claude` sees. `useClaudeSessions` already wrapped list, rename and delete for the
/chat screen. The panel header is new; nothing under it is.
── The one design correction ──
Which session a panel is on is NOT `usePanelMemory`. That hook claims its saved
value once and then ignores the bag, because the editor and file browser are the
only writers of their own state and hearing it echo back would tell them to reopen
what they just closed.
Here the header writes and the body reads — two components with no props between
them — so the value has to stay LIVE. Claim-once would have meant picking a
session changed the label and nothing else. It is the same dashboard-state bag,
read live, so it still survives a reload.
Switching remounts the chat on its key, which is what the existing comment calls
"the honest way to say this is now a different conversation": `useChat` seeds from
the first `initialSessionId` it sees and the resume handshake sends whatever is in
that state on connect.
A NEW chat is `null` until the harness names it — only the harness can — and the
id is recorded on arrival, so "new chat, say something, reload" returns to that
conversation rather than a third one.
Deleting the conversation on screen points the panel at a new one rather than at a
transcript that no longer exists.
── Left alone, and one thing to know ──
`agent_panels` is untouched: a named agent still wins the session choice outright,
since it is one conversation forever by definition. The picker is for the ordinary
case.
The email screen mounts ChatPanelWrapper too, so its chat now also remembers its
session instead of starting fresh each visit. That is a behaviour change to a
screen this work was not aimed at — better in my view, but say if not, and it
scopes to dashboards in one line.
tsgo clean, frontend builds, 846 pass / 7 fail unchanged.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pastilhasandClaude Opus 5
465435ccf1