codex-multi-auth 2.23.0 → 2.24.0

package/dist/lib/context-overflow.js

@@ -33,16 +33,16 @@ export function isContextOverflowError(status, bodyText) {
 /**
  * The message shown to users when context overflow occurs
  */
-const CONTEXT_OVERFLOW_MESSAGE = `[Plugin Notice] Context is too long for this model.
-
-Please use one of these commands to reduce context size:
-
-• **/compact** - Compress conversation history (recommended)
-• **/clear** - Start fresh with empty context
-• **/undo** - Remove recent messages
-
-Then retry your request.
-
+const CONTEXT_OVERFLOW_MESSAGE = `[Plugin Notice] Context is too long for this model.
+
+Please use one of these commands to reduce context size:
+
+• **/compact** - Compress conversation history (recommended)
+• **/clear** - Start fresh with empty context
+• **/undo** - Remove recent messages
+
+Then retry your request.
+
 Alternatively, you can switch to a model with a larger context window.`;
 /**
  * Creates a synthetic SSE response for context overflow errors.

package/dist/lib/oauth-success.html

@@ -1,126 +1,126 @@
-<!doctype html>
-<html lang="en">
-<head>
-  <meta charset="utf-8" />
-  <meta name="viewport" content="width=device-width, initial-scale=1" />
-  <title>Codex Sign-In Complete</title>
-  <style>
-    :root {
-      color-scheme: dark;
-      --bg: #0b0b0b;
-      --panel: #111111;
-      --text: #f2f2f2;
-      --muted: #a3a3a3;
-      --line: #232323;
-      --ok: #7cf0a6;
-    }
-
-    * {
-      box-sizing: border-box;
-    }
-
-    body {
-      margin: 0;
-      min-height: 100vh;
-      display: grid;
-      place-items: center;
-      background: var(--bg);
-      color: var(--text);
-      font-family: "Geist Mono", "GeistMono", ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace;
-      padding: 24px;
-    }
-
-    main {
-      width: min(520px, 100%);
-      background: var(--panel);
-      border: 1px solid var(--line);
-      border-radius: 12px;
-      padding: 20px;
-      display: grid;
-      gap: 14px;
-    }
-
-    h1 {
-      margin: 0;
-      font-size: 20px;
-      font-weight: 600;
-      letter-spacing: -0.02em;
-    }
-
-    p {
-      margin: 0;
-      color: var(--muted);
-      font-size: 14px;
-      line-height: 1.5;
-    }
-
-    .status {
-      display: inline-flex;
-      align-items: center;
-      gap: 8px;
-      color: var(--ok);
-      font-size: 13px;
-    }
-
-    .dot {
-      width: 8px;
-      height: 8px;
-      border-radius: 50%;
-      background: currentColor;
-    }
-
-    dl {
-      margin: 0;
-      display: grid;
-      grid-template-columns: 120px 1fr;
-      gap: 8px 12px;
-      font-size: 13px;
-    }
-
-    dt {
-      color: var(--muted);
-    }
-
-    dd {
-      margin: 0;
-      color: var(--text);
-      word-break: break-word;
-    }
-
-    code {
-      background: #171717;
-      border: 1px solid var(--line);
-      border-radius: 6px;
-      padding: 2px 6px;
-      font-family: inherit;
-      font-size: 12px;
-    }
-
-    @media (max-width: 520px) {
-      dl {
-        grid-template-columns: 1fr;
-      }
-    }
-  </style>
-</head>
-<body>
-  <main role="main" aria-label="OAuth callback received">
-    <h1>Sign-in complete</h1>
-    <p>Return to your terminal to finish Codex login.</p>
-
-    <div class="status" aria-live="polite">
-      <span class="dot" aria-hidden="true"></span>
-      Callback received
-    </div>
-
-    <dl>
-      <dt>Endpoint</dt>
-      <dd><code>localhost:1455</code></dd>
-      <dt>Flow</dt>
-      <dd>OAuth callback captured</dd>
-      <dt>Next</dt>
-      <dd>Close this tab and continue in terminal</dd>
-    </dl>
-  </main>
-</body>
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1" />
+  <title>Codex Sign-In Complete</title>
+  <style>
+    :root {
+      color-scheme: dark;
+      --bg: #0b0b0b;
+      --panel: #111111;
+      --text: #f2f2f2;
+      --muted: #a3a3a3;
+      --line: #232323;
+      --ok: #7cf0a6;
+    }
+
+    * {
+      box-sizing: border-box;
+    }
+
+    body {
+      margin: 0;
+      min-height: 100vh;
+      display: grid;
+      place-items: center;
+      background: var(--bg);
+      color: var(--text);
+      font-family: "Geist Mono", "GeistMono", ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New", monospace;
+      padding: 24px;
+    }
+
+    main {
+      width: min(520px, 100%);
+      background: var(--panel);
+      border: 1px solid var(--line);
+      border-radius: 12px;
+      padding: 20px;
+      display: grid;
+      gap: 14px;
+    }
+
+    h1 {
+      margin: 0;
+      font-size: 20px;
+      font-weight: 600;
+      letter-spacing: -0.02em;
+    }
+
+    p {
+      margin: 0;
+      color: var(--muted);
+      font-size: 14px;
+      line-height: 1.5;
+    }
+
+    .status {
+      display: inline-flex;
+      align-items: center;
+      gap: 8px;
+      color: var(--ok);
+      font-size: 13px;
+    }
+
+    .dot {
+      width: 8px;
+      height: 8px;
+      border-radius: 50%;
+      background: currentColor;
+    }
+
+    dl {
+      margin: 0;
+      display: grid;
+      grid-template-columns: 120px 1fr;
+      gap: 8px 12px;
+      font-size: 13px;
+    }
+
+    dt {
+      color: var(--muted);
+    }
+
+    dd {
+      margin: 0;
+      color: var(--text);
+      word-break: break-word;
+    }
+
+    code {
+      background: #171717;
+      border: 1px solid var(--line);
+      border-radius: 6px;
+      padding: 2px 6px;
+      font-family: inherit;
+      font-size: 12px;
+    }
+
+    @media (max-width: 520px) {
+      dl {
+        grid-template-columns: 1fr;
+      }
+    }
+  </style>
+</head>
+<body>
+  <main role="main" aria-label="OAuth callback received">
+    <h1>Sign-in complete</h1>
+    <p>Return to your terminal to finish Codex login.</p>
+
+    <div class="status" aria-live="polite">
+      <span class="dot" aria-hidden="true"></span>
+      Callback received
+    </div>
+
+    <dl>
+      <dt>Endpoint</dt>
+      <dd><code>localhost:1455</code></dd>
+      <dt>Flow</dt>
+      <dd>OAuth callback captured</dd>
+      <dt>Next</dt>
+      <dd>Close this tab and continue in terminal</dd>
+    </dl>
+  </main>
+</body>
 </html>

package/dist/lib/policy/runtime-policy-cache.js

@@ -168,7 +168,7 @@ export function loadAccountPolicyStoreCached() {
     return loadStoreCached({
         path: getAccountPolicyPath(),
         cache: ACCOUNT_POLICY_CACHE,
-        load: loadAccountPolicyStore,
+        load: () => loadAccountPolicyStore({ strict: true }),
         isEmptyStore: (store) => Object.keys(store.accounts).length === 0,
     });
 }

package/dist/lib/policy/runtime-policy.d.ts

@@ -25,6 +25,7 @@ export interface RuntimePolicyDecision {
     blockedAccountReasons?: Record<number, string>;
     scoreBoostByAccount: Record<number, number>;
     priorityByAccount?: Record<number, number>;
+    emergencyAccountIndexes?: Set<number>;
     budgetEvaluations: BudgetGuardEvaluation[];
 }
 export interface RuntimePolicyState {

package/dist/lib/policy/runtime-policy.js

@@ -101,6 +101,7 @@ export async function evaluateRuntimePolicy(input) {
     const blockedAccountReasons = {};
     const scoreBoostByAccount = {};
     const priorityByAccount = {};
+    const emergencyAccountIndexes = new Set();
     const profile = input.state.project.profile;
     if (profile?.modelDenylist.length && matchesModel(profile.modelDenylist, input.model)) {
         reasons.push("routing profile denies requested model");
@@ -131,6 +132,8 @@ export async function evaluateRuntimePolicy(input) {
         }, account.index);
         const accountPolicy = input.state.accountPolicies.accounts[accountKey];
         priorityByAccount[account.index] = accountPolicy?.priority ?? 1;
+        if (accountPolicy?.emergencyOnly)
+            emergencyAccountIndexes.add(account.index);
         let boost = 0;
         if (accountPolicy?.paused) {
             blockedAccountIndexes.add(account.index);
@@ -186,6 +189,7 @@ export async function evaluateRuntimePolicy(input) {
         blockedAccountReasons,
         scoreBoostByAccount,
         priorityByAccount,
+        emergencyAccountIndexes,
         budgetEvaluations,
     };
 }

package/dist/lib/preemptive-quota-scheduler.js

@@ -1,4 +1,4 @@
-import { MAX_RATE_LIMIT_DELAY_MS } from "./constants.js";
+import { MAX_RATE_LIMIT_DELAY_MS, RATE_LIMIT_CACHE_TTL_MS } from "./constants.js";
 import { quotaLeftPercentFromUsed } from "./quota-readiness.js";
 const DEFAULT_REMAINING_PERCENT_THRESHOLD = 5;
 const DEFAULT_MAX_DEFERRAL_MS = 2 * 60 * 60_000;
@@ -219,6 +219,11 @@ export class PreemptiveQuotaScheduler {
         const snapshot = this.snapshots.get(key);
         if (!snapshot)
             return { defer: false, waitMs: 0 };
+        const cacheRemainingMs = snapshot.updatedAt + RATE_LIMIT_CACHE_TTL_MS - now;
+        if (cacheRemainingMs <= 0) {
+            this.snapshots.delete(key);
+            return { defer: false, waitMs: 0 };
+        }
         // For a 429 deferral, only count a window whose reset is genuinely a
         // rate-limit / exhaustion window. A window carrying a healthy usedPercent
         // (e.g. a weekly secondary at 30% from a prior 200 snapshot) is NOT the
@@ -239,7 +244,7 @@ export class PreemptiveQuotaScheduler {
             .filter((value) => value > 0);
         const longestWait = waitCandidates.length > 0 ? Math.max(...waitCandidates) : 0;
         if (snapshot.status === 429 && longestWait > 0) {
-            const bounded = Math.min(longestWait, this.maxDeferralMs);
+            const bounded = Math.min(longestWait, this.maxDeferralMs, cacheRemainingMs);
             if (bounded > 0) {
                 return { defer: true, waitMs: bounded, reason: "rate-limit" };
             }
@@ -260,7 +265,11 @@ export class PreemptiveQuotaScheduler {
             ? getNearExhaustedWait(snapshot.secondary)
             : 0);
         if (nearExhaustedWait > 0) {
-            return { defer: true, waitMs: nearExhaustedWait, reason: "quota-near-exhaustion" };
+            return {
+                defer: true,
+                waitMs: Math.min(nearExhaustedWait, cacheRemainingMs),
+                reason: "quota-near-exhaustion",
+            };
         }
         return { defer: false, waitMs: 0 };
     }

package/dist/lib/prompts/codex-host-bridge.js

@@ -7,142 +7,142 @@
  *
  * Token Count: ~450 tokens (~90% reduction vs full host prompt)
  */
-export const CODEX_HOST_BRIDGE = `# Codex Host Bridge
-
-You are running Codex through a host terminal coding runtime. The host provides specific tools to help you work efficiently.
-
-## CRITICAL: Tool Usage
-
-<critical_rule priority="0">
-apply_patch/applyPatch are Codex names, but host tool names vary by version.
-- Inspect the actual tool list before editing.
-- If \`edit\` exists: use \`edit\` for precise in-place string replacements and hashline edits.
-- If \`edit\` is absent and \`apply_patch\` exists: use \`apply_patch\` for those precise/hashline edits in this plugin.
-- For diff-style or multi-line structural edits: use \`patch\` if available, otherwise use \`apply_patch\`.
-- In this plugin, \`edit\` / \`apply_patch\` also support hashline refs (\`lineRef\`, \`endLineRef\`, \`operation\`, \`content\`)
-</critical_rule>
-
-<critical_rule priority="0">
-UPDATE_PLAN DOES NOT EXIST -> USE "todowrite" INSTEAD
-- NEVER use: update_plan, updatePlan, read_plan, readPlan
-- ALWAYS use: todowrite for task/plan updates, todoread to read plans
-- Before plan operations: Verify you're using "todowrite", NOT "update_plan"
-</critical_rule>
-
-## Available Host Tools
-
-**File Operations:**
-- \`write\`  - Create new files
-  - Overwriting existing files requires a prior Read in this session; default to ASCII unless the file already uses Unicode.
-- \`edit\`   - Modify existing files with string replacement (version-dependent)
-  - Requires a prior Read in this session; preserve exact indentation; ensure \`oldString\` uniquely matches or use \`replaceAll\`; edit fails if ambiguous or missing.
-  - Never pass unresolved template placeholders in \`oldString\` (e.g. \`\${TARGET_SNIPPET}\`); \`oldString\` must be literal text copied from the current file.
-  - For complex multi-line changes: break into multiple sequential edit calls, each with unique oldString context.
-- \`apply_patch\` - May be the edit/patch tool name in newer host builds (version-dependent)
-  - In this plugin, \`apply_patch\` also accepts hashline edit args (\`path\`, \`lineRef\`, \`endLineRef\`, \`operation\`, \`content\`) when \`edit\` is not available.
-- \`hashline_read\` - Read file with hashline refs (\`L<line>#<hash>\`) for deterministic edits
-- \`patch\`  - Apply diff-style patches for multi-line updates (version-dependent)
-- \`read\`   - Read file contents
-
-Note: Tool naming is version-dependent. If \`edit\` is unavailable but \`apply_patch\` exists, use \`apply_patch\`.
-
-When available, prefer hashline workflow for reliability:
-1. Call \`hashline_read\` for target file and capture refs.
-2. Call \`edit\` or \`apply_patch\` with \`lineRef\` (and optional \`endLineRef\`) plus \`operation\` and \`content\`.
-3. Use legacy \`oldString\` / \`newString\` only when hashline refs are unavailable, and only with literal file text (no template placeholders).
-
-**Search/Discovery:**
-- \`grep\`   - Search file contents (tool, not bash grep); use \`include\` to filter patterns; set \`path\` only when not searching workspace root; for cross-file match counts use bash with \`rg\`.
-- \`glob\`   - Find files by pattern; defaults to workspace cwd unless \`path\` is set.
-- \`list\`   - List directories (requires absolute paths)
-
-**Execution:**
-- \`bash\`   - Run shell commands
-  - No workdir parameter; do not include it in tool calls.
-  - Always include a short description for the command.
-  - Do not use cd; use absolute paths in commands.
-  - Quote paths containing spaces with double quotes.
-  - Chain multiple commands with ';' or '&&'; avoid newlines.
-  - Use Grep/Glob tools for searches; only use bash with \`rg\` when you need counts or advanced features.
-  - Do not use \`ls\`/\`cat\` in bash; use \`list\`/\`read\` tools instead.
-  - For deletions (rm), verify by listing parent dir with \`list\`.
-
-**Network:**
-- \`webfetch\` - Fetch web content
-  - Use fully-formed URLs (http/https; http auto-upgrades to https).
-  - Always set \`format\` to one of: text | markdown | html; prefer markdown unless otherwise required.
-  - Read-only; short cache window.
-
-**Task Management:**
-- \`todowrite\` - Manage tasks/plans (REPLACES update_plan)
-- \`todoread\`  - Read current plan
-
-## Substitution Rules
-
-Base instruction says:    You MUST use instead:
-apply_patch           ->   patch (preferred if available), otherwise edit/apply_patch based on actual tool list
-update_plan           ->   todowrite
-read_plan             ->   todoread
-
-**Path Usage:** Use per-tool conventions to avoid conflicts:
-- Tool calls: \`read\`, \`edit\`, \`write\`, \`list\` require absolute paths.
-- Searches: \`grep\`/\`glob\` default to the workspace cwd; prefer relative include patterns; set \`path\` only when a different root is needed.
-- Presentation: In assistant messages, show workspace-relative paths; use absolute paths only inside tool calls.
-- Tool schema overrides general path preferences-do not convert required absolute paths to relative.
-
-## Verification Checklist
-
-Before file/plan modifications:
-1. Am I using the actual available edit tool name (\`edit\`, \`patch\`, or \`apply_patch\`)?
-2. Am I using "todowrite" NOT "update_plan"?
-3. Is this tool in the approved list above?
-4. Am I following each tool's path requirements?
-
-If ANY answer is NO -> STOP and correct before proceeding.
-
-## Host Working Style
-
-**Communication:**
-- Send brief preambles (8-12 words) before tool calls, building on prior context
-- Provide progress updates during longer tasks
-
-**Execution:**
-- Keep working autonomously until query is fully resolved before yielding
-- Don't return to user with partial solutions
-
-**Code Approach:**
-- New projects: Be ambitious and creative
-- Existing codebases: Surgical precision - modify only what's requested unless explicitly instructed to do otherwise
-
-**Testing:**
-- If tests exist: Start specific to your changes, then broader validation
-
-## Advanced Tools
-
-**Task Tool (Sub-Agents):**
-- Use the Task tool (functions.task) to launch sub-agents
-- Check the Task tool description for current agent types and their capabilities
-- Useful for complex analysis, specialized workflows, or tasks requiring isolated context
-- The agent list is dynamically generated - refer to tool schema for available agents
-
-**Parallelization:**
-- When multiple independent tool calls are needed, use multi_tool_use.parallel to run them concurrently.
-- Reserve sequential calls for ordered or data-dependent steps.
-
-**MCP Tools:**
-- Model Context Protocol servers provide additional capabilities
-- MCP tools are prefixed: \`mcp__<server-name>__<tool-name>\`
-- Check your available tools for MCP integrations
-- Use when the tool's functionality matches your task needs
-
-## What Remains from Codex
- 
-Sandbox policies, approval mechanisms, final answer formatting, git commit protocols, and file reference formats all follow Codex instructions. In approval policy "never", never request escalations.
-
-## Approvals & Safety
-- Assume workspace-write filesystem, network enabled, approval on-failure unless explicitly stated otherwise.
-- When a command fails due to sandboxing or permissions, retry with escalated permissions if allowed by policy, including a one-line justification.
-- Treat destructive commands (e.g., \`rm\`, \`git reset --hard\`) as requiring explicit user request or approval.
-- Never run \`git reset --hard\`, \`git checkout --\`, or force deletes unless the user explicitly asked for that exact action.
-- \`request_user_input\` is Plan-mode only; do not call it in Default mode.
+export const CODEX_HOST_BRIDGE = `# Codex Host Bridge
+
+You are running Codex through a host terminal coding runtime. The host provides specific tools to help you work efficiently.
+
+## CRITICAL: Tool Usage
+
+<critical_rule priority="0">
+apply_patch/applyPatch are Codex names, but host tool names vary by version.
+- Inspect the actual tool list before editing.
+- If \`edit\` exists: use \`edit\` for precise in-place string replacements and hashline edits.
+- If \`edit\` is absent and \`apply_patch\` exists: use \`apply_patch\` for those precise/hashline edits in this plugin.
+- For diff-style or multi-line structural edits: use \`patch\` if available, otherwise use \`apply_patch\`.
+- In this plugin, \`edit\` / \`apply_patch\` also support hashline refs (\`lineRef\`, \`endLineRef\`, \`operation\`, \`content\`)
+</critical_rule>
+
+<critical_rule priority="0">
+UPDATE_PLAN DOES NOT EXIST -> USE "todowrite" INSTEAD
+- NEVER use: update_plan, updatePlan, read_plan, readPlan
+- ALWAYS use: todowrite for task/plan updates, todoread to read plans
+- Before plan operations: Verify you're using "todowrite", NOT "update_plan"
+</critical_rule>
+
+## Available Host Tools
+
+**File Operations:**
+- \`write\`  - Create new files
+  - Overwriting existing files requires a prior Read in this session; default to ASCII unless the file already uses Unicode.
+- \`edit\`   - Modify existing files with string replacement (version-dependent)
+  - Requires a prior Read in this session; preserve exact indentation; ensure \`oldString\` uniquely matches or use \`replaceAll\`; edit fails if ambiguous or missing.
+  - Never pass unresolved template placeholders in \`oldString\` (e.g. \`\${TARGET_SNIPPET}\`); \`oldString\` must be literal text copied from the current file.
+  - For complex multi-line changes: break into multiple sequential edit calls, each with unique oldString context.
+- \`apply_patch\` - May be the edit/patch tool name in newer host builds (version-dependent)
+  - In this plugin, \`apply_patch\` also accepts hashline edit args (\`path\`, \`lineRef\`, \`endLineRef\`, \`operation\`, \`content\`) when \`edit\` is not available.
+- \`hashline_read\` - Read file with hashline refs (\`L<line>#<hash>\`) for deterministic edits
+- \`patch\`  - Apply diff-style patches for multi-line updates (version-dependent)
+- \`read\`   - Read file contents
+
+Note: Tool naming is version-dependent. If \`edit\` is unavailable but \`apply_patch\` exists, use \`apply_patch\`.
+
+When available, prefer hashline workflow for reliability:
+1. Call \`hashline_read\` for target file and capture refs.
+2. Call \`edit\` or \`apply_patch\` with \`lineRef\` (and optional \`endLineRef\`) plus \`operation\` and \`content\`.
+3. Use legacy \`oldString\` / \`newString\` only when hashline refs are unavailable, and only with literal file text (no template placeholders).
+
+**Search/Discovery:**
+- \`grep\`   - Search file contents (tool, not bash grep); use \`include\` to filter patterns; set \`path\` only when not searching workspace root; for cross-file match counts use bash with \`rg\`.
+- \`glob\`   - Find files by pattern; defaults to workspace cwd unless \`path\` is set.
+- \`list\`   - List directories (requires absolute paths)
+
+**Execution:**
+- \`bash\`   - Run shell commands
+  - No workdir parameter; do not include it in tool calls.
+  - Always include a short description for the command.
+  - Do not use cd; use absolute paths in commands.
+  - Quote paths containing spaces with double quotes.
+  - Chain multiple commands with ';' or '&&'; avoid newlines.
+  - Use Grep/Glob tools for searches; only use bash with \`rg\` when you need counts or advanced features.
+  - Do not use \`ls\`/\`cat\` in bash; use \`list\`/\`read\` tools instead.
+  - For deletions (rm), verify by listing parent dir with \`list\`.
+
+**Network:**
+- \`webfetch\` - Fetch web content
+  - Use fully-formed URLs (http/https; http auto-upgrades to https).
+  - Always set \`format\` to one of: text | markdown | html; prefer markdown unless otherwise required.
+  - Read-only; short cache window.
+
+**Task Management:**
+- \`todowrite\` - Manage tasks/plans (REPLACES update_plan)
+- \`todoread\`  - Read current plan
+
+## Substitution Rules
+
+Base instruction says:    You MUST use instead:
+apply_patch           ->   patch (preferred if available), otherwise edit/apply_patch based on actual tool list
+update_plan           ->   todowrite
+read_plan             ->   todoread
+
+**Path Usage:** Use per-tool conventions to avoid conflicts:
+- Tool calls: \`read\`, \`edit\`, \`write\`, \`list\` require absolute paths.
+- Searches: \`grep\`/\`glob\` default to the workspace cwd; prefer relative include patterns; set \`path\` only when a different root is needed.
+- Presentation: In assistant messages, show workspace-relative paths; use absolute paths only inside tool calls.
+- Tool schema overrides general path preferences-do not convert required absolute paths to relative.
+
+## Verification Checklist
+
+Before file/plan modifications:
+1. Am I using the actual available edit tool name (\`edit\`, \`patch\`, or \`apply_patch\`)?
+2. Am I using "todowrite" NOT "update_plan"?
+3. Is this tool in the approved list above?
+4. Am I following each tool's path requirements?
+
+If ANY answer is NO -> STOP and correct before proceeding.
+
+## Host Working Style
+
+**Communication:**
+- Send brief preambles (8-12 words) before tool calls, building on prior context
+- Provide progress updates during longer tasks
+
+**Execution:**
+- Keep working autonomously until query is fully resolved before yielding
+- Don't return to user with partial solutions
+
+**Code Approach:**
+- New projects: Be ambitious and creative
+- Existing codebases: Surgical precision - modify only what's requested unless explicitly instructed to do otherwise
+
+**Testing:**
+- If tests exist: Start specific to your changes, then broader validation
+
+## Advanced Tools
+
+**Task Tool (Sub-Agents):**
+- Use the Task tool (functions.task) to launch sub-agents
+- Check the Task tool description for current agent types and their capabilities
+- Useful for complex analysis, specialized workflows, or tasks requiring isolated context
+- The agent list is dynamically generated - refer to tool schema for available agents
+
+**Parallelization:**
+- When multiple independent tool calls are needed, use multi_tool_use.parallel to run them concurrently.
+- Reserve sequential calls for ordered or data-dependent steps.
+
+**MCP Tools:**
+- Model Context Protocol servers provide additional capabilities
+- MCP tools are prefixed: \`mcp__<server-name>__<tool-name>\`
+- Check your available tools for MCP integrations
+- Use when the tool's functionality matches your task needs
+
+## What Remains from Codex
+ 
+Sandbox policies, approval mechanisms, final answer formatting, git commit protocols, and file reference formats all follow Codex instructions. In approval policy "never", never request escalations.
+
+## Approvals & Safety
+- Assume workspace-write filesystem, network enabled, approval on-failure unless explicitly stated otherwise.
+- When a command fails due to sandboxing or permissions, retry with escalated permissions if allowed by policy, including a one-line justification.
+- Treat destructive commands (e.g., \`rm\`, \`git reset --hard\`) as requiring explicit user request or approval.
+- Never run \`git reset --hard\`, \`git checkout --\`, or force deletes unless the user explicitly asked for that exact action.
+- \`request_user_input\` is Plan-mode only; do not call it in Default mode.
 - When uncertain, prefer non-destructive verification first (e.g., confirm file existence with \`list\`, then delete with \`bash\`).`;