> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase12-session02-release-closeout-and-rollout-readiness/codex-release-notes.md). # Codex Release Notes **Session ID**: `phase12-session02-release-closeout-and-rollout-readiness` **Package**: Cross-cutting **Date**: 2026-05-31 **Status**: Complete *** ## Changelog-Ready Entry ### Added * Added first-class local Codex CLI hook support alongside the existing Claude Code hook path. * Added explicit provider selection for local setup: `factionos init --cli claude`, `factionos init --cli codex`, and `factionos init --cli all`. * Added user-level Codex hook install support from the source-controlled `apps/hooks/hooks.codex.json` template. * Added Codex-aware local diagnostics through `factionos status --cli codex` and `factionos doctor --cli codex`. * Added Codex uninstall support through `factionos uninstall --cli codex`, restoring the first FactionOS backup when available or removing only FactionOS-managed Codex hooks. * Added Codex-aware local ingest, protocol vocabulary, cockpit labels, search/filter behavior, and replay/export-adjacent redaction evidence. ### Changed * `factionos init` remains Claude Code by default for this release; Codex is enabled through explicit provider selection. * Release docs now treat direct user-level Codex hooks as the supported first Codex release path. * Codex hook trust review remains a manual user step in a new Codex CLI session using `/hooks`. ### Deferred * Codex plugin packaging is intentionally deferred for this release. * Project-local trusted `.codex` setup is deferred. * Plugin install, plugin cache refresh, plugin trust review, and plugin uninstall validation are N/A because no plugin package is shipped. ### Security And Privacy * Codex hooks remain local-first and observation-only. * The installer does not mutate Codex auth, provider, telemetry, model, profile, API key, account settings, trusted-project state, or hook trust decisions. * Hook handlers and diagnostics must not expose raw prompts, patch bodies, command output, terminal output, transcript paths, MCP argument bodies, tokens, credentials, hook config bodies, or broad local paths. * CLI uninstall is hook-config cleanup only; it is not broad trusted erasure. ### Known Limitations * Users must review loaded Codex hooks with `/hooks`; this release does not bypass Codex hook trust or automatically approve permission requests. * Codex support is local hook observability, not hosted telemetry or remote execution. * Production-hosted validation is not claimed unless a safe live hosted smoke pass is recorded separately. * Hosted identity, hosted storage, analytics capture, push delivery, tunnels, public replay hosting, remote execution, and broad trusted erasure remain unavailable or future scope. *** ## Short Release Summary FactionOS now supports Claude Code and Codex CLI as local hook targets. Claude Code remains the default setup path, and Codex is available through `factionos init --cli codex` or `factionos init --cli all`. After installing Codex hooks, start a new Codex CLI session and review the loaded hooks with `/hooks`. Codex plugin packaging is explicitly deferred for this release. The supported path is direct user-level hooks plus `status`, `doctor`, and `uninstall` diagnostics for local posture and cleanup. *** ## Operator Rollout Notes 1. Link or install the FactionOS CLI. 2. Run `factionos init --cli codex --faction ` or `factionos init --cli all`. 3. Start the local runtime with `factionos start --daemon`. 4. Open the cockpit with `factionos open`. 5. Start a new Codex CLI session. 6. Review loaded hooks with `/hooks`. 7. Use `factionos status --cli codex` and `factionos doctor --cli codex` for local posture. 8. Use `factionos uninstall --cli codex` for managed-hook cleanup. *** ## Release Note Exclusions Do not include release copy claiming: * Codex plugin availability. * Plugin install, cache refresh, plugin trust, or plugin uninstall success. * Hook trust bypass or automatic permission approval. * Project-local trusted `.codex` setup. * Hosted telemetry, hosted auth, hosted storage, production-hosted validation, analytics capture, public replay hosting, push delivery, tunnels, remote access, remote execution, or broad trusted erasure. *** ## Final Gate Insert Final gate outcomes: * Focused Codex installer and hook-map tests passed: 2 files and 20 tests. * Isolated Codex rollout smoke passed: install, status, doctor, and uninstall preserved unmanaged state and kept `/hooks` guidance visible. * Format, lint, workspace typecheck, full tests, and workspace build passed. * Full tests passed with 175 test files passed, 1 skipped; 2372 tests passed, 1 skipped. * Media tooling, visual promotion, public demo media, draft manifest, battlefield asset, and media release gates passed. Visual promotion retained expected metadata-pending and non-release warnings. * Hosted smoke no-network mode passed as no-claim evidence: four unavailable targets and zero failures. * Secret scan passed over tracked text files. * `git diff --check` passed. Release note caveat: * Do not describe the public demo, Worker, app shell, hosted identity, hosted storage, analytics, public replay, push, remote access, or remote execution as production-validated by this release. The only hosted smoke run in this session was no-network no-claim mode. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase12-session02-release-closeout-and-rollout-readiness/codex-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.