Stream Watcher

Detect silent subagent failures in opencode, especially stream stalls and quiet no-op turns.

Quick start

opencode-stream-watcher catches a narrow but painful class of silent subagent failures: a subagent is still "running," but either the LLM stream has gone silent or a known quiet no-op turn finished without visible progress.

1. Register the published plugin

Add this to your opencode.json:

{
  "plugin": ["opencode-stream-watcher"]
}

Restart opencode. That's it.

By default the plugin will:

• show a sticky WARN toast after 90s of stream silence
• show a RESUME toast if output starts moving again
• auto-abort a stalled session after 10 minutes
• flag quiet no-op turns for the built-in watched specialist set
• write structured watchdog events into opencode's existing log files

2. Know what you'll see

Signal	When it appears	What to do
WARN toast	A running subagent goes silent past warnThresholdMs	Press Esc to interrupt, or ask your foreground agent to call watchdog_abort
RESUME toast	A warned stalled stream starts producing output again	Usually no action needed
ABORT event	Silence crosses abortThresholdMs and auto-abort is enabled	Re-run or inspect the stuck task
No-op event	A watched quiet specialist finishes without visible work surfaced	Check whether the turn actually did what you expected

3. Check logs or tools when needed

• Logs live under ~/.local/share/opencode/log/
• Foreground-agent tools:
  • watchdog_status
  • watchdog_abort

For local plugin development and symlink-based testing, skip to CONTRIBUTING.md and docs/TESTING.md.

The problem

You delegate work to an opencode subagent. The TUI shows it's running. Minutes pass. No output, or a quiet specialist turn ends with no meaningful work surfaced. The agent isn't necessarily crashed — sometimes the LLM stream just stopped emitting tokens, and sometimes the turn was a silent no-op.

The fingerprint in ~/.local/share/opencode/log/:

INFO 10:14:00 service=llm modelID=gpt-5.4 agent=backend-specialist mode=subagent stream
...                                          (22 minutes of silence)
INFO 10:36:36 service=session.prompt cancel
ERROR 10:36:36 error=Aborted process

You only know something went wrong because you noticed, hit Esc, and reconstructed the timeline after the fact.

Two silent failure modes, not one

Mode	What you see	What the plugin verifies at runtime
Stream stall	A subagent still looks busy, but the stream stops producing parts	Session activity goes idle past the WARN/ABORT thresholds
Quiet no-op turn	A built-in watched specialist finishes without visible work surfaced	The finished turn matches the plugin's narrow no-op checks for the default watched agent set

Both are user-visible silent failures. They are different runtime checks, which is why stall thresholds and no-op watching stay documented separately.

What this plugin does

Subscribes to the opencode message bus, timestamps every streaming chunk per session, and layers in focused runtime checks for silent failures:

• Warns you with a sticky TUI toast when a session goes quiet past a threshold (default 90s).
• Lets you know when it recovers, via a transient success toast.
• Auto-aborts the stalled session after 10 minutes by default.
• Flags quiet no-op turns for the built-in watched specialist set.
• Logs everything through opencode's structured log so you can grep incident history.

No system notifications, no terminal bells, no busy-work. Just focused TUI feedback, structured logs, no-op visibility for known quiet specialists, and a default safety stop for long silent stream stalls.

What a warning looks like in the TUI:

┌──────────────────────────────────────┐
│ ⏸  Stream stalled                ⚠  │
│                                      │
│ backend-specialist · ses_1a16…       │
│ Silent for 95s (last: reasoning).    │
│                                      │
│ Esc to interrupt · ask your          │
│ foreground agent to call             │
│ watchdog_abort.                      │
└──────────────────────────────────────┘

Install

Requires: opencode v1.2 or later (uses the plugin API).

For normal use, register the published package in opencode.json:

{
  "plugin": ["opencode-stream-watcher"]
}

Then restart opencode.

That's it — by default you get a WARN at 90s and an auto-abort at 10 minutes.

For local development with a built dist/plugin.js symlink, use the workflow in CONTRIBUTING.md instead of the package registration above.

Verify it loaded

On startup the plugin writes a load line to opencode's log. Open the latest log file under ~/.local/share/opencode/log/ and look for service=stream-watchdog with loaded.

You should see an entry like service=stream-watchdog level=info ... loaded.

Configure

All keys optional; defaults shown:

{
  "plugin": ["opencode-stream-watcher"],
  "stream-watchdog": {
    "warnThresholdMs": 90000,
    "abortThresholdMs": 600000,
    "tickMs": 10000,
    "toast": true,
    "log": true,
    "noop": {
      "enabled": true
    },
    "duration": {
      "enabled": true,
      "minToastMs": 5000,
      "slowToastMs": 30000
    }
  }
}

Key	Default	Meaning
warnThresholdMs	90000	Idle milliseconds before a stream-stall WARN toast fires
abortThresholdMs	600000	Idle ms before auto-abort. Set 0 to opt out explicitly.
tickMs	10000	How often the watchdog checks tracked sessions
toast	true	Show TUI toasts
log	true	Write structured log entries via client.app.log
noop.enabled	true	Watch known quiet no-op turns for the built-in code-mutating specialists: coder, backend-specialist, frontend-specialist, devops-specialist, test-engineer, code-simplifier, svelte-file-editor
duration.enabled	true	Emit turn-duration logs and end-of-turn toasts
duration.minToastMs	5000	Only show a turn-done toast when a turn takes at least this long
duration.slowToastMs	30000	Upgrade the toast to slow-turn warning styling at or above this duration
perAgent	{}	Override stall thresholds, disable no-op watching for a default watched agent, and tune nested duration toast thresholds by exact agent name

Per-agent thresholds

{
  "stream-watchdog": {
    "warnThresholdMs": 90000,
    "abortThresholdMs": 600000,
    "perAgent": {
      "code-reviewer-deep": {
        "warnThresholdMs": 300000,
        "abortThresholdMs": 0
      },
      "coder": {
        "warnThresholdMs": 60000,
        "abortThresholdMs": 120000,
        "noopWatch": false
      }
    }
  }
}

Use perAgent when one agent class naturally runs quieter, should auto-abort sooner, should opt out with 0, needs different duration toast thresholds, or should disable no-op watching for one default watched agent with noopWatch: false. By default, no-op watching is enabled for coder, backend-specialist, frontend-specialist, devops-specialist, test-engineer, code-simplifier, and svelte-file-editor only; agents outside that set are never no-op flagged.

Turn-duration reporting

By default the plugin logs completed turns as TURN_DURATION and shows an info toast (⌛ Turn done) for turns that take at least 5s. At 30s or above, that toast becomes a warning (⌛ Turn done · slow).

{
  "stream-watchdog": {
    "duration": {
      "enabled": true,
      "minToastMs": 5000,
      "slowToastMs": 30000
    },
    "perAgent": {
      "code-reviewer-deep": {
        "duration": {
          "minToastMs": 15000,
          "slowToastMs": 60000
        }
      },
      "doc-writer": {
        "duration": {
          "minToastMs": 3000,
          "slowToastMs": 20000
        }
      }
    }
  }
}

Per-agent duration overrides support minToastMs and slowToastMs only. duration.enabled is global.

Opt out of auto-abort

Set abortThresholdMs to 0 when you want WARN/RESUME behavior without auto-abort.

{
  "stream-watchdog": {
    "warnThresholdMs": 90000,
    "abortThresholdMs": 0
  }
}

The default remains 600000 unless you override it.

Migration note for older configs

If you already raised warnThresholdMs above the default 600000, also raise abortThresholdMs above your WARN threshold or set abortThresholdMs to 0.

Otherwise the watchdog can auto-abort before it ever reaches WARN.

Tooling

The plugin also exposes two foreground-agent tools:

• watchdog_status — inspect tracked sessions and recent watchdog events
• watchdog_abort — abort a specific stalled session, or the longest-idle tracked session if you omit an ID

Example watchdog_status response:

stream-watchdog: tracking 2 sessions.
Tracked sessions:
- sessionID=ses_1a16c8b9 agent=backend-specialist slug=ses_1a16… idleMs=95000 lastPartKind=reasoning state=warned
- sessionID=ses_7bc2f41e agent=doc-writer slug=ses_7bc2… idleMs=12000 lastPartKind=text lastTurnMs=8400 state=tracking

Recent events (oldest → newest):
- time=2026-05-28T14:01:35.000Z type=WARN sessionID=ses_1a16c8b9 agent=backend-specialist
- time=2026-05-28T14:03:12.000Z type=RESUME sessionID=ses_f03d91aa agent=code-reviewer

Example watchdog_abort result:

{
  "aborted": true,
  "sessionID": "ses_1a16c8b9",
  "agent": "backend-specialist",
  "idleMs": 95000
}

Reaction paths

When a stream-stall WARN toast appears:

You want to…	Do this
Cancel the stalled session	Esc — opencode's interrupt key. In the TUI, this typically reaches the running subagent.
Abort only the stuck subagent	Ask your foreground agent to call watchdog_abort with the stalled sessionID, or let it pick the longest-idle tracked session
Wait it out	Sticky toast stays until activity resumes (RESUME toast confirms) or auto-abort fires
Restart the whole session	If the subagent stays wedged or repeated stalls suggest a bad state, restart opencode and retry
Adjust thresholds	Change the global or perAgent config above, then restart opencode

Troubleshooting

Problem	What to check
No toast, no log events	Confirm the plugin is registered in opencode.json, restart opencode, then check the latest file under ~/.local/share/opencode/log/ for service=stream-watchdog ... loaded
WARN fired too early or too late	Check warnThresholdMs, tickMs, and any perAgent override for that exact agent name
A stall warned but did not auto-abort	Confirm abortThresholdMs is not 0 and that any per-agent override did not disable abort for that agent
You want selective abort	Use watchdog_abort instead of killing the entire opencode session
You need a repro recipe	Use docs/TESTING.md and scripts/stall-fixture.md

How it works

opencode bus ──► event hook ──► per-session lastActivity map
                                         │
                              every tickMs (10s)
                                         ▼
                              ┌─ idle > warnThreshold  ──► WARN toast + log
state machine: tracking ─────►│
                              └─ idle > abortThreshold ──► session.abort() + error toast + log
                                         │
                              activity resumes
                                         ▼
                                   RESUME toast + log

The watchdog reads message.part.updated (fires on every streaming chunk — text, reasoning, or tool delta) and session.status events. It emits a WARN when activity goes silent past warnThresholdMs, RESUME if it picks back up, and aborts when silence crosses abortThresholdMs unless you explicitly set that threshold to 0. Toasts go through client.tui.showToast(); the abort goes through client.session.abort().

Details and the why behind each decision: docs/DESIGN.md.

Roadmap

Current releases already include the v1 docs shape described above: WARN/RESUME/ABORT toasts, structured logs, per-agent thresholds, watchdog_status, watchdog_abort, turn-duration reporting, stats counters, and empirical threshold guidance.

The scope stays intentionally narrow: detect silent stalls, surface them clearly, and optionally abort them. Live tracking stays on the project board and milestones.

Contributing

PRs welcome. Start with AGENTS.md and CONTRIBUTING.md. Good-first-issues are tagged.

Not affiliated

opencode is built by Anomaly. This plugin is independent and unaffiliated.

License

MIT — see LICENSE.