Claude Code Improves Background MCP Tasks: Questions Wait for You and Esc Means Answer Later
Claude Code 2.1.325 improves how background MCP tasks ask the user questions. A question no longer opens over a message being typed, Esc now means "answer later", and Claude is told when a task is waiting so it can point to /tasks. A task stuck after its question was closed is also fixed.
Key Takeaways
- Task questions no longer interrupt a message being typed.
- Esc now means "answer later" and keeps the question in
/tasks. - Claude is told when a task is waiting and can point to
/tasks. - Stuck tasks after a closed or repeated question are fixed.
- The footer says when input is needed.
- Tasks that stopped updating after a lost connection are fixed.
Questions that wait
A background MCP task's question used to open over a message the user was still typing. It now waits until the draft is sent or cleared, and the spinner and turn timer keep running.
Esc means answer later
Esc on a background MCP task's question now means "answer later". Nothing is sent to the server and the question stays in /tasks. A task that got stuck after its question was closed with Esc or asked again is fixed: the footer says it needs input, and Enter in /tasks shows the question again.
Claude knows a task is waiting
Claude is now told when a task is waiting for the user's answer and can point the user to /tasks. Background MCP tasks that stopped updating after another call to the same server lost the connection are also fixed.