Distinguish a requested command from the filesystem, network, and external access actually allowed.
Coding & development · Documented · Documentation checked 2026-10-04
Codex CLI, IDE extension, and desktop coding work; cloud environments need separate setup.
MCP / plugin support varies by client. New permission profiles are beta; approval policy and network access are separate controls.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Distinguish a requested command from the filesystem, network, and external access actually allowed.
Filesystem permissions, network policy, and approval rules constrain different operations. MCP and plugins can add external tools outside the repository. A permitted shell command does not imply permission to call every remote API. New permission profiles are beta and differ from older sandbox configuration.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Inspect the active client’s permission and approval settings; in CLI, use the documented /permissions or status controls.
- Allow only required repository paths and network destinations.
- For an extension, inspect its tool list and connected identity before enabling it.
- Test a harmless read, then review any proposed write or command before execution.
Worked example
A coding task might need local test execution and read-only issue context, but no production database access. Build a permission matrix first. Granting a connector broad administrative rights would be unnecessary for that task.
Inspect this repository and propose a fix plan. Read only the approved workspace and issue context. Before any command or external action, show what it changes and why it is needed. Stop if required access is missing. Do not access production data, send messages, or publish changes.
Inspect and verify the result
Compare requested operations with actual tool calls and effective settings. Verify external account scope in the provider service. A denied action is useful evidence of a boundary; do not bypass it to finish a tutorial.
Limits and troubleshooting
Approval behavior and permission profiles are separate. Client and plugin support varies; IDE does not inherit every desktop plugin. Web search can have a different access mechanism from local shell networking. Review the exact current documentation for the configured environment.
Data, permissions, and actions
Shell commands can execute code and change files. MCP calls can read or modify external records. Prompt instructions describe intent, while runtime and service controls enforce authority. Keep credentials in approved secret handling rather than ordinary prompts.
Related reading
Cloud environments and repository access
Prepare a repeatable remote environment with dependencies, scoped secrets, and a known test command.
A scoped repository bug fix
Reproduce a sample defect and hand off a checked diff.
A prepared cloud task and review handoff
Run a bounded repository task in a reproducible cloud environment.
Permissions and meaningful approvals
Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Permissions and approval policies · OpenAI
Plugins and supported surfaces · OpenAI
Codex CLI · OpenAI