OpenAI Codex integration

Keep coding while Codex handles an independent change.

Codex handles implementation tasks. Flame gives those tasks a place to run alongside your projects, branches, terminals, tests, reviews, and other agents.

The developer problem

The coding agent should not become another isolated workspace.

When an agent works separately from your editor, Git state, and test surfaces, it is easy to lose track of where a change belongs or whether it is ready to land.

Flame lets you assign Codex a repository task while keeping the rest of development in view. Its task has a project, an optional isolated worktree, a visible execution history, and a review path back into the same workspace.

Try it on a real task

What Codex enables in Flame

Connect

Enable Codex in AI settings and use your existing supported Codex or ChatGPT login. Flame installs the native runtime on demand.

Example task

Assign Codex a pagination regression in the API while you continue a frontend feature in your original checkout.

Inspect the result

Inspect the isolated branch, run the API tests, and choose local merge, push, or push and prepare a PR form.

What to expect

Provider access is separate from Flame. The current Codex integration supports ordinary agent sessions, without Flame-managed native worker teams.

A connected workflow

A Codex task that stays connected to the codebase

  1. 01

    Scope the repository task

    Create a Codex task from a project or connected task-tracker item and choose the branch, isolation, permissions, and landing policy.

  2. 02

    Run without blocking the editor

    Codex works in the background while the task board reports status, duration, token use, tool calls, and terminal output.

  3. 03

    Coordinate agent choices

    Use Codex for one job and Claude Code or Gemini via Antigravity for another; Flame does not require the whole workspace to standardize on one provider.

  4. 04

    Review the generated code

    Use the Git diff and merge preview before choosing an explicit landing action for the completed branch.

How it works in Flame

Codex in a workspace built for supervision

01

Codex is the agent. Flame is the workspace.

The distinction matters: Flame manages projects, worktrees, terminals, test surfaces, Git review, and the task queue; Codex performs the coding task you assign.

02

Isolate changes before they overlap

Assign an optional dedicated Git worktree to a Codex task. Your current checkout remains available for manual work or another agent task.

03

Work across more than one repository

For a response-format change, search the API and its consumers together, attach the affected files, and grant the conversation access to the repositories it needs.

04

Keep the final decision with the developer

Inspect the diff, run tests, and decide whether to merge locally, push the branch, or prepare a PR/MR form for submission. Automatic landing is opt-in.

FAQ

Codex integration questions

Use Codex with Flame.

Download Flame to keep implementation, verification, review, and the final Git decision in one workspace.

Free to use on macOS, Windows, and Linux.