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.
OpenAI Codex integration
Run Codex as part of your complete development workflow
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.
A connected workflow
A Codex task that stays connected to the codebase
The tool remains the system you know. Flame provides the local workspace where the work moves forward.
- 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.
- 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.
- 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.
- 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
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.
Work across more than one repository
Flame’s projects root, groups, workspace search, and scoped multi-project AI context are designed for work that crosses services or repositories.
Keep the final decision with the developer
Inspect the diff, run tests, and decide whether to merge, squash, open a pull request, or push. 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.