Microsoft GH-300 Bundle

For the different scenario The CLI asks to delete all tracked files as part of a cleanup, "Deny the command and provide a safe restricted cleanup scope" could be appropriate. Approval prompts exist to prevent destructive unreviewed actions. The present requirement is A team considers allowing every CLI tool without confirmation on a production machine, which calls for "Avoid blanket allow-all and use isolated sandboxed scope". Unrestricted tools can create destructive side effects.

"Enable assisted permissions where supported and keep policy enforcement" targets A user wants routine safe commands considered for assisted approval. Assisted approval is narrower than blanket authorization. That differs from A team considers allowing every CLI tool without confirmation on a production machine; the required decision here is "Avoid blanket allow-all and use isolated sandboxed scope". Unrestricted tools can create destructive side effects.

The action "Use manual permission mode and review each proposed action" is useful when A security-sensitive session should request confirmation before each new tool. Manual mode maintains explicit oversight of unapproved operations. Under the stated condition A team considers allowing every CLI tool without confirmation on a production machine, instead choose "Avoid blanket allow-all and use isolated sandboxed scope". Unrestricted tools can create destructive side effects.

The action "Rotate the exposed credentials and carefully review the redaction diff" is useful when A prompt asks the CLI to remove secrets from a tracked file. Deleting plaintext from one file may not revoke or remove leaked credentials. Under the stated condition A CLI agent wants to edit configuration and a generated lockfile at once, instead choose "Review both proposed file changes before allowing writes". Tool execution can modify multiple related files.

The alternative "Compare diffs and preserve the validated version unless approved" fits another situation: An agent proposes overwriting an existing hand-reviewed script. Automatic regeneration can discard important manual decisions. Here the condition is A CLI agent wants to edit configuration and a generated lockfile at once; use "Review both proposed file changes before allowing writes" instead. Tool execution can modify multiple related files.

The alternative "Choose an authorized output path within the workspace" addresses A script generator is asked to place logs in a protected system directory. Filesystem policies should constrain writes to approved locations. It does not resolve A CLI agent wants to edit configuration and a generated lockfile at once; the correct choice is "Review both proposed file changes before allowing writes". Tool execution can modify multiple related files.

The action "Compare diffs and preserve the validated version unless approved" is useful when An agent proposes overwriting an existing hand-reviewed script. Automatic regeneration can discard important manual decisions. Under the stated condition A user wants the agent to generate a migration script but not run it, instead choose "Request script creation with execution explicitly forbidden". Creating a file and executing it are distinct permissions.

The alternative "Review both proposed file changes before allowing writes" addresses A CLI agent wants to edit configuration and a generated lockfile at once. Tool execution can modify multiple related files. It does not resolve A user wants the agent to generate a migration script but not run it; the correct choice is "Request script creation with execution explicitly forbidden". Creating a file and executing it are distinct permissions.

For the different scenario A prompt asks the CLI to remove secrets from a tracked file, "Rotate the exposed credentials and carefully review the redaction diff" could be appropriate. Deleting plaintext from one file may not revoke or remove leaked credentials. The present requirement is A user wants the agent to generate a migration script but not run it, which calls for "Request script creation with execution explicitly forbidden". Creating a file and executing it are distinct permissions.

The alternative "Review both proposed file changes before allowing writes" fits another situation: A CLI agent wants to edit configuration and a generated lockfile at once. Tool execution can modify multiple related files. Here the condition is A script generator is asked to place logs in a protected system directory; use "Choose an authorized output path within the workspace" instead. Filesystem policies should constrain writes to approved locations.

The alternative "Request script creation with execution explicitly forbidden" addresses A user wants the agent to generate a migration script but not run it. Creating a file and executing it are distinct permissions. It does not resolve A script generator is asked to place logs in a protected system directory; the correct choice is "Choose an authorized output path within the workspace". Filesystem policies should constrain writes to approved locations.

"Compare diffs and preserve the validated version unless approved" targets An agent proposes overwriting an existing hand-reviewed script. Automatic regeneration can discard important manual decisions. That differs from A script generator is asked to place logs in a protected system directory; the required decision here is "Choose an authorized output path within the workspace". Filesystem policies should constrain writes to approved locations.

The alternative "Request script creation with execution explicitly forbidden" addresses A user wants the agent to generate a migration script but not run it. Creating a file and executing it are distinct permissions. It does not resolve A prompt asks the CLI to remove secrets from a tracked file; the correct choice is "Rotate the exposed credentials and carefully review the redaction diff". Deleting plaintext from one file may not revoke or remove leaked credentials.

"Choose an authorized output path within the workspace" targets A script generator is asked to place logs in a protected system directory. Filesystem policies should constrain writes to approved locations. That differs from A prompt asks the CLI to remove secrets from a tracked file; the required decision here is "Rotate the exposed credentials and carefully review the redaction diff". Deleting plaintext from one file may not revoke or remove leaked credentials.

The action "Review both proposed file changes before allowing writes" is useful when A CLI agent wants to edit configuration and a generated lockfile at once. Tool execution can modify multiple related files. Under the stated condition A prompt asks the CLI to remove secrets from a tracked file, instead choose "Rotate the exposed credentials and carefully review the redaction diff". Deleting plaintext from one file may not revoke or remove leaked credentials.

For the different scenario A prompt asks the CLI to remove secrets from a tracked file, "Rotate the exposed credentials and carefully review the redaction diff" could be appropriate. Deleting plaintext from one file may not revoke or remove leaked credentials. The present requirement is An agent proposes overwriting an existing hand-reviewed script, which calls for "Compare diffs and preserve the validated version unless approved". Automatic regeneration can discard important manual decisions.

"Request script creation with execution explicitly forbidden" targets A user wants the agent to generate a migration script but not run it. Creating a file and executing it are distinct permissions. That differs from An agent proposes overwriting an existing hand-reviewed script; the required decision here is "Compare diffs and preserve the validated version unless approved". Automatic regeneration can discard important manual decisions.

The action "Choose an authorized output path within the workspace" is useful when A script generator is asked to place logs in a protected system directory. Filesystem policies should constrain writes to approved locations. Under the stated condition An agent proposes overwriting an existing hand-reviewed script, instead choose "Compare diffs and preserve the validated version unless approved". Automatic regeneration can discard important manual decisions.

The alternative "Continue the existing session and inspect the current working tree" fits another situation: A developer needs to resume work without losing approved file changes. Resumption should preserve actual state rather than recreate it. Here the condition is A long-running conversation no longer recalls a critical original requirement; use "Restate the requirement and inspect the session's effective context" instead. Context management can compact earlier details.

The alternative "Start a separate scoped CLI session for that task" addresses A teammate wants to start an independent task with separate assumptions. Context isolation reduces interference between unrelated goals. It does not resolve A long-running conversation no longer recalls a critical original requirement; the correct choice is "Restate the requirement and inspect the session's effective context". Context management can compact earlier details.

For the different scenario A developer wants to check how much conversation context is in use, "Use the CLI's supported context inspection command" could be appropriate. Explicit context visibility helps manage long interactions. The present requirement is A long-running conversation no longer recalls a critical original requirement, which calls for "Restate the requirement and inspect the session's effective context". Context management can compact earlier details.

The alternative "Scope subsequent file reads and summarize relevant findings" fits another situation: An agent produces a large dependency analysis consuming most context. Large tool outputs can crowd useful information out of context. Here the condition is A developer needs to resume work without losing approved file changes; use "Continue the existing session and inspect the current working tree" instead. Resumption should preserve actual state rather than recreate it.

The alternative "Use the CLI's supported context inspection command" addresses A developer wants to check how much conversation context is in use. Explicit context visibility helps manage long interactions. It does not resolve A developer needs to resume work without losing approved file changes; the correct choice is "Continue the existing session and inspect the current working tree". Resumption should preserve actual state rather than recreate it.

For the different scenario A long-running conversation no longer recalls a critical original requirement, "Restate the requirement and inspect the session's effective context" could be appropriate. Context management can compact earlier details. The present requirement is A developer needs to resume work without losing approved file changes, which calls for "Continue the existing session and inspect the current working tree". Resumption should preserve actual state rather than recreate it.

The alternative "Start a separate scoped CLI session for that task" addresses A teammate wants to start an independent task with separate assumptions. Context isolation reduces interference between unrelated goals. It does not resolve An agent produces a large dependency analysis consuming most context; the correct choice is "Scope subsequent file reads and summarize relevant findings". Large tool outputs can crowd useful information out of context.

For the different scenario A long-running conversation no longer recalls a critical original requirement, "Restate the requirement and inspect the session's effective context" could be appropriate. Context management can compact earlier details. The present requirement is An agent produces a large dependency analysis consuming most context, which calls for "Scope subsequent file reads and summarize relevant findings". Large tool outputs can crowd useful information out of context.

The action "Continue the existing session and inspect the current working tree" is useful when A developer needs to resume work without losing approved file changes. Resumption should preserve actual state rather than recreate it. Under the stated condition An agent produces a large dependency analysis consuming most context, instead choose "Scope subsequent file reads and summarize relevant findings". Large tool outputs can crowd useful information out of context.

For the different scenario A developer needs to resume work without losing approved file changes, "Continue the existing session and inspect the current working tree" could be appropriate. Resumption should preserve actual state rather than recreate it. The present requirement is A teammate wants to start an independent task with separate assumptions, which calls for "Start a separate scoped CLI session for that task". Context isolation reduces interference between unrelated goals.

"Scope subsequent file reads and summarize relevant findings" targets An agent produces a large dependency analysis consuming most context. Large tool outputs can crowd useful information out of context. That differs from A teammate wants to start an independent task with separate assumptions; the required decision here is "Start a separate scoped CLI session for that task". Context isolation reduces interference between unrelated goals.

The action "Use the CLI's supported context inspection command" is useful when A developer wants to check how much conversation context is in use. Explicit context visibility helps manage long interactions. Under the stated condition A teammate wants to start an independent task with separate assumptions, instead choose "Start a separate scoped CLI session for that task". Context isolation reduces interference between unrelated goals.

"Scope subsequent file reads and summarize relevant findings" targets An agent produces a large dependency analysis consuming most context. Large tool outputs can crowd useful information out of context. That differs from A developer wants to check how much conversation context is in use; the required decision here is "Use the CLI's supported context inspection command". Explicit context visibility helps manage long interactions.

The action "Start a separate scoped CLI session for that task" is useful when A teammate wants to start an independent task with separate assumptions. Context isolation reduces interference between unrelated goals. Under the stated condition A developer wants to check how much conversation context is in use, instead choose "Use the CLI's supported context inspection command". Explicit context visibility helps manage long interactions.

The alternative "Restate the requirement and inspect the session's effective context" fits another situation: A long-running conversation no longer recalls a critical original requirement. Context management can compact earlier details. Here the condition is A developer wants to check how much conversation context is in use; use "Use the CLI's supported context inspection command" instead. Explicit context visibility helps manage long interactions.