{"version":"2.1.288","anchor":"remotebridge-permission-withdrawn-message-env-secret-expi","canonical_anchor":"remotebridge-permission-withdrawn-message-env-secret-expi","heading":"Remote sessions explain withdrawn permission requests","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remotebridge-permission-withdrawn-message-env-secret-expi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote sessions explain withdrawn permission requests\n\nRemote sessions can now say a permission request was withdrawn because nobody answered it in time, and a `--any-host` flag appears\n\n**Unclear.** It is not clear which commands accept `--any-host` or `--gh-standin`, or what they do.\n\n**What**\n\nSeveral additions relate to remote sessions, where Claude Code runs on another machine and connects to you:\n\n- A new message reads \"This permission request was withdrawn because it was not answered in time.\" A permission request is Claude Code asking you before it does something.\n\n- When a remote environment is set up, Claude Code now also reads how long that environment's secret has before it expires.\n\n- Two new usage events are recorded: one when folder settings are held back, and one about user rules at the moment of connecting.\n\n- A new `--any-host` flag is present, along with a `--gh-standin` option name.\n\n**Why**\n\nIf a permission request in a remote session disappears, this message explains that it timed out.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}