Origin Story

Origin Story

Cool Workflow started from a simple observation:

Claude has workflows.
Codex has tools.
Cool Workflow gives Codex a workflow kernel.

Claude-style workflow discipline made it clear that agent work should not be only a single conversational turn. Useful work needs phases, saved context, organized outputs, continuation, and verification. Codex-style coding agents have strong execution tools, but they need an open workflow layer that can define, decompose, record, verify, resume, and deliver complex engineering tasks.

Product Position

Cool Workflow is not another AI app. It is a workflow kernel underneath AI coding agents.

It serves work that is:

• long-running
• multi-phase
• evidence-backed
• multi-agent
• verifier-gated
• checkpointable and resumable
• reportable

What CW Copies From Workflow Discipline

CW copies the lower-level discipline, not a closed product experience:

• structured workflow decomposition
• resumable state
• tool-aware execution
• memory of prior phases
• verification gates
• clear handoff between planning, acting, observing, and reporting

CW avoids:

• single-vendor packaging
• host-specific assumptions
• hiding runtime logic inside a skill or adapter
• treating one prompt as the whole unit of work

Mapping

Workflow value	CW implementation
workflow / plan	workflow app + phases
continuation	.cw/runs/<run-id>/state.json
subtask delegation	dispatch manifests
artifact discipline	task/result/report files
review / verification	verifier gates
safe state merge	verifier-gated commit
background continuity	schedules and routines
host integration	CLI, MCP, and skills

Narrative

Cool Workflow brings Claude-like workflow discipline to Codex, but implements it as an open, CLI/MCP-backed, Unix-inspired workflow kernel.