What
Some MCP servers (outside tools Claude Code connects to) can run a task in the background and report back later. Claude Code changes how it follows those tasks:
- If the server is removed from your setup, Claude Code keeps checking on the task at a slower pace and looks again after a delay.
- A task's final result can be shown through a new route that stores it with the finished task.
- For remote servers, Claude is told to explain, only if you ask about exiting, that the task keeps running on the server and checking stops when the session ends.
- New follow-up hints, depending on the problem, tell you to use
/mcpto reconnect or sign in. Claude Code does not reconnect the server by itself.
Before, the note at the start of a task said only that the result would arrive as a task notification.
Why
You get clearer guidance when a long MCP task loses its connection, and you know that quitting Claude Code does not stop the work on the server.
Names in the bundle/mcp