Oracle

Oracle

Use Claude Fable as a parallel judgment process. Keep one Claude session paired with the current Codex task, return to it with new evidence, and let Codex remain responsible for verification, writing, and execution.

Consult Oracle

1. Do enough first-party work to identify the real decision. Inspect relevant artifacts and separate facts from guesses.
2. Send a compact decision brief containing:
   • objective and why it matters;
   • constraints and irreversible choices;
   • evidence, attempts, and observed failures;
   • the decision or uncertainty Oracle should resolve;
   • only the new context since the prior consultation.
3. Run the bundled wrapper from the active working directory:

python3 <skill-directory>/scripts/oracle.py ask <<'EOF'
Objective: ...
Why it matters: ...
Constraints: ...
Evidence and attempts: ...
Decision needed: ...
New since our last exchange: ...
EOF

The wrapper uses CODEX_THREAD_ID by default. Outside Codex, set ORACLE_THREAD_KEY or pass --thread-key <stable-conversation-id>. Never invent a different key for a later turn in the same task.

4. Evaluate the advice against primary evidence. Oracle is an advisor, not an authority. Correct factual errors and reject suggestions that violate the user's intent or the repository's constraints.
5. Incorporate the useful judgment into the plan or implementation in Codex's own clear voice. Do not paste Oracle's raw memo to the user unless the user asks for it.

Maintain the Paired Session

• Let the wrapper create the first Fable session and persist its UUID. On every later consultation, use ask again; it resumes the stored session automatically.
• Treat follow-ups as deltas. State what changed, what failed, and which decision is now live. Do not resend the full history that Fable already has.
• Reconsult after material new evidence, a failed approach, a changed constraint, or a new decision fork. Do not ping Oracle merely to endorse a settled choice.
• Inspect the pairing with python3 <skill-directory>/scripts/oracle.py status.
• Never reset merely to get a different answer. If the stored Claude session is unavailable or its context is irreparably wrong, explain the continuity loss and use reset --force only with user approval.

Preserve Safety and Context Quality

• Remove secrets, credentials, private user data, and irrelevant logs from the brief.
• Give Oracle file paths only when their contents are safe to disclose to the locally authenticated Claude account.
• Keep Oracle read-only. The wrapper starts Claude in safe mode, supplies a strict empty MCP configuration, and exposes only Read, Glob, and Grep with non-interactive permission handling.
• Keep the stable system prompt, fable model alias, and xhigh effort default unless the user explicitly requests a change.
• If Claude is missing, unauthenticated, or returns an error, report that plainly and continue with Codex's best judgment when safe; do not silently create a replacement session.