### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? In Cowork/Dispatch mode, when the user stops responding for a short period, the platform automatically injects a system-level message into the conversat

[BUG] Dispatch idle-pause triggers accelerating "no visible output" retry loop (not a duplicate of #70422 or #71303)

Status Open

Maintainer reply None cached

Activity 0 comments · opened Aug 9, 2026

Preflight Checklist

[x] I have searched existing issues and this hasn't been reported yet
[x] This is a single bug report (please file separate reports for different bugs)
[x] I am using the latest version of Claude Code

What's Wrong?

In Cowork/Dispatch mode, when the user stops responding for a short period, the platform automatically injects a system-level message into the conversation: "Your previous response had no visible output. Please continue and produce a user-visible response."

This message is injected as if it were a user turn, forcing Claude to respond via SendUserMessage. The moment that response is sent, the platform detects another pause (the user still hasn't typed) and immediately re-injects the same system message, triggering another response. The cycle repeats and accelerates, with messages arriving every few seconds. Claude is required to respond to every injected message — there is no mechanism to suppress or ignore the injected prompts.

Not a duplicate of #70422 or #71303. #70422's trigger is a Bash tool call with no stdout, capped at 2-3 duplicate responses. #71303 is about intentional silence being overridden once. This is Dispatch-specific: triggered by user idle time, and it loops with unbounded acceleration rather than firing once or a few times.

What Should Happen?

Dispatch should not force a response when the user is simply pausing in a conversation. Idle time from the user should not be treated as "no visible output" from Claude. At minimum:

The injected retry prompt should only fire once per idle period, not repeatedly
There should be a substantial cooldown (5+ minutes) before it fires at all
Force-quitting the desktop app should actually stop the loop, not just pause it until the app is reopened

Error Messages/Logs

Your previous response had no visible output. Please continue and produce a user-visible response.

Steps to Reproduce

Start a conversation in Cowork/Dispatch mode (mobile and/or desktop)
Stop responding for a short period (don't type anything)
Observe the system auto-inject: "Your previous response had no visible output. Please continue and produce a user-visible response."
Claude responds to the injected message
Without the user typing anything, the same injected message fires again almost immediately
The cycle repeats and accelerates — messages arrive every few seconds
Force-quit the desktop app — the loop stops while the app is closed
Reopen the desktop app — the loop resumes immediately, picking back up where it left off

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Latest available version as of August 2026 (exact version number not readily available from Cowork desktop app UI)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Screen floods with rapid messages every 4-10 seconds. Happens on Android mobile and Windows desktop simultaneously if both are open. Particularly disruptive during emotional or slow-paced conversations where pauses are normal.

Suggested fix: remove the "no visible output" injection entirely for Dispatch/conversational sessions, or add a substantial cooldown (5+ minutes) and limit it to one injection per session rather than looping indefinitely.

View original on GitHub ↗