Skip to content

exec_command repeatedly requests incorrect sandbox permissions and fails before using the required network permission #845

Description

@PierrunoYT

Version / branch / commit

0.6.0

OS and environment

Windows 11 Pro / Powershell

Steps to reproduce

Steps to reproduce

  1. Open the repository in Zero on Windows using PowerShell.
  2. Ask the agent to run:
git branch --show-current
  1. Observe that the command fails with:
additional_permissions requires sandbox_permissions set to "with_additional_permissions"
  1. Run the same command again.
  2. Observe that it fails with:
additional_permissions must include at least one of network or file_system
  1. Ask the agent to create a GitHub issue for the failed command.
  2. Approve the public GitHub issue creation.
  3. Ask the agent to add the second error as a comment to the created issue.
  4. Observe that gh issue comment repeatedly fails or requests additional network permissions instead of posting the comment.

Expected behavior

Expected behavior

  • git branch --show-current should run successfully without requesting additional sandbox permissions.
  • Read-only local Git commands should not require network or file-system write access.
  • The current branch name should be returned directly.
  • When posting a GitHub issue or comment, the tool should request only the required network permission.
  • After the user approves the action, the GitHub command should execute without repeated permission prompts or sandbox configuration errors.

Actual behavior

Actual behavior

  • git branch --show-current fails instead of returning the current branch name.
  • The first attempt returns:
additional_permissions requires sandbox_permissions set to "with_additional_permissions"
  • A later attempt returns:
additional_permissions must include at least one of network or file_system
  • The agent generates invalid or unnecessary additional_permissions settings for a read-only local Git command.
  • When adding a follow-up comment with gh issue comment, the command is blocked by permission errors or triggers another network-access approval prompt.
  • The agent repeatedly retries with different permission configurations instead of successfully executing the commands.

Relevant logs, screenshots, or error messages

Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions