Your MCP tool can run as a task. Claude Code 2.1.319 stops waiting for it.
By Lior AharonovFounder, 7IT Solutions ·
What happened
Per its changelog, Claude Code 2.1.319 adds MCP tasks in the terminal: when a server runs a tool call as a task, the client moves it to the background right away and gives Claude the result when it finishes. CLAUDE_CODE_DISABLE_MCP_TASK_BACKGROUND turns that off, and the same release fixes servers on the older handshake that failed to connect or returned empty results.
Why it matters
A slow tool used to hold the whole turn hostage while the agent stared at a spinner. Now a server that reports long work as a task lets the agent keep moving. A server that just blocks until done still holds the turn.
What to do
If a tool of yours runs longer than a few seconds, check whether your SDK can run it as a task, then test it against Claude Code 2.1.319. If your server uses the older handshake, retest the connection on this version.

My take
Lior Aharonov
Founder, 7IT Solutions
Slow tools were always the server owner's problem. Now the client has a lane for them, and only servers that ask for it get in.
Sources
| Claude Code changelog, version 2.1.319 | raw.githubusercontent.com |
Researched with AI tools; every fact is checked against the linked sources.