Questions, answered.

CodexFlow is the operating system for Codex: a signed, repository-installed workflow stack with 2,000+ specialist skills, 11 agents, persistent project memory, 12 safe commands, 9 automated checks, AGENTS.md, guardrails, and handoffs.

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

No. CodexFlow does not replace Codex. It gives your repository the operating structure around Codex: project memory, rules, skills, agents, commands, checks, guardrails, and handoffs.

CodexFlow files are plain text and can help humans or AGENTS.md-compatible workflows understand the project. The product is positioned specifically for developers using Codex.

CodexFlow V2 can install AGENTS.md guidance, persistent project memory, 2,000+ specialist skills, 11 agents, 12 safe commands, 9 automated checks, QA guardrails, and handoff templates.

No. Prompt packs are static text copied into a chat. CodexFlow installs versioned workflow files into your repository so the workflow can be reviewed, reused, updated, and preserved in Git.

Generated files live in your repository under paths such as AGENTS.md, .agents/skills, .codexflow/agents, .codexflow/memory, .codexflow/commands, and .codexflow/checks.

Yes. CodexFlow-generated workflow files are plain text. You should review and adapt them to your repository. Use Git to track changes.

No. CodexFlow improves structure, context, and reviewability. You are still responsible for reviewing, testing, and approving code changes.

CodexFlow emits workflow files that you review in Git. Start from a clean branch, inspect the diff, and commit only the files you want to keep.

Yes. Install CodexFlow on a clean branch or with a clean working tree whenever possible. Review the generated files before committing.

Yes. Use:

codexflow uninstall --yes

CodexFlow preserves project memory by default so you do not accidentally delete useful context.

Yes. Use:

codexflow payload remove codexflow-v2-individual-core

Then review the Git diff.

After payment verification, you receive secure access to the signed activation file, signed V2 payload manifest, verified archive, and install documentation.

Yes. You can preview what gets installed on the public installed-files page. The preview is read-only sample material. It is not an installer, activation file, payload archive, license grant, or unpaid product tier.

Paid customers install CodexFlow from their repository root using the activation file, signed payload manifest, and verified archive provided through the secure order access page.

codexflow license activate --activation-file ./codexflow.activation.json
codexflow payload install \
  --manifest ./codexflow-v2-individual-core-2.0.0.manifest.json \
  --archive ./codexflow-v2-individual-core-2.0.0.tar.gz
codexflow emit
codexflow doctor

Paid Personal and Commercial Solo customers receive access to the same CodexFlow V2 Individual payload, signed activation file, signed payload manifest, verified payload archive, hashes, install documentation, and 12 months of V2 payload/update access.

No. Personal and Commercial Solo receive the same CodexFlow V2 Individual payload. The difference is the license right attached to the activation.

No. The current public paid plans are one-time purchases. The V2 version you buy remains yours under that license, and 12 months of V2 updates are included.

Personal is for one named individual using CodexFlow for non-commercial personal work. It does not allow commercial use.

Commercial Solo is for one named individual using CodexFlow for paid solo work, including own products, SaaS projects, freelance work, consulting work, and client work.

No. Use Commercial Solo for business, client, freelance, SaaS, or other commercial work.

No. Commercial Solo is a single-individual license. Team or multi-seat use requires a separate arrangement and is not currently available through self-serve checkout.

Team licensing is waitlist / custom only. Contact support if you need multi-seat licensing, shared workflow standards, centralized billing, or organization-level support.

The CodexFlow CLI does not transmit usage telemetry in this release.

Yes. The commerce website records operational data needed for orders, fulfillment, fraud prevention, access control, support, and dispute evidence.

No. Paid payloads are not intended to be placed in public/static directories. Paid access is handled through secure delivery and signed payload verification.

No. Premium output may include hashed or truncated license metadata, but it should not include raw license keys.

You can commit the generated workflow files you want to keep. Do not publish activation files, payload archives, or restricted paid assets in public repositories.

Paid checkout is processed through the payment provider shown at checkout.

Paid access is issued after payment verification and fulfillment. The success page alone does not fulfill paid orders.

Refund handling depends on order status, access status, and applicable rules. Refunds are generally easier before activation or payload access has been delivered. After digital files are issued or downloaded, refunds may be limited unless the product is materially defective, inaccessible, or not as described.

See Refund Policy.

Use the support page:

Contact support

Include your order email, license tier, CLI version, operating system, command that failed, error output, and whether the issue affects activation, payload install, emitted files, memory, checks, or checkout access.

Do not send raw private keys, production secrets, passwords, or full customer data.