Connect Codex
3 minute read · Chats & Local Agents
Connect a Codex account profile, then choose it for a conversation. Your Vortex sign-in and provider sign-in are separate accounts.
- Connect the account
- Keep provider profiles distinct
- What to expect from Codex
- Make a small first run
- Interpret account usage
- Resolve common connection problems
Connect the account
- Open Settings → Integrations and select Codex.
- Check installation status. If needed, choose Install and follow preparing, installing and verification progress. An error or cancelled installation needs attention before a run can start.
- Choose Sign in. Complete the supported browser flow and any displayed provider code, then return to Vortex to verify the account status.
- Start a new chat, check the intended account profile, then use the provider icon and model picker to choose Codex and an available model. Ask it to explain the first step of your app idea.
Keep provider profiles distinct
Provider accounts can hold multiple profiles for Codex. Name each profile so you can recognize the intended account, complete its connection flow and check its status before a run. A saved profile is separate from your Vortex sign-in and from a website login in the chat browser.
If a connection fails, inspect and reconnect the affected profile rather than replacing a working profile. Verify the account and model again before continuing. See provider accounts, models and usage; additional profiles do not include additional provider subscriptions or tokens.
What to expect from Codex
Codex uses your connected OpenAI account. Available models, reasoning settings and usage windows come from that account. Built-in image generation can use the connected Codex capability; it does not require the optional separately billed image API connection.
If the app reports unknown or signed out, open the connection controls again. An unknown state is not a confirmed sign-in. A provider account rejection needs an eligible account or another supported agent; Vortex does not change provider eligibility or include its tokens.
Continue with your first app, model and usage choices and permissions.
Make a small first run
After the connection screen confirms the account, open a new project chat and select Codex in the composer. Start with a read-only request: “Explain this project's entry point and how I can start it. Do not change files yet.” Check that the response comes from the chosen provider and that it refers to the selected project. Then request a small change and inspect the files and Preview result.
When a model exposes reasoning or service-tier controls, choose among the options Vortex shows for that model. Availability can differ by account. An installed executable, a connected account and a completed run are three separate checks; do not stop diagnosing after only the installation check succeeds.
Interpret account usage
Codex may expose five-hour and weekly account windows. These are your provider's allowance, separate from cloud storage and local project work. A context estimate describes the conversation size, not remaining paid account credit. Refresh the usage popover after a reset or connection change and read any accompanying error instead of treating a missing percentage as unlimited usage.
Resolve common connection problems
If sign-in opens a browser, finish the provider flow and return to Vortex for verification. Cancel a stalled attempt through its dialog before starting another. If the account is connected but a run is rejected, inspect the provider eligibility, model choice and returned error. If installation fails, keep its captured output and retry the failed step rather than replacing a detected system installation blindly.
Codex's built-in image generation, when available to the connected account, is separate from an explicitly selected image API connection. It must not silently switch to a separately billed API when a built-in operation is unavailable. See attachments and images for inspecting and exporting the result.