codex - 💡(How to fix) Fix [BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17653Fetched 2026-04-14 05:41:39
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Timeline (top)
labeled ×3commented ×2cross-referenced ×1renamed ×1
RAW_BUFFERClick to expand / collapse

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?

<img width="365" height="271" alt="Image" src="https://github.com/user-attachments/assets/089b2e07-714c-411b-b78a-7465896a8b40" />

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

extent analysis

TL;DR

Setting the "Full access" permission before making the initiating prompt may resolve the issue.

Guidance

  • The problem seems to occur when the "Full access" setting is changed after the prompt is made, suggesting a potential timing or initialization issue.
  • To verify, try setting "Full access" before creating the prompt and check if the issue persists.
  • Consider providing more details about the expected behavior of the "Full access" setting to better understand the root cause.
  • If the issue is related to the UI layout, providing feedback on the new layout might help the developers prioritize changes.

Example

No code snippet is provided as the issue does not seem to be code-related.

Notes

The issue might be specific to the latest version of the IDE extension or the Business seat subscription, and more information about the extension's configuration or the specific use case could help in identifying the root cause.

Recommendation

Apply workaround: Set "Full access" before making the initiating prompt, as this seems to be the safest and most straightforward way to avoid the issue until a more permanent fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix [BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt [2 comments, 2 participants]