{"version":"2.1.282","anchor":"device-bind-link-payload-drops-issued-at-timestamp","canonical_anchor":"device-bind-link-payload-drops-issued-at-timestamp","heading":"Remote tool-host binding request no longer carries a timestamp","tier":"internal","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/device-bind-link-payload-drops-issued-at-timestamp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Remote tool-host binding request no longer carries a timestamp\n\nThe request Claude Code sends to link a device to a remote tool host no longer includes an issued-at time and is now laid out as separate fields\n\n**Unclear.** What the binding request is used for, and why the timestamp was dropped, is not clear.\n\n**What**\n\nWhen Claude Code links a device to a remote tool host (another machine that runs tools on its behalf), it sends a binding request. That request no longer includes the 8-byte timestamp recording when it was issued. Its contents are also now packed as a list of separate fields, each prefixed with its length, instead of one joined-up block of data.\n\n**Why**\n\nThis is a change to the format two programs use to talk to each other, so nothing looks different in normal use. It can matter if the two ends of a link are running different versions of Claude Code and expect different formats.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}