What
When a command sent from a remote 'bridge' session is a /clear command, Claude Code now recognizes this and automatically dismisses any dialog currently open in the local session, rather than leaving that dialog in the way. It also records a telemetry event when this happens.
Why
Previously, a local dialog box could block a /clear request coming from a remote session, leaving things stuck. This change lets that clear command go through without requiring someone at the local machine to close the dialog first.
Names in the bundle/clear
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on How the agent loop works touched a line naming /clear after this was published.
With [streaming input](/docs/en/agent-sdk/streaming-vs-single-mode), a message that is still queued when a turn ends at the max-turns limit stays queued. Claude Code doesn't add it to that turn's last model call. It starts a new turn for t…agent-sdk/agent-loop see the edit
Confirmed since
Anthropic's documentation has since written up /clear, on Monitoring.
`event.sequence` starts at 0 each time a Claude Code process starts and counts up for the life of that process. It keeps counting across `/clear`, which assigns a new `session.id`. If you [resume a session without forking](/docs/en/how-cla…monitoring-usage see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /clear, on Monitoring.
Anthropic's release notes agree
Fixed /clear from Remote Control waiting on SessionStart hooks and on open terminal dialogs before completing
The name it cites is new in this build
New in this build: tengu_woolly_owl