What
When work moves to the background, Claude Code shows a "Running in background" hint naming a command to follow it. Under some conditions the hint now names /workflows and says "to monitor", where it used to name /tasks and say "to view".
A permission for a projects entry point was also added to the connection Claude Code uses with other apps.
Why
You may see /workflows suggested in the hint where you used to see /tasks.
Names in the bundle/workflows/tasks
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.
Confirmed since
Anthropic's documentation has since written up /workflows, on Orchestrate subagents at scale with dynamic workflows.
* **Failed**: runs again, and so does every agent the script starts after it, even ones that completed. Stopping one agent alone, by selecting it in [`/workflows`](#watch-the-run) and pressing `x`, counts as failing.workflows see the edit
Confirmed since
Anthropic's documentation has since written up /tasks, on Transports Charter.
* **[Tasks and Events WG](/community/working-groups/tasks-events)**: The Tasks andcommunity/working-groups/transports see the edit
Added since
A small documentation edit on Scientific Computing Charter touched a line naming /tasks after this was published.
* **[Tasks and Events WG](/community/working-groups/tasks-events)**: Tasks are the foundation for the long-runningcommunity/interest-groups/scientific-computing see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Scientific Computing Charter touched a line naming /tasks after this was published.
Anthropic's release notes agree
[VSCode] Changed background sub-agents to show as one status line under their Agent card instead of streaming every step into the chat; the…