Activate the license
Verify the signed activation file and register the local install identity. codexflow license activate
Workflow
From paid license to reviewable repo layer.
CodexFlow verifies the license, checks entitlement, installs a signed payload, and writes local files you inspect in Git.
Start clean
Put the install on its own branch.
CodexFlow writes ordinary repo files. A branch keeps the whole install visible, reversible, and easy to compare before anything reaches main.
$ git checkout -b codexflow-install
$ git status --short
# review every generated file before commit
Install path
Verify first. Write files second.
Every paid install follows the same gate: local signature checks, online entitlement checks, then Git-reviewable output.
Check entitlement
Confirm the license is active, eligible for this payload, and inside its soft device limit. online check
Install the payload
Verify the signed manifest, archive checksum, size, license tier, and entitlement before writing files. payload install
Emit and review
Write the operating layer into the repo, then inspect it before committing. codexflow emit
The emitted layer is just files.
Once the payload passes verification, CodexFlow writes the operating stack into the project where Codex and Git can read it.
Project instructions
AGENTS.md captures repo rules, branch discipline, test expectations, sensitive files, and the definition of done.
AGENTS.mdSpecialist skills
2,000+ workflows give Codex task-specific process, checks, and handoff rules instead of one generic prompt.
.agents/skillsAgent roles
Planning, implementation, review, security, release, and memory roles keep each job inside a focused mode.
.codexflow/agentsPersistent memory
Decisions, handoffs, incidents, and learned project rules survive the current chat and stay with the repo.
.codexflow/memorySafe commands
Repeatable workflows turn start, plan, build, review, fix, ship, and rollback into shared repo procedures.
.codexflow/commandsAutomated checks
Deterministic guards catch branch mistakes, secrets, payload issues, stale memory, and public leaks.
.codexflow/checksDaily workflow
Codex starts with project context already loaded.
The difference is not a bigger prompt. The repo carries the operating rules forward between sessions.
Cold Codex session before
- Paste project rules back into every new thread.
- Hope the model remembers sensitive files, tests, and release rules.
- Rebuild context when another tool or teammate touches the repo.
CodexFlow-backed repo after
- Codex reads AGENTS.md, skills, memory, commands, and checks from the repo.
- Plans, reviews, and handoffs use the same local operating layer.
- You inspect changes with
git diffand revert like any other files.
Trust model
License checks without opaque installs.
The online layer lets revoked, expired, or over-limit licenses fail while keeping the payload signed and the output local.
Checks before install
- Signed activation verified locally
- Signed manifest checked before archive use
- Archive checksum and size verified
- Server-side revocation and entitlement check
Local-first behavior
- Soft install identity with 3-device limit
- 7-day offline grace for already-installed payloads
- No hardware fingerprinting in v1
- No CLI usage telemetry in this release
- Independent toolkit for Codex users
What the workflow does not do.
CodexFlow gives Codex a repo operating layer. You still own the code, review the diff, and decide what ships.
- It does not bypass Codex review
- It does not hide files from Git
- It does not publish payload archives publicly
- It does not replace your tests
- It does not claim OpenAI affiliation
- It does not install a background daemon
Install it where your work already lives.
Activate the license, verify the signed payload, emit the files, and review the result in Git.