[quickbeard]

Every session row — in the sidebar's Recents and on the home View all list — gains a hover-revealed vertical three-dot button at its right edge. It opens the same menu the ⋯ button beside a session title opens: Rename, Share…, Archive, Delete….

Previously the only way to rename, archive or delete a session was to open it first and use the menu next to its title, which is exactly backwards when you are clearing out sessions you do not want to open.

The menu is reused, not reimplemented

Both renderings — the legacy DropdownMenu and the v2 MenuV2 — plus the DialogDeleteSession closure move verbatim out of message-timeline.tsx into the fork-only components/session-actions-menu.tsx. The session header renders that component too, so there is one definition of the four items instead of three copies free to drift.

One subtlety worth not undoing: the component owns the deferred Rename and Share. Neither can run on onSelect — the menu is still closing and pulls focus back to its trigger, which blurs the inline editor the instant it opens. That deferral used to be the header's pendingRename/pendingShare store fields; it now lives in the component, so every caller inherits it.

Rename edits the row's label in place using the existing createInlineEditorController (the same primitive the legacy sidebar's workspace rename uses) — Enter saves, Esc cancels. archiveSession/renameSession/deleteSession move into createHomeModel() so the sidebar and the home screen run one implementation; home.tsx's duplicate archiveSession is gone.

Two bugs this surfaced

The local sidecar publishes no session lifecycle events. Watching /event while creating and archiving sessions against a running app produces nothing but server.connected. The recents index is only ever corrected by a refetch, so an archived row stayed on screen looking broken. Actions now invalidate the index query. This is pre-existing — the session header's Archive has the same staleness — but it is what made the new menu look non-functional.

share is scope-sensitive. It exists only on the directory-scoped sync store; the server-level store has no such key at all. Gating on the server-level store offered Share on a server with sharing disabled, and the session page then refused to open the popover. The rows now read ensureDirSyncContext(session.directory) — the same store the session page reads through useSync — and the row menu matches the header exactly.

Share from a row

Share opens the session and asks it to open its popover, via a small pending-signal bridge (utils/session-share-request.ts). The popover cannot live on a row: it reads share.url off the fully synced session, and the recents index drops it because SessionV2Info has no share field — making it work in place would be a Schema/Protocol/Server change.

This bridge is unverified at runtime. The environment it was tested against has share: "disabled" both globally and per-directory, so the item is correctly hidden in both menus there and the path could not be exercised.

Verification

Driven against a running desktop app over CDP:

• Menu renders in both lists with the correct items, matching the session header
• Inline rename opens focused, saves on Enter, cancels on Esc
• Archive removes the row and sets archived server-side
• Delete confirms, removes the row, and the session 404s afterwards
• Session header menu still works (both design variants)

bun turbo typecheck clean across 32 packages. bun test in packages/app: 624 pass / 0 fail. Lint clean on touched files.

Ten throwaway sessions were created for testing and all deleted; a final audit confirmed no real session was archived or deleted.

Fork bookkeeping

DIVERGENCES.md gains rows for the two upstream files touched (message-timeline.tsx, home.tsx). The four fork-only files are not tracked there. CHANGELOG.md has an Unreleased entry.

🤖 Generated with Claude Code