TUI attention sound plays repeatedly while idle with no events (WSL2) #40882

Activity

1. anujbolewar commented on Aug 7, 2026

   

   anujbolewar

   on Aug 7, 2026

   More actions

   I started tracing this and need a small log to pin the exact trigger before I can land a precise fix.

   What I found so far: the notification for the completion sound fires in packages/tui/src/feature-plugins/system/notifications.ts on every session.status busy→idle transition per session (deduped only by a module-local active set, so one sound per busy→idle cycle). Server-side, busy is re-published at the top of every agent step (path src/session/processor.ts / the run loop) and idle is published once per completed run. So a repeated idle sound means a session is going busy→idle repeatedly while it looks idle to you — a few candidates: a subagent session completing in the background, a queued/steer prompt re-running, a status that gets stuck busy, or the active session-warming-opt-in plugin.

   To tell them apart, could you capture the actual event timeline? Drop this debug plugin at ~/.config/opencode/plugins/status-log.ts:

   import { appendFile, mkdir } from "node:fs/promises"
   import path from "node:path"
   
   export default {
     id: "debug-status-log",
     async tui(api: any) {
       const file = path.join(process.env.HOME ?? "", ".cache/opencode/status-events.log")
       await mkdir(path.dirname(file), { recursive: true })
       const line = (s: string) => appendFile(file, `${new Date().toISOString()} ${s}\n`).catch(() => {})
       await line("== started ==")
   
       api.event.on("session.status", (e: any) => {
         const parent = api.state.session.get(e.properties.sessionID)?.parentID
         line(`STATUS ${e.properties.sessionID} parent=${parent ?? "-"} ${JSON.stringify(e.properties.status)}`)
       })
       api.event.on("session.idle", (e: any) => {
         line(`IDLE ${e.properties.sessionID}`)
       })
     },
   }

   Then: 1) start opencode2, leave it idle, wait for the sound, 2) quit and paste ~/.cache/opencode/status-events.log.

   What the log tells us:

   • STATUS <id> ... busy then ... idle pairs around each sound + the parent value → whether it's the top-level session (done) or a subagent (subagent_done) cycling.
   • busy with no matching idle → a stuck-busy status.
   • an empty log while the sound plays → not session.status-driven, and I'll look at the audio path instead.

   If you could also run once with session-warming-opt-in disabled and share both logs, that bisects the most likely trigger.
2. github-actions commented on Oct 8, 2026

   

   github-actionsBot

   on Oct 8, 2026 – with GitHub Actions

   Contributor

   More actions

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

   closed this as not plannedon Oct 8, 2026