The workflow OS for OpenAI Codex.

CodexFlow turns every Codex-powered repo into a structured development system — AGENTS.md, persistent memory, skills, slash commands, QA guardrails, runbooks, and handoff workflows installed through a signed paid setup.

Get CodexFlow View demo

Git-reviewable
Signed paid payload
No telemetry
Human-readable files

Signed paid payloadRepo-native, no SaaS lock-in

Terminal

$ codexflow license activate --activation-file ./codexflow.activation.json✓ activation verified: Standard / Commercial Solo$ codexflow payload install --manifest ./individual-core.manifest.json --archive ./individual-core.tar.gz✓ manifest signature verified✓ archive checksum verified$ codexflow emitagents: compose(AGENTS.md + local workflow rules)skills: install(nextjs-web-pro, vercel-deploy, seo-audit)commands: link(plan-feature, review-diff, ship)✓ paid CodexFlow workflow is active✓ run codexflow doctor before your next session_

Works alongside

OpenAI CodexClaude CodeCursorAiderGemini CLIContinue.devOpenAI CodexClaude CodeCursorAiderGemini CLIContinue.dev

All product names and logos shown are trademarks of their respective owners. CodexFlow is independent and is not affiliated with, endorsed by, or sponsored by any of them.

What gets installed

Your repo gets a complete paid workflow layer.

CodexFlow scans your project shape and writes a small, human-readable system into your repo. Codex reads it on every session. You keep ownership of every file.

AGENTS.md gives Codex repo rules.Project conventions, sensitive files, test paths, definition of done.
Skills, commands, and runbooks live under .codex/.Reusable specialist workflows. Versioned in Git.
Memory and handoffs stay in Git.Decisions, known issues, prompt logs — durable across sessions.

repository

▸your-repo/
●AGENTS.md
●PROJECT_CONTEXT.md
▸.codex/
▸memory/
└DECISIONS.md
└HANDOFF.md
└KNOWN_ISSUES.md
▸skills/ · 25 specialist workflows
▸commands/ · plan · review · ship
▸runbooks/ · release · incident · ci
▸guardrails/ · dry-run · backups · risky-files

Slash commands

One-off prompts become reusable workflows.

Replace improvised instructions with repo-scoped commands. Every command runs inside the same memory, skills, and guardrails — every time.

>/plan-feature add SEO checks⌘ K

Workflow

From blank Codex session to structured delivery.

The same four steps drive every change — onboarding a new repo, shipping a feature, or recovering an incident.

Step 01

Scan the repo

CodexFlow reads project shape, package scripts, framework hints, routes, workflow files, and existing conventions.

Step 02

Install the workflow OS

Generate AGENTS.md, repo memory files, Codex skills, slash commands, runbooks, QA checklists, and handoff templates.

Step 03

Work through structured commands

Plan, implement, debug, review, test, release prep, and handoff — every task starts from known repo context.

Step 04

Keep the repo warm

Update memory, decisions, prompt logs, and handoffs. The next Codex session starts with context instead of confusion.

Prompt packs vs CodexFlow

Prompt packs give instructions. CodexFlow gives your repo an operating system.

Generic prompt pack

Chat in, context out.

Instructions live in a transient conversation. Every new task starts cold.

UYou · 09:14How do I add SEO checks before shipping?

AIAssistant · 09:14Here are eight tips. (Lives only in this thread.)

UYou · next dayWait, how were we doing SEO again?

CodexFlow

Workflow files committed to the repo.

The same skill, command, and runbook run every time — versioned in Git.

📁 .codex/skills/ nextjs-seo-audit.md📁 .codex/commands/ audit-seo.md📁 .codex/runbooks/ release-prep.md

$ git statusOn branch main added: AGENTS.md added: .codex/skills/nextjs-seo-audit.md added: .codex/commands/audit-seo.md

Built for

Developers who ship with Codex.

Not for demos. Not for toy prompts. For real repo work.

Solo founders

Keep product context, decisions, and release discipline in the repo — not the chat.

Indie hackers

Ship faster with Codex without the codebase becoming harder to understand.

Freelancers

Repeatable AI-assisted workflows per client. Each repo keeps its own rules.

Technical operators

Audits, incident fixes, deploy debugging, release prep — with structure, not improvisation.

Power users

Give Codex more than a good prompt. Give it a workflow system it keeps using.

Pricing

Paid licenses for serious Codex work.

Choose the license that matches how you use CodexFlow. Public demo materials show the workflow before you buy.

Personal€49one-time

For named individual use

Signed activation and the individual paid payload for personal, non-commercial projects.

Signed activation
Skills, commands, runbooks
QA guardrails & handoffs

Get Personal

Standard · Commercial Solo€149one-time

For solo commercial use

Everything in Personal · plus

Commercial solo rights
Signed manifest & verified archive
Secure customer access page

Get Standard

Team / BusinessCustomwaitlist

For teams and organizations

Multi-seat licensing, internal workflow governance, and organization-level support.

Shared workflow standards
Centralized billing
Custom launch support

Join waitlist

FAQ

Common questions.

Is CodexFlow affiliated with OpenAI?

No. CodexFlow is independent and is not affiliated with, endorsed by, or sponsored by OpenAI.

Is CodexFlow just a prompt pack?

No. Prompt packs are static instructions you paste into a chat. CodexFlow installs a versioned workflow layer directly into your repository, so Codex can work from durable project context and repeatable procedures.

Does CodexFlow send my code to external servers?

The CodexFlow CLI does not transmit usage telemetry in this release. CodexFlow files are installed into your repo and remain human-readable and Git-reviewable.

Read full FAQ

Install once. Improve every Codex session.

Choose a paid license, install the signed payload, and give every Codex session a structured repo workflow.

CodexFlow is independent and is not affiliated with, endorsed by, or sponsored by OpenAI.

Get CodexFlow View demo