Make the list of auto-approved commands configurable via `execpolicy`

[bolinfest]

This is a highly requested feature. https://github.com/openai/codex/blob/main/codex-rs/execpolicy/README.md explains the bones of what we have today, though this logic needs to be polished and wrapped up in a way that is easy for end-users to take advantage of.

[polyrand]

I believe this is a much-needed feature. While this gets polished and made available to users, maybe allowing to pass custom Starlark .policy files when running codex could be a good starting point?

[JonathanAquino-NextRoll]

Cursor CLI has a nice UI for choosing which tools to allow:

[fcakyon]

How can one create an allowed tools list as in claude code?

[hmottestad]

Thought I would use Codex CLI to migrate some tests to use Testcontainers. Really want to be able to let the sandbox interact with docker!

[ignatremizov]

Would love to have this implemented!

[ignatremizov]

The recent PR #7033 by @zhao-oai adds a version of prefix allowance during TUI execution, it would be awesome to configure a pre-approved list of prefix commands before execution. Anyone is working on this?

[ignatremizov]

Recently noticed that:

  Would you like to run the following command?

  Reason: Check if DB accepts connections

  $ PGPASSWORD=pass psql -h 127.0.0.1 -p 5432 -U my_user -d local_db -c "select 1;"

› 1. Yes, proceed (y)
  2. Yes, and don't ask again for commands that start with `PGPASSWORD=pass psql -h 127.0.0.1 -p 5432 -U my_user -d local_db -c "select 1;"` (p)
  3. No, and tell Codex what to do differently (esc)

it's getting the wrong prefix selection. I would like to set everything before the first quotes to be auto-approved. @zhao-oai was this intentional? (p) is also harder to reach than (a) (it was "always approve this command (a)" before)