18 lines
1018 B
Markdown
18 lines
1018 B
Markdown
# Background tasks viewer limits
|
|
|
|
The chat background-task surface now shows only shell identities verified for the
|
|
selected chat session by the current-running snapshot and lifecycle events. It
|
|
keeps a bounded in-memory tail of exits observed by this client so a selected task
|
|
can settle with an observed exit code; it is not durable task history.
|
|
|
|
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. A task that exits after observation remains
|
|
visible and reports the server's output or an explicit unavailable/empty state.
|
|
|
|
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.
|