Product updates and verified release notes.
This changelog records customer-facing CodexFlow releases and important product changes.
CodexFlow is independent and is not affiliated with, endorsed by, or sponsored by OpenAI.
0.1.0 — Release Candidate
Date: 2026-05-23
Status: Ready for controlled launch and paid manual fulfillment
CodexFlow 0.1.0 establishes the first sellable release of the product: a paid Individual payload, Personal and Standard activation behavior, public demo materials, and a tested customer journey for activation, payload installation, and failure handling.
Added
- Public demo materials for generated workflow examples
- Core CLI entry points
- Repo workflow layer
- AGENTS.md workflow foundation
- Repo memory structure
- Agent scaffolding
- Command scaffolding
- Skill scaffolding
- Paid Individual payload
- Signed activation files
- Signed payload manifest
- Verified payload archive
- Payload checksums
- License status flow
- Payload install flow
- Payload remove flow
- Uninstall flow
- Premium file watermark metadata
- Customer install documentation
- Manual fulfillment support for Personal and Standard purchases
Paid Individual payload
The paid Individual payload includes:
- 8 paid agents
- 10 paid commands
- 20 paid skills
- 38 paid workflow asset files
Personal and Standard customers receive the same paid Individual payload. The license activation controls the rights boundary.
- Personal: non-commercial use only
- Standard / Commercial Solo: commercial solo use allowed
Verified
The release candidate passed:
- Typecheck
- Test suite
- Build
- Package check
- Release build
- Release verification
- Release leak check
- Customer-journey end-to-end tests
- Activation and payload tests
- Utility command tests
- Security failure scenarios
The verified customer journey covers:
- Public demo and package-boundary behavior
- Personal activation behavior
- Standard activation behavior
- Paid payload installation
- Premium output generation
- Tampered activation rejection
- Expired activation rejection
- Tampered payload rejection
- Missing entitlement rejection
- Unknown signing key rejection
- Payload removal
- Uninstall behavior
Security and integrity
This release includes checks designed to prevent paid assets from leaking into the public package.
Verified behaviors include:
- Paid payload files are not included in the public npm package.
- Payload archives are checked against signed manifests and hashes.
- Tampered activation files are rejected.
- Tampered payload archives are rejected.
- Premium output avoids raw license keys.
- Premium output avoids raw customer emails.
- Premium output avoids private signing keys.
- Premium output avoids customer source-code excerpts in watermark metadata.
Package boundary
The public package is intentionally limited.
The verified public npm package contains:
- License and notice files
- CLI build files
- Demo/package metadata
- Public package files
- Public command and skill scaffolding required for paid setup
Paid payload assets are delivered separately through signed activation and payload access.
Known launch-stage limitations
The following items are not part of the current self-serve product experience:
- Team / Business tier
- Multi-seat licensing
- Organization-level permissions
- Hosted revocation list
- Auto-update notifications from the CLI
- Enterprise procurement flow
- Shared team policy management
These limitations do not affect Personal or Standard / Commercial Solo individual workflow installation.
Recommended upgrade path
Use:
- Public demo materials to inspect the workflow shape before buying
- Personal for one individual doing non-commercial work
- Standard / Commercial Solo for one individual doing commercial solo work
Contact support before purchasing if more than one person needs to use CodexFlow.
Roadmap direction
CodexFlow’s next product direction is focused on:
- More automated paid fulfillment
- Stronger customer access flow
- More secure production signing operations
- Better upgrade and renewal experience
- Team / Business licensing design
- Additional workflow packs for common repository types
- Improved documentation for stack-specific workflows
Roadmap items are not included until they appear in a released version.
Stay current
Before using CodexFlow in an important repository:
- Install the current release.
- Run the health check.
- Review generated files in Git.
- Confirm your license status.
- Keep your activation and paid payload materials private.