title fresh chats by first prompt instead of session id

[kevinjosethomas]

• chats started from prime-agent showed their session id as the name because a fresh session has no saved scan or spawn prompt to derive a title from yet.
• the session summary now falls back to the live in-memory first user message, so the chat is titled by its first prompt right away.
• resumed sessions and subagents are unaffected since the saved title and spawn prompt still take precedence.

---

Note

Low Risk
Display-only change to session list titling with unchanged precedence for saved and subagent sessions.

Overview
Fresh top-level chats no longer show the session ID as the display title when the jsonl has not been scanned or flushed yet.

summaryForActiveSession extends the firstMessage chain: saved scan title and subagent spawn prompt still win, but if both are missing the daemon now derives a 120-char compact label from the live first user message in memory via new helper firstUserMessageText.

Resumed sessions and subagents are unchanged because existing precedence rules still apply.

^{Reviewed by Cursor Bugbot for commit 50e6f1b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Title fresh chats by first user message text when no session title or prompt exists

In daemon-session-list.ts, summaryForActiveSession gains a final fallback for firstMessage: when neither savedSession.firstMessage nor metadata.prompt is available, it calls the new firstUserMessageText helper to extract a title from the first user message in the session. The helper scans session.messages for the first role === 'user' entry, extracts plain text, and truncates it to 120 characters.

^{Macroscope summarized 50e6f1b.}

[linear]

ENG-4243 Chats started from prime-agent are unnamed

Chats that are started from "prime-agent" command have their session ID as their name, rather than their first prompt. This is because we mock a real session before it's created, until a real chat message is sent.

Review in Linear