A session whose only activity is a command stays "blank": its views and title are hidden

[manueljpconde]

What happens

A session that has run a command but has no chat turn yet is treated as blank by the Session list. The client then shows the welcome screen ("Into the Unknown" and the composer) instead of the conversation, hides the conversation view tabs (Chat, Trajectory, and plugin-contributed views), and lists the session as "New Session", ignoring a title set with session.rename.

This matters for plugins that create a session and start work in it through a command. For example, a plugin creates a session with sessions.create({ workspaceId }), runs a slash command in it through remote.commands.execute(sessionId, '/ …'), and opens it. The command runs and its events are committed (command/run, command/done), but the user lands on an empty welcome screen and has no way to see the plugin's view or the session's title until they send a chat message.

Where it comes from

packages/api/session-controller/src/list.ts, applySessionListMetadata:

const blank = state.blank && event.type !== 'turn/start'

Only turn/start ends blankness. A committed command/run doesn't, so the client skeleton keeps treating the session as blank:

• DefaultConversationViews.tsx returns null for the view area;
• ConversationMainPanel.tsx renders the Hero;
• ConversationSession.tsx hides the header's view ring;
• Rows.tsx shows the localized "New Session" label over the stored title.

Proposed change

Treat a committed user command as activity:

const blank = state.blank && event.type !== 'turn/start' && event.type !== 'command/run'

This also fits the "New Session reuses a blank one" behaviour: a session that has already run a command shouldn't be reused as an empty one.

Alternatives

• A public way for a plugin to select a conversation view (today selectView exists only in the shell's own header slot props, and ConversationBinding exposes no view selection).
• Sending a synthetic first turn. This costs a model call and adds model-visible input, so it isn't a good fit.

Environment: dsh 0.2.1-alpha.1, web profile.

[PerryLink]

你这条逐条都对，我把每一处引用都在最新代码上核过了（含你提到的 Rows.tsx、Into the Unknown、selectView 接口面）。而且我要指出一个比 UI 隐藏更严重的后果。

1. 判定点确实只认 turn/start

packages/api/session-controller/src/list.ts:51：

const blank = state.blank && event.type !== 'turn/start'

• :87 → init: () => ({ blank: true, lastPromptAt: null })
• :121 → blank: metadata?.blank ?? session.seq === 0

list.ts 内 turn/start 只出现在这一行，而 command/run 在整个文件里 0 命中。⇒ 你的判断成立：blank 的清零条件只有 turn/start。

2. 下游四个消费者，逐个核实

• packages/client/ui-conversation/src/client/skeleton/DefaultConversationViews.tsx:32 → if (session.blank && conversationPhase(session, conversation) === 'blank') return null
• packages/client/ui-conversation/src/client/skeleton/ConversationMainPanel.tsx:18,21,38,42-43 → 'blank' / summaryBlank / 两处 shellPhase === 'blank' 判定 / const phase = settling ? 'settling' : hero ? 'hero' : 'active'
• packages/client/ui-workspace/src/client/rows/Rows.tsx:47-49 → /** Row display title: blank rows show the localized New Session label. */ function displayTitle(node, t) { return node.blank ? t('session.new') : (node.title || t('session.untitled')) }（你说的 Rows.tsx 确实存在，只是在 ui-workspace 下，不在 ui-conversation）
• packages/client/ui-conversation/src/client/contract/snapshot.ts:26-34 → const active = conversation.activeTargets.size > 0 || (!session.blank && !session.awaitingFirstTurn) || session.running / return active ? 'active' : session.promptAttempted ? 'engaging' : 'blank'

hero.headline 的 'Into the Unknown' 也逐字在 ui-conversation/src/client/locales.ts:455。

3. 「隐藏标题/View tabs」是有意设计 —— 但你的问题不是

packages/client/ui-conversation/README.md:75 写得明白：

A blank Session retains the header's leading and corner controls… while hiding its title, actions, utilities, and View tabs. Selecting a Workspace creates the Session needed by these controls; the first message is not required.

:79 还补了 A blank Session still omits the conversation.view slot。

⇒ 所以"隐藏"本身是契约。真正的问题是**blank 的「有活动」定义只认 turn/start** —— 文档从未声称"只跑过命令的会话也应保持 blank"。这是真实的设计缺口，不是文档化的取舍。建议在报告里这么写，否则容易被 README :75 一句挡回。

4. ⭐ 比你报的 UI 问题更严重的一点：跑过命令的会话会被当成空会话复用

packages/client/ui-workspace/src/client/contract/slots.ts:119 → Start a New Session: with a workspace, reuse-or-create its blank session；navigation.ts:63 → Resolve the reusable or newly created blank Session for a Workspace.，:200 → if (summary === undefined || !summary.blank || summary.cwd !== workspace.path，:384 → if (summary !== undefined && (!summary.blank || workspace === undefined)) {

⇒ 因为 command/run 不清 blank，一个已经跑过命令、有实质历史的会话会被当成"可复用的空会话"。

这一条比标题被隐藏重要得多（前者是显示问题，后者是往已有历史里继续写）。建议把它提到诉求的第一位 —— 采纳率会明显不同。

5. 你的一行修法有效，而且不需要改客户端

list.ts:51 加上 && event.type !== 'command/run' 后：

• session.blank 变 false
• ⇒ snapshot.ts:31 的 !session.blank && !session.awaitingFirstTurn 直接为真
• ⇒ conversationPhase 返回 'active'
• ⇒ 上面四个消费者全部自动放开

只加 command/run 就够，不必同时判 command/done —— 你已提到这个，我同意：blank 一旦清掉不可逆，加一个就够。

6. 副作用面（提 PR 时建议一并说明）

这两处也读 session.blank，改动后行为会一起变：

• packages/client/ui-agent-preset/src/client/index.ts:124,245
• packages/client/ui-agent-preset/src/client/seat-store.ts:165,181,214

它们做的是"blank 会话预置同步"。变化方向正是你想要的（不再把跑过命令的会话当空壳），但属行为变更，在 PR 描述里点明会省掉一轮 review 往返。

临时规避（不推荐）：会话内补发一个合成 turn/start —— 你自己也评估过，成本是一次模型调用，不值。

7. 版本

你写 dsh 0.2.1-alpha.1。我核的是 origin/master = d743267388（= dsh-v0.2.1-alpha.2），上述文件与行在 master 上逐条仍成立 ⇒ 不构成过期，你引的 list.ts:51 原文一字未改。

至于你说的 selectView 只在 header slot props 面上（ui-conversation/src/client/contract/slots.ts:356）、ConversationBinding 侧没有 View 选择面 —— 这条我也确认了，属实。