web: session icon shows no progress indicator while a background shell runs #56660

Activity

1. opencode-agent commented on Oct 18, 2026

   

   opencode-agentBot

   on Oct 18, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report. I can confirm this on 2.0.32 and on the latest dev (63c1a27).

   What I checked:

   • Server: the simulated model starts sleep 300 with the shell tool's background: true option, and the turn ends. The server then reports the session as idle (session.active() is empty, and the session has an idle timestamp). The shell list still shows the shell as running, with metadata.sessionID pointing at that session. The script below reproduces this.
   • Web app: I used the app's e2e harness with that same data. A tab whose session is running shows the progress indicator. A tab whose session is idle but owns a running background shell shows the project avatar instead, as in the screenshot below.

   This matches your analysis: useSessionTabAvatarState only looks at session status and pending inbox items, never at data.shell. Related:

   • TUI session list shows no activity spinner for background shell commands #51810 / fix(tui): show the session list spinner for background shell commands #51811: the same gap in the TUI session list
   • fix(core): keep sessions active while background work is outstanding #53211: a server-side change to keep sessions active while background work is outstanding

   

   Reproduction script (drive.ts)

   // Reproduces #56660 at the server/data level the web app reads:
   // after a turn that started a background shell ends, the session is no longer
   // reported as active/running, while the shell is still running. The web app's
   // useSessionTabAvatarState only checks session status + pending inbox, so the
   // tab/home icon falls back to the project avatar.
   import { Effect } from "effect"
   import { Llm, OpenCodeDriver } from "opencode-drive"
   
   export default OpenCodeDriver.use(
     { ...(process.env.OC_DEV ? { opencode: { dev: process.env.OC_DEV } } : {}), project: { git: true } },
     ({ ui, llm, opencode }) =>
       Effect.gen(function* () {
         yield* llm.queue(
           Llm.toolCall({
             index: 0,
             id: "call_bg",
             name: "shell",
             input: { command: "sleep 300", description: "Sleep in background", background: true },
           }),
           Llm.finish("tool-calls"),
         )
         yield* llm.queue(Llm.text("Started sleep 300 in the background. Turn over."))
         yield* ui.submit("Run sleep 300 in the background")
         yield* ui.waitFor("Turn over.")
         yield* Effect.sleep(3000)
         const active = yield* Effect.orDie(opencode.session.active())
         const shells = yield* Effect.orDie(opencode.shell.list())
         const sessions = yield* Effect.orDie(opencode.session.list())
         yield* Effect.log("SESSIONS " + JSON.stringify(sessions).slice(0, 600))
         yield* Effect.log("ACTIVE " + JSON.stringify(active))
         yield* Effect.log("SHELLS " + JSON.stringify(shells).slice(0, 1500))
       }),
   )

   Run it with opencode-drive: opencode-drive run ./drive.ts. It drives opencode from your PATH; set OC_DEV to the path of an OpenCode checkout to run that from source instead.
2. opencode-agent

   added

   reproduced

   on Oct 18, 2026
3. dluc commented on Nov 8, 2026

   

   dluc

   on Nov 8, 2026

   Last edited by dluc

   More actions

   This also affects OpenCode Desktop 2.2.5 and session API consumers, not just the web session icon. In Desktop, I see a session appear stopped while a shell script is still running in the background. API clients that derive their Working/idle indicator from session.active() can also show the session as stopped when it is omitted after the agent turn ends, even though its shell remains active.

   Please consider the impact on session API consumers as well as the built-in UI. If background shell activity is intentionally separate from agent execution status, an accessible way for API clients to distinguish it would help avoid displaying the session as fully stopped.