desktop: hiding the thinking timeline category also silences the Thinking status

Aberta
#65,331 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
react, typescript
Domínio
frontend

Direção de pesquisa

Start at packages/session-ui/src/timeline-next/rules.ts liveThinkingShows() and turn-phase-machine.ts, both gating the phase on reasoning.placement !== "hidden". Then packages/app/src/session/timeline/message-timeline.tsx:469-470, where the thought row replaces the status lane. For merging, compare projection.ts:730/:905-935 (already groups adjacent reasoning parts) with context-group.tsx:64,151-168, where thoughtsOnly emits one ThoughtRow per part. Done: hidden thinking still shows a Thinking status, and a reasoning-only group renders one merged row.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area/desktop platform/macos type/feature version/v2

Description

Two symptoms from the same coupling, which together leave no usable middle ground for the thinking category:

  1. Hidden thinking kills the status signal. With 思考 = 隐藏, the status line under a working turn can only read 工作中 ("Working"). The Thinking state becomes unreachable, so there is no way to tell "the model is streaming reasoning" from "the request is stalled waiting on the provider".
  2. Grouped thinking gives one row per reasoning part. With 思考 = 分组 + 折叠, a stretch of reasoning parts with no tool call in between renders as N separate 「思考 N 秒」 rows (16 in a row in my session). There is no option to merge them.

Source (dev branch):

  • packages/session-ui/src/timeline-next/rules.ts:190 — liveThinkingShows() is just detail.thinking.placement !== "hidden", and it gates the whole signal
  • packages/session-ui/src/timeline/turn-phase-machine.ts:60 — a turn only enters the thinking phase when reasoning.placement !== "hidden", otherwise it falls through to WORKING_TURN_PHASE
  • packages/app/src/session/timeline/message-timeline.tsx:469-470 — "Thinking" is not a status-line string at all; the streaming thought row replaces the status lane
  • packages/session-ui/src/timeline-next/tools/context-group.tsx:64,151-168 — a group containing only reasoning parts (thoughtsOnly) skips the group wrapper and emits one ThoughtRow per part, so the collapse switch has nothing to act on
  • the projection already collects adjacent reasoning parts into a single context group (projection.ts:730, :905-935); only the renderer splits them back out

Suggested fixes, in order of how much they would help:

  1. Decouple the status signal from the display setting — allow the thinking phase and a "Thinking" status line even when thinking rows are hidden.
  2. Merge consecutive grouped reasoning parts into one row, e.g. 「思考 3 条 · 共 21 秒」.
  3. Optional: show elapsed time in the status line ("Working 1:23"). The data already exists — the sidebar inbox renders sidebar.inbox.status.workingFor.

OpenCode version

2.3.2 — desktop on macOS, New timeline experiment enabled (general.newTimeline = true)

Steps to reproduce

  1. Settings → General → Timeline → 高级, set 思考 = 隐藏
  2. Run any turn that emits reasoning. The status line reads 工作中 for the entire turn, including while reasoning is actively streaming.
  3. Set 思考 = 分组 + 折叠
  4. A stretch of reasoning parts with no tool call between them renders one row each

Plugins

none

Operating System

macOS (desktop app)

Terminal

n/a — desktop app

Screenshot

16 consecutive 「思考 N 秒」 rows. Can attach if useful.

Linguagem predominante
TypeScript
Estrelas
227k
Forks
30.7k
Merge médio
3h 57min
PRs com merge (30d)
484

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de anomalyco/opencode

Todas as issues de anomalyco/opencode

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.