Replies: 1 comment 1 reply
-
|
Read-only mode is designed for cases where you don't want the agent to make modifications to your code. It's useful for operations like planning or "explain this code base to me". It's not intended to be used for code generation. For code generation, you should typically use the "Agent" sandboxing mode. The model learns to work differently based on the sandbox mode that you specify. You might be able to steer it somewhat based on prompting, but you will be working against its trained behaviors if you use read-only mode for code generation tasks. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I usually try to approve the code changes instead of letting AI agents run wild,
so my go-to approval mode is "Read Only."
Now, sometimes Codex doesn't complain and gets the work done, But more often than not, it will just stall and complain that because it is in the sandbox mode, it can't make any changes. And then I tell it that it can actually make changes, but it just needs my approval. I tell it to change the code and ask for my approval, and then it will start working.
Sometimes the bash commands, fail, but sometimes they succeed. And whenever the commands fail, it complains about the approval mode being read-only, that it needs to be able to write to the workspace when my experience tells me that if I gaslight Codex into thinking that it can actually make changes, it will actually make changes.
So I'm wondering what's going on here.
Codex is my favorite agentic coding AI, but whenever it complains about read-only mode, it really gets frustrating.
Beta Was this translation helpful? Give feedback.
All reactions