CodexFlowGet CodexFlow

Docs

Documentation

CodexFlow documentation hub for installation, paid activation, repo memory, AGENTS.md, skills, commands, QA guardrails, runbooks, licensing, and troubleshooting.

Get CodexFlowView demo

Purchased CodexFlow? Start here.

Activate your signed license, install the paid payload, emit the workflow files, and verify the setup before your first Codex session.

bash
codexflow license activate --activation-file ./codexflow.activation.json
codexflow payload install \
  --manifest ./individual-core-<version>.manifest.json \
  --archive ./individual-core-<version>.tar.gz
codexflow emit
codexflow doctor
Read the install guide

Setup in three steps

  1. Activate — verify your signed Personal or Standard license locally.
  2. Install the payload — unpack the signed archive after manifest and checksum verification.
  3. Emit and verify — generate repo workflow files, then run codexflow doctor.

Start

Install

Activate your paid license, install the signed payload, and verify the repo workflow.

What gets installed

AGENTS.md, repo memory, skills, commands, runbooks, guardrails.

Pricing

Personal €49, Standard / Commercial Solo €149, and Team waitlist.

Reference

License

Personal vs Standard rights. Signed activation. Commercial use.

Security

Signed payloads, verified archives, secure customer access.

Troubleshooting

Reset activation, fix payload errors, repair stuck installs.

Learn how to install, activate, and use CodexFlow.

CodexFlow is a repo-native workflow OS for developers using OpenAI Codex. These docs explain how the product works, what gets installed, how paid activation works, and how to use CodexFlow safely in real repositories.

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

Start here

Install / Getting Started

Activate a paid license, install the paid Individual payload, emit the repo workflow layer, and verify the setup.

What Gets Installed

Understand the workflow files CodexFlow adds to your repo: AGENTS.md, repo memory, skills, commands, QA guardrails, runbooks, handoff templates, and paid payload files.

Pricing

Compare Personal, Standard / Commercial Solo, and Team waitlist licensing. See what each tier includes and which license rights apply.

License Summary

Understand Personal vs Standard, commercial-use boundaries, single-user rules, redistribution restrictions, and paid payload rights.

Core concepts

Repo memory

Repo memory keeps durable project context in the repository. It helps Codex and humans preserve decisions, known issues, prompt logs, and handoffs across sessions.

Best used for:

  • Project context
  • Technical decisions
  • Known risks
  • Work logs
  • Follow-up tasks
  • Session handoffs

AGENTS.md

AGENTS.md gives Codex project-level operating instructions. It should explain how the repo works, what conventions matter, how to edit safely, and how to finish work properly.

Best used for:

  • Repo rules
  • Branch discipline
  • Sensitive files
  • Testing expectations
  • Review expectations
  • Definition of done

Skills

Skills are specialist workflows that help Codex handle repeatable tasks with better structure.

Best used for:

  • Performance work
  • SEO work
  • Security review
  • Supabase projects
  • Vercel deployment debugging
  • React refactors
  • Test planning
  • Release preparation

Commands

Commands turn repeated development rituals into reusable prompts and procedures.

Best used for:

  • Planning a task
  • Implementing a feature
  • Reviewing changes
  • Preparing a release
  • Creating a handoff
  • Running a focused audit

QA guardrails

QA guardrails help make AI-assisted changes more reviewable and less chaotic.

Best used for:

  • Dry-runs
  • Backups
  • Risky-file review
  • Test plans
  • Validation checklists
  • Safe write boundaries

Runbooks

Runbooks provide known-good procedures for common development and operational scenarios.

Best used for:

  • CI repair
  • Incident debugging
  • Deployment troubleshooting
  • Release checks
  • Audit workflows
  • Production-readiness review

Paid Personal and Standard customers receive a signed activation file and signed paid Individual payload access.

The paid setup flow is:

  1. Purchase Personal or Standard.
  2. Receive secure access to activation and payload materials after verified fulfillment.
  3. Activate the signed license file.
  4. Install the paid payload from the signed manifest and verified archive.
  5. Emit the paid workflow layer.
  6. Review the Git diff.

Personal and Standard receive the same paid Individual payload. The license rights are different.

  • Personal: one individual, non-commercial use.
  • Standard / Commercial Solo: one individual, commercial solo use allowed.

Security and privacy basics

CodexFlow is local-first workflow tooling.

Core principles:

  • Workflow files live in your repository.
  • Generated files are human-readable.
  • Git is the review boundary.
  • Paid payloads use signed manifests and verified archives.
  • Activation files are signed.
  • Premium output is watermarked without exposing raw secrets.
  • The CLI does not transmit usage telemetry in this release.
  • The website records operational data needed for orders, fulfillment, access, support, fraud prevention, and dispute evidence.

Practical workflow

A strong CodexFlow workflow looks like this:

  1. Start on a clean branch.
  2. Ask Codex to read AGENTS.md and relevant repo memory.
  3. Pick the command, skill, or runbook that matches the task.
  4. Ask for a plan before edits.
  5. Review risky areas before write operations.
  6. Run tests and checks.
  7. Update handoff notes.
  8. Commit a clean diff.

CodexFlow improves the operating structure around Codex. It does not remove the need to review and test code.

Troubleshooting shortcuts

I do not see paid content

Run:

bash
codexflow license status

A valid paid activation and installed paid payload are required before paid workflow files can be emitted.

My activation file is rejected

Download it again from your secure access flow or contact support. Modified, expired, or incorrectly signed activation files are rejected.

I want to remove paid payload files

Run:

bash
codexflow payload remove

Then review the Git diff.

I want to uninstall CodexFlow

Run:

bash
codexflow uninstall --yes

CodexFlow preserves repo memory by default to reduce the risk of accidental context loss.

Reference pages

If you are new to CodexFlow, read these in order:

  1. What Gets Installed
  2. Install / Getting Started
  3. License Summary
  4. CodexFlow vs Prompt Packs

You've seen the model. Add the paid CodexFlow workflow to your repo.

Get CodexFlowView demo
Supportsupport@codexflow.ioLicensePersonal vs StandardTroubleshootingActivation & payload

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 CodexFlowView demo