{"version":"2.1.281","anchor":"remote-tools-given-up-call-records-use-the-journals-host-an","canonical_anchor":"remote-tools-given-up-call-records-use-the-journals-host-an","heading":"Remote-tools given-up call records use the journal's host and epoch","tier":"internal","area":"Remote Devices","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-tools-given-up-call-records-use-the-journals-host-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote-tools given-up call records use the journal's host and epoch\n\nRecords of abandoned remote tool calls now use the journal's host and epoch and a new machineHadCall field\n\n**Unclear.** The finding does not say what a reader sees differently as a result of this change.\n\n**What**\n\nWhen a tool call run remotely is given up, Claude Code writes a record of it so it can be corrected later. For calls that were adopted, that record now uses `journalHost` and `journalEpoch`. The `onApprovalLeg` field is replaced by `machineHadCall`, which is true in these cases:\n\n- The call was waiting for approval\n\n- The call was being reconciled while in progress\n\n- The call was adopted as `ask_in_flight`\n\n- The call was adopted as `interrupted`\n\n**Why**\n\nThe record of an abandoned call now points at the machine and run that actually held it, which affects how a later correction is matched to it.\n\n- Area: Remote Devices\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}