Init Project
Guide the user through first-time Codex project bootstrap for project policies and operator mode state.
Continuity contract
- Follow the shared Primary-task continuity and side work rule in AGENTS.md; retain the admitted primary outcome and next authorized action.
- Answer brief questions inline. Promptly delegate eligible substantive admitted side work to matching non-spawning specialists under existing authority, capacity, full resource surfaces and gates; continue ready primary work in the same turn without waiting for the side result.
- Defer conflicting side work with its owner/resume point or use already-authorized validated isolation; preserve manual modes and explicit user stop/pause/cancel/reprioritization and native Goal holds.
- After an accepted phase or completed batch, continue to the next clear step unless a real gate blocks progression.
- Before claiming completion, reconcile the current result against the original request and any still-open required follow-up inside the same task.
- If a required next action is already known and still inside the current task, keep the task open instead of stopping at a partial batch.
Preset expansion table
Presets are init-time shortcuts only. They expand into canonical agents-mode keys. The preset name is NOT persisted in the file.
| Key | default (safe-init) |
absolute-balance (everyday center) |
external-aggressive (aggressive external use) |
correctness-first (no-time-limit correctness) |
power-mode (hardest-task maximum result) |
max-speed (speed-first) |
|---|---|---|---|---|---|---|
consultantMode |
disabled |
internal |
external |
external |
external |
disabled |
delegationMode |
auto |
auto |
force |
force |
force |
auto |
parallelMode |
auto |
auto |
force |
auto |
force |
force |
mcpMode |
auto |
auto |
auto |
force |
force |
auto |
preferExternalWorker |
false |
false |
true |
true |
true |
false |
preferExternalReviewer |
false |
true |
true |
true |
true |
false |
externalProvider |
auto |
auto |
auto |
auto |
auto |
auto |
externalPriorityProfile |
balanced |
balanced |
balanced |
balanced |
quality-first |
balanced |
reserveResolver |
claude-sonnet |
claude-sonnet |
claude-sonnet |
claude-sonnet |
claude-sonnet |
claude-sonnet |
externalPriorityProfiles |
shipped as-is | shipped as-is | shipped as-is | shipped as-is | shipped as-is | shipped as-is |
externalOpinionCounts |
all 1 |
all 1 |
all 1 |
advisory+review lanes 2, others 1 |
advisory+review lanes 2, others 1 |
all 1 |
externalCodexWorkdirMode |
neutral |
neutral |
neutral |
neutral |
neutral |
project |
externalClaudeWorkdirMode |
neutral |
neutral |
neutral |
neutral |
neutral |
project |
externalModelMode |
runtime-default |
runtime-default |
runtime-default |
pinned-top-pro |
pinned-top-pro |
runtime-default |
externalCodexProfile |
gpt-6.1-sol-xhigh |
default |
default |
gpt-6.1-sol-xhigh |
gpt-6.1-sol-xhigh |
gpt-6.1-sol-high |
externalClaudeProfile |
opus-xhigh |
sonnet-high |
sonnet-high |
opus-max |
opus-max |
sonnet-high |
correctness-first and power-mode lane-specific opinion counts:
advisory.repo-understanding: 2advisory.design-adr: 2review.pre-pr: 2review.security: 2review.performance-architecture: 2review.ui-visual-correctness: 2- all other lanes:
1
Routing conventions (not persisted as keys):
- same-host fast-path: under
external-aggressiveandmax-speed, when neutral isolation is not required, allow per-invocation explicit self-provider override. Keep the stored file canonical; this is a routing rule, not a persisted key. - overflow means spill, not serialize: under
external-aggressive, internal slot saturation pushes independent eligible lanes into$external-worker,$external-reviewer, or$external-brigadeby default. - power-mode means hardest-task maximum useful result: start from the
quality-firstprovider-priority profile, then combinecorrectness-firstvalidation density withexternal-aggressivefan-out, while keeping neutral workdirs and production-onlyautorouting so the extra power does not become a hidden project-state or example-provider shortcut.
Steps
Read current state.
- Read the project's root
AGENTS.mdand check whether a## Project policiessection already exists. - Read
.agents/.agents-mode.yamlfirst. - If it is missing, read legacy
.agents/.agents-modeas compatibility input only. - If both local files are missing, fall back through pack-local global
~/.codex/.agents-mode.yaml, pack-local global legacy~/.codex/.agents-mode, then the shared cross-pack global~/.agents-mode.yaml(alongside~/.claude.json), before applying built-in defaults. Each key resolves to the highest layer that defines it; layers compose, they do not replace each other wholesale. - Normalize effective values in memory through the dispatch owner's existing per-key read order before presenting or trusting them. Use any global fallback as the starting point for project-local review; do not rewrite borrowed/global configuration on read. Persist the explicitly selected project configuration to the canonical project-local
.yamlpath only within the authorized configuration write in Step 7, and do not recreate legacy files. - If either surface already exists, show the current values and ask whether to keep them, review them, or start fresh.
- Read the project's root
Read the installed canonical sources.
- Read the installed policy catalog from
../lead/policies-catalog.md. - Read the installed Codex dispatch contract from
../lead/external-dispatch.md. - Use those two files as the canonical source for policy choices, allowed
agents-modevalues, and write rules instead of inventing parallel semantics.
- Read the installed policy catalog from
Configure project policies.
- Walk through each policy area from the catalog one at a time.
- For each area:
- state the policy name and question
- list the allowed options with concise descriptions
- show the default
- accept shorthand answers or the default
- If the user says "defaults for the rest" or similar, apply defaults to all remaining policy areas.
Select a preset (optional).
- Ask the user if they want to start from a preset:
default,absolute-balance,external-aggressive,correctness-first,power-mode, ormax-speed. - If the user picks a preset, apply its full key expansion from the table above as the starting values.
- After applying a preset, ask whether to write that preset as-is or fine-tune individual keys first.
- If the user says
use the preset,preset only,apply as-is, or otherwise declines manual tweaking, skip the key-by-key operator-mode walkthrough and carry the preset-expanded values straight to confirmation. - If the user says "custom" or skips this step, start from the
defaultbaseline. - The preset name is NOT persisted — only the expanded canonical keys are written.
- Ask the user if they want to start from a preset:
Configure operator modes.
- Run this step only when the user started from
custom, skipped preset selection, or explicitly asked to fine-tune after selecting a preset. - Walk through the canonical
agents-modekeys one at a time:consultantModedelegationModeparallelModemcpModepreferExternalWorkerpreferExternalReviewerexternalProviderexternalPriorityProfilereserveResolverexternalPriorityProfilesexternalOpinionCountsexternalCodexWorkdirModeexternalClaudeWorkdirModeexternalModelModeexternalCodexProfileexternalClaudeProfile
- Use the existing value when present, the preset-expanded value if one was selected, or otherwise default to:
consultantMode: disableddelegationMode: autoparallelMode: automcpMode: autopreferExternalWorker: falsepreferExternalReviewer: falseexternalProvider: autoexternalPriorityProfile: balancedreserveResolver: claude-sonnet- shipped
externalPriorityProfiles externalOpinionCountsdefaulting each documented lane to1externalCodexWorkdirMode: neutralexternalClaudeWorkdirMode: neutralexternalModelMode: runtime-defaultexternalCodexProfile: gpt-6.1-sol-xhighexternalClaudeProfile: opus-xhigh
- Accept shorthand answers such as
force,external reviewer only,opus, ordefaults for the rest.
- Run this step only when the user started from
Confirm the final choices.
- Present one summary table for
## Project policies. - Present one summary table for
.agents/.agents-mode.yaml. - Ask for confirmation before writing.
- Present one summary table for
Write
.agents/.agents-mode.yaml.- Write the canonical file to
.agents/.agents-mode.yaml. - Preserve unknown keys when updating an existing file.
- Treat comment-free, partial, or older-layout files as legacy input and rewrite them to the current canonical format instead of preserving stale layout.
- Do not recreate legacy
.agents/.agents-mode; write the canonical output only to.agents/.agents-mode.yaml. - Keep one key per line and include inline comments for every canonical scalar key plus every shipped
externalPriorityProfiles/externalOpinionCountsentry. - Refresh the shipped
externalPriorityProfilesandexternalOpinionCountsblocks to the current pack version while preserving the effective values of known keys and any unknown keys.
Use this canonical shape:
consultantMode: {value} # allowed: external | internal | disabled; default: disabled delegationMode: {value} # allowed: manual | auto | force; default: auto parallelMode: {value} # allowed: manual | auto | force; default: auto mcpMode: {value} # allowed: auto | force; default: auto preferExternalWorker: {value} # allowed: false | true; default: false preferExternalReviewer: {value} # allowed: false | true; default: false externalProvider: {value} # selectable here: auto | codex | claude; default: auto; kimi is explicit-only and is not initialized as a project-local scalar; grok remains unavailable in 1.x; removed gemini/qwen values fail closed with E_EXTERNAL_PROVIDER_REMOVED externalPriorityProfile: {value} # allowed: balanced | quality-first | <repo-local production profile>; default: balanced reserveResolver: {value} # allowed: disabled | claude-sonnet | claude-wrapper | wrapper:<command>; default: claude-sonnet externalPriorityProfiles: {value} # allowed: structured profile map externalOpinionCounts: {value} # allowed: structured lane-count map externalCodexWorkdirMode: {value} # allowed: neutral | project; default: neutral externalClaudeWorkdirMode: {value} # allowed: neutral | project; default: neutral externalModelMode: {value} # allowed: runtime-default | pinned-top-pro; default: runtime-default externalCodexProfile: {value} # allowed: default | gpt-6.1-sol-high | gpt-6.1-sol-xhigh | gpt-6.1-sol-max | gpt-6-sol-high | gpt-6-sol-xhigh | gpt-6-sol-max | gpt-5.6-sol-xhigh | gpt-5.6-sol-max | gpt-5.6-terra; default: gpt-6.1-sol-xhigh externalClaudeProfile: {value} # allowed: sonnet-high | opus-xhigh | opus-max | fable-xhigh; default: opus-xhigh- Write the canonical file to
Write
## Project policiestoAGENTS.md.- Add or replace only the
## Project policiessection in the project's rootAGENTS.md. - If the section already exists, update it in place.
- If it does not exist, append it at the end of the file so it stays user-managed outside the installed pack content.
- Use this rendered format:
## Project policies - **Testing:** {methodology}, {coverage target or "no coverage target"} - **Commits:** {format description} - **Branching:** {model description} - **File size:** {policy description} - **Error handling:** {style description} - **PR review:** {policy description} - **Documentation:** {when to write} - **Language style:** {preferences or "follow existing conventions"} - **Dependencies:** {policy description}- Add or replace only the
Confirm completion.
- Tell the user the project policies and operator mode file are saved.
- Mention
$second-opinionfor later consultant toggle changes.
Rules
- Be concise; the catalog and dispatch contract hold the details.
- Do not invent extra policy keys or extra
agents-modekeys. - Preserve unknown keys in
.agents/.agents-mode.yamlwhen updating. - For decision-driving reads, use the dispatch owner's per-key precedence (local
.agents/.agents-mode.yaml, local legacy.agents/.agents-mode, pack-local global~/.codex/.agents-mode.yaml, pack-local global legacy~/.codex/.agents-mode, shared cross-pack global~/.agents-mode.yaml, then built-in defaults) and the in-memory normalization in Step 1; inspection grants no write to the source overlay. Persist only the explicitly selected authorized project configuration in Step 7. - Do not modify any other section of
AGENTS.md. - Treat root
AGENTS.mdas the project-runtime target, not the Orchestrarium monorepo maintenance overlay.