• Tech Dev NotesTech Dev Notes
Apps
  • App lookup
  • App compare
Market movement
  • App charts
  • App rankings
Visual proof
  • App screens
  • App listing screenshots
  • App icons
Build intelligence
  • App tech stacks
  • Tool releases
  • Developers
More
  • X feature flags
  • Grokipedia
  • Blog
  • Follow on X
Skip to content
All content/ filesChangelog

codex-cli/latest/content · 0.143.0-alpha.26

docs/config.md

Docs·726 B·16 lines

content/

  • .

    • AGENTS.md
    • CHANGELOG.md
    • config.md
    • dependencies-lock.txt
    • README.md
    • version.json
  • docs

    • agents_md.md
    • authentication.md
    • CLA.md
    • config.md
    • contributing.md
    • example-config.md
    • exec.md
    • execpolicy.md
    • getting-started.md
    • install.md
    • license.md
    • open-source-fund.md
    • sandbox.md
    • skills.md
    • slash_commands.md
  • docs/codex-rs

    • bazel.md
    • codex_mcp_interface.md
    • protocol_v1.md
  • completions/bash

    • codex.bash
  • completions/fish

    • codex.fish
  • completions/zsh

    • codex.zsh
  • prompts

    • gpt_5_1_prompt.md
    • gpt_5_2_prompt.md
    • gpt_5_codex_prompt.md
    • gpt-5.1-codex-max_prompt.md
    • gpt-5.2-codex_prompt.md
    • prompt_with_apply_patch_instructions.md

Configuration

For basic configuration instructions, see this documentation.

For advanced configuration instructions, see this documentation.

For a full configuration reference, see this documentation.

Lifecycle hooks

Admins can set top-level allow_managed_hooks_only = true in requirements.toml to ignore user, project, and session hook configs while still allowing managed hooks from requirements and managed config layers. This setting is only supported in requirements.toml; putting it in config.toml does not enable managed-hooks-only mode.

Previousdocs/codex-rs/protocol_v1.mdNextdocs/contributing.md

© 2026 Tech Dev Notes

RSSAboutAPIPrivacyTermsSitemap@techdevnotes