General
What is CodexFlow?
CodexFlow is a repo-native workflow OS for developers using OpenAI Codex. It installs structured workflow files into your repository so Codex can work with persistent context, AGENTS.md guidance, skills, commands, QA guardrails, runbooks, and handoff workflows.
Is CodexFlow affiliated with OpenAI?
No. CodexFlow is independent and is not affiliated with, endorsed by, or sponsored by OpenAI.
Is CodexFlow a coding agent?
No. CodexFlow does not replace Codex. It gives your repository the workflow structure around Codex: memory, rules, skills, commands, guardrails, runbooks, and handoffs.
Why call it a workflow OS?
Because CodexFlow gives your repo an operating structure for AI-assisted development. It is not a computer operating system. It is a workflow operating system for Codex-powered repositories.
Product
What does CodexFlow install?
CodexFlow can install AGENTS.md guidance, repo memory files, Codex skills, slash-command workflows, QA guardrails, shipping runbooks, and handoff templates.
Paid users also receive access to the signed paid Individual payload.
Is CodexFlow just a prompt pack?
No. Prompt packs are usually static text copied into a chat. CodexFlow installs a versioned workflow layer into your repository so the workflow can be reviewed, reused, updated, and preserved in Git.
Where do CodexFlow files live?
CodexFlow files live in your repository. Generated output is designed to be human-readable and Git-reviewable.
Can I edit the generated files?
Yes. CodexFlow-generated workflow files are plain text. You should review and adapt them to your repository. Use Git to track changes.
Does CodexFlow guarantee correct code?
No. CodexFlow improves structure, context, and reviewability. You are still responsible for reviewing, testing, and approving code changes.
Demo and installation
Can I see CodexFlow before buying?
Yes. The public demo shows example generated repo structure, sample AGENTS.md guidance, a sample workflow command, and a before/after Codex task transcript.
The demo is read-only sample material. It is not an installer, activation file, payload archive, license grant, or unpaid product tier.
How do I install CodexFlow after purchase?
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.
The core paid setup is:
bash
codexflow license activate --activation-file ./codexflow.activation.json
codexflow payload install \
--manifest ./individual-core-0.1.0.manifest.json \
--archive ./individual-core-0.1.0.tar.gz
codexflow emit
codexflow doctorShould I install CodexFlow on a clean branch?
Yes. Install CodexFlow on a clean branch or with a clean working tree whenever possible. Review the generated files before committing.
Can I uninstall CodexFlow?
Yes. Use the uninstall flow:
bash
codexflow uninstall --yesCodexFlow preserves repo memory by default so you do not accidentally delete useful project context.
Can I remove the paid payload?
Yes. Use:
bash
codexflow payload removeThen review the Git diff.
Plans
What do paid customers receive?
Paid Personal and Standard customers receive access to the signed paid Individual payload, signed activation file, signed payload manifest, verified payload archive, hashes, and install documentation.
Do Personal and Standard include different payload files?
No. Personal and Standard receive the same paid Individual payload. The difference is the license right attached to the activation.
What is Personal?
Personal is for one named individual using CodexFlow for non-commercial personal work. It does not allow commercial use.
What is Standard / Commercial Solo?
Standard / Commercial Solo is for one named individual using CodexFlow for solo commercial work, including own products, SaaS projects, freelance work, consulting work, and client work.
Can I use Personal for my business?
No. Use Standard / Commercial Solo for business, client, freelance, SaaS, or other commercial work.
Can a team use one Standard license?
No. Standard is a single-individual license. Team or multi-seat use requires a separate arrangement and is not currently available through self-serve checkout.
Do you offer a team plan?
Team / Business licensing is waitlist / custom only. Contact support if you need multi-seat licensing, shared workflow standards, centralized billing, or organization-level support.
Activation and payloads
What is an activation file?
An activation file is a signed license file that tells CodexFlow which tier you have and which entitlements are available.
What is the paid Individual payload?
The paid Individual payload is the signed package of premium CodexFlow workflow assets available to Personal and Standard customers.
Why does payload installation require activation?
Activation verifies that the user has the right entitlement before premium assets are installed or emitted.
What happens if my activation file is modified?
Modified activation files are rejected because the signature no longer verifies.
What happens if my payload archive is modified?
Modified payload archives are rejected because the archive no longer matches the signed manifest and expected hashes.
Privacy and security
Does the CodexFlow CLI transmit usage telemetry?
The CodexFlow CLI does not transmit usage telemetry in this release.
Does the website store order information?
Yes. The commerce website records operational data needed for orders, fulfillment, fraud prevention, access control, support, and dispute evidence.
Are paid payloads public?
No. Paid payloads are not intended to be placed in public/static directories. Paid access is handled through secure delivery and signed payload verification.
Are raw license keys exposed in generated files?
No. Premium output may include hashed or truncated license metadata, but it should not include raw license keys.
Can I commit CodexFlow files to Git?
You can commit the generated workflow files you want to keep. Do not publish paid proprietary payload archives, activation files, or restricted paid assets in public repositories.
Payments and refunds
Is CodexFlow a subscription?
No. The current public paid plans are one-time launch-price purchases.
What payment method is used?
Paid checkout is processed through the payment provider shown at checkout.
When do I receive paid access?
Paid access is issued after payment verification and fulfillment. The success page alone does not fulfill paid orders.
Can I get a refund?
Refund handling depends on order status, access status, and applicable rules. Refunds are generally easier before paid activation or payload access has been delivered. After paid digital files are issued or downloaded, refunds may be limited unless the product is materially defective, inaccessible, or not as described.
See Refund Policy.
Usage
Who is CodexFlow for?
CodexFlow is for solo developers, technical founders, freelancers, consultants, and operators who use Codex in real repositories and want more structure, memory, QA, and handoff discipline.
Can I use CodexFlow with any tech stack?
CodexFlow is designed to analyze repository shape and emit relevant workflow assets. Some skills and workflows are more relevant to specific stacks such as Next.js, React, Vercel, Supabase, WordPress, WooCommerce, and Node.js projects.
Does CodexFlow work without Codex?
CodexFlow files are plain text and can help any human or AI assistant understand the workflow. The product is positioned specifically for Codex-powered repositories.
Can I use CodexFlow on multiple repositories?
A licensed individual may use CodexFlow within the scope of their license. Personal use must remain non-commercial. Standard use may cover solo commercial work by that named individual. Team sharing is not included.
Support
How do I contact support?
Use the support page:
What should I include in a support request?
Include:
- Your order email
- License tier
- CLI version
- Operating system
- Command that failed
- Error output
- Whether the issue affects activation, payload install, emitted files, or checkout access
Do not send raw private keys, production secrets, passwords, or full customer data.