Skip to content

tui: session shows 'done' when a background command finishes while session is still active #45560

Closed as not planned

Description

@TomKalina

Summary

When a background command completes (especially after failing), the session
status appears as "done" even though the agent is still actively working —
e.g. waiting on another background task or about to take the next action.
This is misleading: the user sees "done" and thinks the entire session
finished, when in reality the session is still in progress.

Environment

  • opencode version: 0.0.0-dev-202608261632
  • OS: Darwin 25.6.0 (arm64)
  • Terminal: TERM=xterm-256color (TERM_PROGRAM unset)
  • Shell: /bin/zsh
  • Install/channel: dev build (fix/v2-titlebarright-provider branch)
  • Active plugins: @mohak34/opencode-notifier, @nick-vi/opencode-type-inject,
    oh-my-openagent, opencode-gemini-auth, opencode-openai-codex-auth,
    opencode-wakatime

Reproduction

  1. Start an opencode session.
  2. Launch a long-running command in the background (e.g. pnpm ios).
  3. While it runs, launch a second background command that fails quickly.
  4. The failed command completes → session status shows "done".
  5. The first long-running command is still executing, and the agent is
    waiting to continue once it finishes.

Expected Behavior

The session-level status should reflect that the session is still active
and working. It should show a running/working state, not "done", as long as
the agent has pending background tasks or is about to take further action.

Actual Behavior

A completed (or failed) background command causes the session to display
"done", even though the session is still in progress with other work
pending.

Additional Context

This caused confusion in practice: a build failed (CocoaPods encoding
error), the session showed "done", but a second build was still running
and the agent was waiting to continue with the next step (running Maestro
E2E tests). The user asked "are you still working?" because the UI said
done.

Ideally the status would aggregate all active work: if any background
command is still running, or the agent is waiting to proceed, the session
should show a working/running state rather than done.

Activity

  1. github-actions commented on Oct 27, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions