Connect Codex

3 minute read · Chats & Local Agents

Connect Codex once, then choose it in a project conversation. Your Vortex sign-in and provider sign-in are separate accounts.

• Connect the account
• What to expect from Codex
• Make a small first run
• Interpret account usage
• Resolve common connection problems

Connect the account#

1. Open Settings → Agents & chat and select Codex.
2. 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.
3. Choose Sign in. Complete the supported browser flow and any displayed provider code, then return to Vortex to verify the account status.
4. Start a new chat, choose Codex and an available model, then ask it to explain the first step of your app idea.

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.