4e4d09b6a4
The chat background-task bar now lists only tasks that are still running, so an exited task no longer lingers and the bar disappears when the last one ends. The one-line 'running now and recently observed exits' subtitle is replaced by a compact 'Background tasks · N running' header, and the list is capped at three touch-sized rows and scrolls beyond that instead of pushing the composer down the screen. Unit-tested (running-only set and the row cap) and the stale note updated.
25 lines
1.4 KiB
Markdown
25 lines
1.4 KiB
Markdown
# Background tasks viewer limits
|
|
|
|
The chat background-task bar shows only shell identities verified for the
|
|
selected chat session by the current-running snapshot and lifecycle events. It
|
|
lists **only tasks that are still running**: a task that exits leaves the bar, and
|
|
the bar disappears entirely once the last one ends, so the bar's height tracks the
|
|
running work rather than accumulating finished tasks. The bar shows at most three
|
|
rows (`BACKGROUND_TASK_VISIBLE_ROWS`) and scrolls beyond that.
|
|
|
|
The store still keeps a bounded in-memory tail of exits observed by this client, so
|
|
a task's exit code can settle internally; it is not durable task history and is no
|
|
longer rendered by the bar.
|
|
|
|
The upstream shell list is RUNNING-only. Tasks which ended before observation are
|
|
not enumerated or backfilled. Verified output is read lazily for the selected task
|
|
through one bounded 64 KiB page; refresh rereads that page from cursor zero rather
|
|
than accumulating client history. Selecting a running task reports the server's
|
|
output or an explicit unavailable/empty state; because the bar lists only running
|
|
tasks, a task's output is not readable from the bar after it exits.
|
|
|
|
This changes the chat UI. The packaged OpenCode skill references and chat topic
|
|
documentation should describe the running-only, bounded-observation behavior and
|
|
the lack of durable history when the manual `docs-fold` pipeline next updates
|
|
shared documentation.
|