← All guides

Codex can chat but cannot run commands, use the network or write files

Check the current chat’s permissions, then handle file, network or terminal errors.

Updated

Start here

Open the current permission menu and check the selected mode. Ask Codex for the failed command and target before choosing the next step.

On this page

1. Open permissions

  1. On desktop or IDE, use the control below the input box. In CLI chat, enter /permissions.
  2. Usually start with Ask for approval. Review the command and target before approving a pending request; ask the administrator if options are unavailable.

2. Get the exact error

  1. Send the text below to the current chat.
  2. Use the returned path, domain or startup error to choose the next step.
List the failed command, complete error and target file or domain.
State the working directory and any pending approval, then suggest the next action.

3. Fix a file-writing problem

  1. Check whether the file is in the active project; switch to the correct project if needed.
  2. For read-only or occupied files, check attributes and finish your own editing or export operation. If writing still fails, request a patch for review.

4. Check network or terminal access

  1. For a network failure, confirm the domain and any pending approval. Compare the same credential-free, read-only check in a regular terminal.
  2. If commands cannot start, compare Get-Location on Windows or pwd on macOS/Linux in the regular terminal and Codex.

5. Contact support

  1. Provide the client version, permission mode, error screenshot and regular-terminal comparison.
  2. For organization or system restrictions, support can help identify what the administrator needs to check.

Contact support →

Useful links