Use gald3r with OpenAI Codex¶
Gald3r integrates with local Codex CLI, desktop and IDE installations. Check the installed Codex version and help: available settings and hook events vary by version. This page does not claim parity with hosted Codex environments.
The generated overlay supplies project instructions, skills, agent definitions, MCP configuration and five lifecycle hooks: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse and Stop. Generation is not proof that a particular host discovered or executed them. Legacy prompt files are not a guarantee of native slash-command support.
The board lives under .gald3r/project/ in layout v2. Use gald3r task
and gald3r bug commands to resolve the layout rather than hardcoding paths.
Get started¶
gald3r setup
gald3r platform install codex --generated
Python 3 is still required for these hook scripts; the main Gald3r CLI is native. Install preparation resolves Python through the shared platform resolver, enables UTF-8 mode, and anchors the script paths to the target project. It fails with an actionable prerequisite message if Python cannot be found. Windows hook paths containing quotes, percent signs or exclamation marks are rejected rather than passed to the command interpreter with ambiguous meaning.
For an existing overlay, inspect the installation preview and preserve custom
files. Reinstallation requires --force; pair it with
--preserve-user-mods to keep customized files and produce reconciliation
sidecars. --force alone permits overwrites, with a backup by default.
A changed generated hook definition may require renewed trust. After
installation, use Codex's hook review interface (/hooks where available) to
review and approve the exact definitions yourself. Project trust, MCP discovery
and hook trust are separate. Gald3r must not write approvals on your behalf.
Verify a fresh session produces the expected lifecycle events and a scoped chat
log with the same session identity. Simulated calls and an enabled MCP entry are
useful diagnostics, but do not establish working Codex lifecycle integration.
After moving a project, regenerate and review its anchored commands again;
use the preservation option to retain customized hooks for reconciliation.
In the recorded September 2026 smoke, Codex CLI 0.144.1 discovered the host's
$CODEX_HOME/config.toml MCP entry from a fresh project. That observation is
specific to the tested CLI build; it does not establish configuration discovery
for other versions or the app-bundled client. See
docs/maintainer/_CODEX_MCP_AND_WORKTREE_SMOKE.md for a completed
initialize/tools-list/tools-call round-trip against the exact natively-discovered
executable, with identity and capability recorded.