[DOCS] Agent stop notification docs omit who-stopped attribution and updated wording

Open 💬 0 comments Opened Jun 23, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/agent-view
https://code.claude.com/docs/en/remote-control
https://code.claude.com/docs/en/agent-teams

Section/Topic

Agent stop/finish notifications, including who stopped the agent and expected notification wording.

Current Documentation

The agent view docs define stopped sessions only as:

Stopped - The session was stopped with Ctrl+X or claude stop

The Remote Control docs say:

Claude decides when to push. It typically sends one when a long-running task finishes or when it needs a decision from you to continue.

The Agent Teams docs say:

Idle notifications: when a teammate finishes and stops, they automatically notify the lead.

What's Wrong or Missing?

Claude Code v2.1.187 fixed agent stop notifications to correctly attribute who stopped the agent and changed wording from came to rest to finished / stopped.

The current docs do not document that stop notifications identify who stopped the agent, what finish/stop notification wording users should expect, or how this applies across agent view, Remote Control push notifications, and teammate idle notifications.

Suggested Improvement

Add a short note near the agent-view session-state table and cross-reference it from Remote Control notifications:

When a background agent finishes or is stopped, Claude Code notifications distinguish between agents that finished normally and agents that were stopped. Stop notifications identify who stopped the agent, such as you stopping it with Ctrl+X or claude stop, so recipients can tell whether the stop was intentional.

If agent-team notifications use the same wording, update the Agent Teams idle notification bullet to clarify that teammates notify the lead when they finish normally or are stopped, and that stop notifications include attribution.

Impact

Medium - Makes feature difficult to understand

Additional Context

v2.1.187 changelog context: Fixed agent stop notifications not correctly attributing who stopped the agent, and improved wording ("finished"/"stopped" instead of "came to rest").

Duplicate search found no exact duplicate. Nearby but non-duplicate issues include #60400 for completion notification duration and #31683 for sub-agent completion notification content.

View original on GitHub ↗