{"version":"2.1.300","anchor":"remote-session-create-permission-mode-can-differ-on-the-run","canonical_anchor":"remote-session-create-permission-mode-can-differ-on-the-run","heading":"Cloud sessions on self-hosted runners stop sending your settings' permission mode and effort","tier":"notice","area":"Cloud Sessions","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/remote-session-create-permission-mode-can-differ-on-the-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Cloud sessions on self-hosted runners stop sending your settings' permission mode and effort\n\nWhen creating a cloud session on a self-hosted runner, a mode or effort from your settings is no longer sent, with a notice to use --permission-mode\n\n**What**\n\nWhen Claude Code creates a cloud session (one that runs on another machine, for example with `--remote`), the request now says where the permission mode (how much Claude may do without asking) and the effort level came from. New fields `personAskedForSession`, `isModeFromSettings` and `isEffortFromSettings` tell an explicit request apart from a value that only came from your settings files.\n\n- Self-hosted runners: if the session runs on a self-hosted runner (a machine your organization runs), a permission mode or effort that came from settings is no longer sent. Before, the permission mode was always sent. The result is marked with `settingsModeOnRunner` (`not_sent` or `not_pushed`), with `self_hosted_runner` given as the reason.\n\n- Notice: new code compares the mode with and without your settings. If your settings' default permission mode doesn't apply on a self-hosted runner, a notice tells you to relaunch with `--permission-mode`. It is shown as a warning when the mode is `plan`. The finder did not locate where this notice is called from.\n\n- Timing: the permission mode notice is now worked out after the session has been created, using the mode the runner reports, rather than only from the decision made before creation.\n\n- Sign-in: attaching to and creating a cloud session now go through an extra authentication step first, and the access token is chosen from your profile (`consoleProfileBearer`).\n\n**Why**\n\nThe mode shown for a remote session may now match what the runner actually applied. On a self-hosted runner, a default mode in your local settings no longer carries over, so pass `--permission-mode` on launch if you want a specific mode there.\n\n- Area: Cloud Sessions\n- Names: `--remote`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}