A useful AI process often outgrows one prompt: gather the right material, split independent work, call existing tools, check the result, and finish the job. Codex Agents Workflow makes that process visible and reusable inside Codex. Start from a Skill or a plain-language brief, edit the graph, and run it with your configured Providers.
Your current Main conversation keeps the decisions and final acceptance. Workers receive the materials their steps need. The local Host handles scheduling, handoffs, tools, and recorded progress.
Version 1.2.2 narrows worker receipt checks to declared products, preserving original tool diagnostics and artifact checks without freezing renderer state directories. The workbench checks for updates when opened and provides a GitHub Star link; update checks never block Runs.
For a task with three independent deliverables, the process can look like this:
flowchart LR
Goal[Goal + source material] --> Main[Current Main: choose scope]
Main --> A[Worker: deliverable A]
Main --> B[Worker: deliverable B]
Main --> C[Worker: deliverable C]
A --> Review[Current Main: review results]
B --> Review
C --> Review
Review --> Done[Accepted artifacts]
This is an illustrative graph. Real Workflows express dependencies, conditional routes, tools, and concurrency limits. Independent branches can run together; steps that need earlier results wait for them.
- Reuse a process that already works. Skill to Workflow converts instructions, references, and existing callable tools into an executable graph.
- Build from a brief. Describe the result and the steps you need; Build Workflow generates a graph for review and editing.
- Give each step a focused context. Declare its inputs, resources, predecessor results, and write scope.
- Keep coordination in the Host. It releases ready work, waits for events, and records attempts and outputs. Main makes the semantic decisions.
- Repair the part that failed. Inspect recorded progress and continue the affected work while keeping completed results available.
Requires Node.js 20+, Git, and a Codex host supporting plugins and MCP Extensions.
git clone https://github.com/TohmaN233/codex-agents-workflow.git
cd codex-agents-workflow
codex plugin marketplace add .
node plugins/codex-agents-workflow/scripts/install-local.mjsFor dependency setup, automated installation and verification, follow INSTALL.md.
In a Codex task, open the workbench:
Use $codex-agents-workflow:workflow-control-plane and open the workbench inside Codex.
- Choose Skill to Workflow for an existing Skill, or Build Workflow for a new process.
- Review the generated graph and its declared tools and dependencies. Automatic authoring publishes an enabled, launch-ready Workflow after review; the manual option keeps a reviewed Draft for your approval.
- Choose New task, enter your goal, and follow the Run's progress and outputs.
Native Codex Providers are enabled by default. Configure optional external Providers in Provider settings. Enabled Roles can also help Main with ordinary tasks; Workflow nodes bind directly to Providers. See the user guide for configuration and execution options.
Browse Workflow Package for optional installable packages, source Skill credits, usage notes, comparison results, and complete output examples. Download the selected *.workflow-package.json and choose Install Workflow in the workbench.
The engine includes Build Workflow and Skill to Workflow. The package collection is maintained separately. Have a generally useful process to share? Contributions to the collection are welcome.
- Documentation — setup, configuration, authoring, execution, and recovery.
- Architecture — how Main, workers, the Host, Skills, and the harness fit together.
- Workflow format — nodes, bindings, tools, and execution contracts.
- Project & author's post · Author · Repository
Contributing: verify the browser UI
Use Node.js 22+ in plugins/codex-agents-workflow/control-plane:
npm ci --ignore-scripts --no-audit --no-fund
npm run check:webMIT license · Security policy · Version 1.2
