Skip to content

[Feedback]: Have proper sandboxed execution logic #8

Description

@claell

What problem are you trying to solve?

The current permission settings are not sufficient for my use case. I general, the available approval modes are hard for me to understand.

What would improve it?

What I want is sandboxed execution (I am on Windows). A bit like in Codex (potentially the only app that got this right; GitHub Copilot in VS Code is not doing this, neither is Claude Code. They have a sandbox. Reads are typically allowed. Writings outside the project folder, internet access, ... requires permission. And because they have a sandbox, they can also apply this to arbitrary command executions. They can ensure that nothing can be circumvented, or hidden inside some long script, because they always limit the real effect with their sandbox.

What do you do today?

No response

Product area

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions