{"version":"2.1.302","anchor":"remote-bridge-records-a-timestamp-on-pending-close-effort-r","canonical_anchor":"remote-bridge-records-a-timestamp-on-pending-close-effort-r","heading":"Remote control close records gain a timestamp, and effort settings report a request ID","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/remote-bridge-records-a-timestamp-on-pending-close-effort-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Remote control close records gain a timestamp, and effort settings report a request ID\n\nA pending close on a remote connection now records when it happened, and applying settings remotely now also reports an effort_request_id\n\n**What**\n\nThese changes affect programs that drive Claude Code from outside, either through the SDK (the toolkit for controlling Claude Code from your own code) or through a remote connection.\n\n- Pending close: when a remote connection is about to close, the record Claude Code keeps now includes an `at` timestamp. It previously held only a code, a cause and a detail.\n\n- `effort_request_id`: after a controlling program changes session settings through `apply_flag_settings`, the SDK session now also reports metadata that includes `effort_request_id`.\n\n- The handler that applies those settings now receives a second piece of information.\n\n**Why**\n\nThese are small additions to how a controlling program and Claude Code talk to each other. A program that reads close records or session metadata may now see the extra fields.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}