Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Forwarded tool calls now carry request_id and instance_id

Records of tool calls forwarded to another host now include request_id and instance_id, and in-flight updates are batched

Group of 2 Under the hood Internal Changes
JSON All of v2.1.281
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Remote DevicesArea: what it touches
Internal ChangesKind: in v2.1.281,
Internal ChangesSection of the release

What

When a tool call is forwarded to another host and served there, Claude Code keeps records of it. Those records now carry two extra identifiers.

  • The dispatch record (previously tool_use_id, tool, host, host_epoch and dispatched_at) accepts optional request_id and instance_id fields. Each is checked against a pattern, and a malformed value is dropped instead of rejecting the whole record.
  • The in_flight_served_calls record now includes request_id and instance_id and is refreshed when either changes. Before, it was keyed only by host_epoch.
  • Updates to that in-flight record are batched into one notification per short processing step, instead of one for every call added.
  • The directory-sync note written after a remote call is simpler: the deferWrite and exclusive options and the 'taken_in' routine flag are gone.

Why

This is internal plumbing for remote execution. It lets forwarded calls be matched up more reliably and cuts down on repeated update messages.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what these calls are or where a reader would see these records.

See this entry in the whole of v2.1.281 →

Feedback