Skip to content

[BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt #17653

Open

Description

@topemalheiro

What version of the IDE extension are you using?

latest

What subscription do you have?

Business seat

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

Image

After making the initiating prompt, setting to Full access doesn't work; the safe way is to set it before the prompt.

This starts being a nuisance since when we switch accounts, Full access setting doesn't stay. As well as it being on the right corner makes it harder to notice (I prefer it on the left like before, and I fully support the chat width being 100% of the side panel for the record, that's not in question).

What steps can reproduce the bug?

Make a prompt and set the Change permissions setting to Full access.

What is the expected behavior?

Full access works immediately.

Additional information

No response

Activity

  1. changed the title [-][BUG] Not accepting all permissions when setting Full access after doing the first prompt[/-] [+][BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt[/+] on Apr 13, 2026
  2. added
    bugSomething isn't working
    sandboxIssues related to permissions or sandboxing
    on Apr 13, 2026
  3. github-actions commented on Apr 13, 2026

    @github-actions
    Contributor
  4. topemalheiro commented on Apr 13, 2026

    @topemalheiro
    Author

    Potential duplicates detected. Please review them and close your issue if it is a duplicate.

    Powered by Codex Action

    The first issue is my complaint about Full access, which, for the most part, is fixed except for this problem.

    The second is about command permissions not staying over account switches, I reckon, and some other settings. It's asking for certain settings to be account-agnostic, and to be associated with the Codex instance, I presume.

  5. mtfelian commented on Apr 24, 2026

    @mtfelian

    Now many things like using playwright became completely unusable because of this with constant asking for permissions. Solution with

    approval_policy = "never"
    sandbox_mode = "danger-full-access"
    

    in config.toml works but that's not a good practice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingsandboxIssues related to permissions or sandboxing

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions