{"version":"2.1.288","anchor":"device-bind-repositories-trusted-log-and-event-now-carry-co","canonical_anchor":"device-bind-repositories-trusted-log-and-event-now-carry-co","heading":"Remote session repository trust log now says what it covers","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/device-bind-repositories-trusted-log-and-event-now-carry-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote session repository trust log now says what it covers\n\nThe log line and usage data for trusting repositories when a remote session is created now say what the trust covers\n\n**Unclear.** What range of things the trust can cover is not known.\n\n**What**\n\nWhen Claude Code links this device to a remote session, it records that repositories were trusted on the request that created the session. That log line now ends by saying what the trust covers, and the usage data sent when the trust is recorded, or refused and then retried, carries the same detail. The refused-and-retried record also now takes its refusal reason from a different place than before.\n\n**Why**\n\nThis is a small diagnostics change, plus a fix to how the refusal reason is reported.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}