I can help install your CodexFlow package, explain pricing, or answer security and license questions.
Docs
Install, verify, and work with durable repo context.
Use these docs to activate CodexFlow, install the signed payload, review the diff, and start Codex with the same repo operating layer every session.
Start here
Purchased CodexFlow? Install with Codex, then verify locally.
The customer package includes INSTALL_WITH_CODEX.md. Paste it into Codex inside your target repo, then review every generated file in Git.
Docs hub
Start with the install path.
These pages cover the package, the signed payload, and the repo files CodexFlow writes.
Getting started
The guided install walkthrough for new CodexFlow customers.
start hereInstall guide
Manual package install, signed activation, payload install, emit, doctor, and Git review.
installWhat gets installed
AGENTS.md, 2,000+ skills, 11 agents, memory, commands, checks, and delivery materials.
filesSecurity
Local-first CLI behavior, signed artifacts, entitlement checks, and paid-package boundaries.
trustReference pages for decisions and support.
Use these when you are comparing licenses, checking update access, or diagnosing a failed install.
Troubleshooting
Activation, payload, entitlement, and emitted-content recovery paths.
repairLicense plans
Personal and Commercial Solo rights, limits, watermarks, and upgrade paths.
rightsUpdates
Buy-once ownership, 12 months of V2 update access, and signed upgrade delivery.
updatesPricing
Personal, Commercial Solo, and Team Waitlist options.
pricingInstall checklist
- Download the secure customer package from your access page.
- Open Codex in the target repository and paste INSTALL_WITH_CODEX.md.
- Activate the signed activation file.
- Install the signed payload archive from its manifest.
- Run codexflow emit and codexflow doctor.
- Review git diff before committing anything.
Current V2 footprint
Support
Need help with activation or payload install?
Keep private files out of public channels. Send support the order ID and CLI diagnostics, not secrets.
Start from the docs, finish in Git.
Install the signed payload, emit the operating layer, and review every generated file before you commit.