{"version":"2.1.293","anchor":"served-shell-settings-hold-gains-a-cause-field-and-a-setti","canonical_anchor":"served-shell-settings-hold-gains-a-cause-field-and-a-setti","heading":"Remotely served shell commands record why they were held and whether settings changed","tier":"internal","area":"Remote Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/served-shell-settings-hold-gains-a-cause-field-and-a-setti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Remotely served shell commands record why they were held and whether settings changed\n\nWhen a remotely served shell command is held on settings, Claude Code now records the cause and notes if settings changed around the command\n\n**What**\n\nWhen Claude Code runs a shell command that came in remotely, the permission check now does more:\n\n- When the command is held back over settings, the reason is recorded.\n\n- Settings are compared before and after the command, and a note is added if they changed around it.\n\n- The follow-up check now reports the kind of error and the HTTP status code when it fails.\n\n**Why**\n\nThis tightens how permissions are handled for remotely served commands and makes a failure easier to explain afterwards.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}