[FEATURE] Allow Claude to intentionally produce no visible output

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

There’s no way for Claude to intentionally stay silent. The system treats “no visible output” as an error, but sometimes silence is the correct response — especially in conversational/coaching contexts where:
• The conversation has naturally ended
• A reply would be redundant or counterproductive
• The agent has explicitly committed to not responding

Proposed Solution

Allow Claude to produce an intentional “no response” that the system accepts as valid output, rather than forcing a visible message on every turn. Something like an explicit “acknowledge without responding” action.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

I’m using Claude Code as a personal coaching agent. During a conversation, Claude promised me it wouldn’t reply after I said goodbye — we’d explicitly discussed that unnecessary replies after a farewell were a pattern we wanted to break.
When I said “ok” to close the conversation, Claude correctly produced no output. But the system immediately prompted it with:
“[Your previous response had no visible output. Please continue and produce a user-visible response.]”
This forced Claude to respond, breaking the promise it had just made. It happened twice in the same conversation.