Connect Codex
Overview
AutoPilot uses Codex as its reviewer and planner. Codex reviews the work produced by the developer agent, helps plan tasks, and checks results before they are accepted. Codex stays local on your machine, so your code and review activity never leave your environment.
AutoPilot connects to Codex through your existing local Codex setup. You remain in control of your credentials and your machine.
Setup
Connecting Codex takes a few steps. You only need to do this once per machine.
- Install and sign in to Codex by following its official setup instructions for your operating system.
- You may need to log in to Codex separately as part of that setup. Follow the official instructions to authenticate.
- Return to AutoPilot and run the connection check.
- AutoPilot detects whether Codex is available and reports the result.
- Once connected, Codex reviews tasks, diffs, plans, and results as part of the AutoPilot workflow.
Troubleshooting
If the connection check does not pass, the most common causes are listed below.
Codex not found
AutoPilot could not locate Codex on your machine. Confirm that Codex is installed by following its official setup instructions, then return to AutoPilot and run the connection check again.
Codex not authenticated
Codex is installed but no active session was found. Sign in to Codex separately as described in its official instructions, then run the connection check again.
Review not starting
If Codex is connected but a review does not begin, confirm that the connection check passes and that Codex is still authenticated. Re-run the connection check, then start the task again so Codex can pick up the work.
Connection status not green
A connection status that is not green means AutoPilot cannot currently reach Codex. Verify that Codex is installed and signed in, then run the connection check to refresh the status.
If a problem persists after trying these steps, see Troubleshooting for more detail.
Need help? Contact support.
