{"version":"2.1.287","anchor":"remote-tool-serve-new-stale-answer-and-ask-seats-full-outco","canonical_anchor":"remote-tool-serve-new-stale-answer-and-ask-seats-full-outco","heading":"Remote tool requests can now end as too old or as turned away for lack of room","tier":"internal","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/remote-tool-serve-new-stale-answer-and-ask-seats-full-outco","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Remote tool requests can now end as too old or as turned away for lack of room\n\nClaude Code now records when a remote tool answer is too old and when no slots are free for a remote request\n\n**Unclear.** It is unclear whether these are only new log labels or also change what happens to the requests.\n\n**What**\n\nIn some setups, tools are run on another machine and the answers come back over the network. Claude Code's logs for this now record two new outcomes:\n\n- An answer was judged too old, based on when the request was made.\n\n- A request was turned away because all the slots for such requests were already in use.\n\nBefore this change, the only recorded reasons were answers with no date, parts that could not be dated, and stale parts.\n\n**Why**\n\nThe new outcomes point to remote tool requests now having a limit on how many can run at once, and to answers being refused when they arrive too late.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}