Switching to sub-agent and back re-asks permission for commands previously ran that aren't being run again

Resolved 💬 2 comments Opened Feb 21, 2026 by darlingm Closed Feb 24, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

0.104.0

What subscription do you have?

pro

Which model were you using?

gpt-5.3-codex

What platform is your computer?

Linux 6.18.8-arch2-1 x86_64 unknown

What terminal emulator and version are you using (if applicable)?

Suckless terminal 0.9.3, tmux 3.6a

What issue are you seeing?

I switched to a (sub) agent, back to the main agent, and was re-asked for permission for everything I had granted a long time ago, even though it never ran those commands again.

What steps can reproduce the bug?

  1. Cause Codex to ask for permission then spawn agents, and grant permission.
  2. Switch to a (sub) agent.
  3. Switch back to main agent.
  4. Observe being asked for the same permissions as in step 1, even though Codex never runs the commands after this second time it's asking permission.

I haven't verified if this always reproduces, but having run /feedback with thread ID 019c8199-e775-7120-85a0-1134ccf354a4 I'm hoping that's OK.

What is the expected behavior?

Once I give permission to run a command and it's run, Codex shouldn't later ask again, especially if it's not going to run those again.

Additional information

I ran '/feedback' and was given thread ID 019c8199-e775-7120-85a0-1134ccf354a4.

I know there's other "asking permission again" issues. I don't see any involving agent switching or being asked for commands it's not trying to run.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 6 months ago

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

  • ##11298
  • ##10735
  • ##12095
  • ##12108

Powered by Codex Action

darlingm contributor · 6 months ago

(It could be a duplicate. I can't tell if it's the same root cause as another, or if it's related to agent view switching.)