{"version":"2.1.305","anchor":"new-allow-loopback-field-oncheckpointrequest-tengu-amber-l","canonical_anchor":"new-allow-loopback-field-oncheckpointrequest-tengu-amber-l","heading":"Early groundwork for a loopback policy option and remote checkpoint requests","tier":"soon","area":"Sessions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/new-allow-loopback-field-oncheckpointrequest-tengu-amber-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Early groundwork for a loopback policy option and remote checkpoint requests\n\nPolicies can now record an allow-loopback setting, and remote sessions gained a hook for checkpoint requests, with no visible effect yet\n\n**Unclear.** What the loopback setting, the checkpoint request callback and the new setting actually do is not known.\n\n**What**\n\nA policy that Claude Code reads can now carry an `allow_loopback` value. When that value is `true`, Claude Code records it. Loopback means connections back to your own machine, such as `localhost`.\n\nThe part of Claude Code that handles input and output for remote sessions also gained a callback for checkpoint requests. A callback is a piece of code that runs when a particular event happens. A remotely controlled setting, `tengu_amber_ledger`, also appears.\n\n**Why**\n\nThese look like early pieces of features that are not released yet. Nothing here changes what you see today.\n\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no\n- Present in the build but not switched on"}