[bug]0.1.2-rc.1重启后，工作区内的对话名称，全部为工作区的名称，点击进入对话后才恢复为该对话的原有名称

[Forchelly]

如图所示

[Forchelly]

这个问题解决在哪儿了？我真没招了，这到底有没有经过测试就端上来了？ @tianyicui

[argszero]

Thanks for the clear repro. I dug into the source and can confirm this is a cold-list projection cache gap, not lost title data — the title is still in the durable log.

Why the list shows the workspace name

The session list reads each row's title from the projection cache (projectionStore.get('title') in packages/api/session-controller/src/client/sessions/manager.ts:915), not from a live re-fold of the session log. The display title is then derived by displayTitleOf(title, cwd, id) in service.ts:146:

if (title !== undefined) return title
if (cwd !== undefined && cwd !== '') {
  const base = workspaceTitleOf(cwd)      // ← workspace basename fallback
  if (base !== '') return base
}
return id

So when the title projection key is absent from the cold cache row, the list falls back to the workspace name — precisely the symptom you see. Entering a conversation re-instantiates the session, which re-folds the log (foldSessionTitle), so the true title comes back.

Why the title row is missing after a restart

session/title is a durable event type (packages/core/session/src/known-event-types.ts:51) and folds into the title projection key (titleProjectionDefinition, stateVersion: 1), so nothing is lost from the log.

But the projection cache only checkpoints at specific moments (packages/session/session-projection-cache/src/index.ts:272-305): every N events, an interval timer, turn/end, session/created, and session/disposed. A hard process restart never fires session/disposed — the last surviving checkpoint is the previous turn/end.

The key timing issue: the LLM title provider (first-prompt / all-prompts cadence in the session-title service) schedules generation after the main request is logged, and commits the session/title event after that turn. So the title event typically lands after the last turn/end — and therefore after the last durable checkpoint. If the daemon restarts before the interval/count throttle flushes that tail, the cold cache row has no title value even though the log does.

Suggested direction (small, targeted)

Make the session/title append itself a cache write point — e.g. treat it like turn/end as a mandatory flush — so the title is checkpointed the moment it commits, regardless of arrival relative to turn/end. Alternatively, on cold list, if the title key is absent and a session/title event exists in the log, hydrate it (the cold-read ladder already does probeSmallCold; folding just the title would be cheap).

I'm happy to help write a patch if you'd like. The distinction matters: the title is safe, this is purely a cold-list projection staleness.