Oracle + PackX Handoff Field Guide

Spend Codex on implementation, not on reading 500K tokens of context.

Original source pages and recordings require authorized access. The full article text here is public.

Spend Codex on implementation, not on reading 500K tokens of context.

Use this when the hard part is broad context synthesis and Codex should bring back an implementation-ready plan.

Use Oracle with a codebase.

Workshop transcript

Choose the right mechanism

Mechanism Use when Agent responsibility Artifact
PackX preview Before any large handoff Verify files and token estimate ~/.oracle/bundles/<slug>.txt
Browser Oracle Expensive broad reasoning Upload bundle to ChatGPT browser mode ~/.oracle/sessions/<slug>/output.log
Codex implementation After plan returns Patch, test, verify, summarize .notes/<task>/verification.md

Agent-ready prompt

Use Oracle + PackX for this broad codebase question.
Preview the bundle first.
Build a markdown bundle under ~/.oracle/bundles/<slug>.txt.
Run Oracle in browser mode with a 3-5 word slug.
Read the full Oracle output, write a local plan, implement the first shippable slice, and verify locally before asking Oracle again.

Applied stories

Stale test-suite migration

Role: Senior engineer

Hundreds of tests need classification into keep, rewrite, browser QA, or delete.

Agent brief: Pack tests, source owners, failures, and CI logs; ask Oracle for a migration plan; Codex implements one bucket at a time.

Done when:

  • bundle path
  • Oracle plan
  • migration goal file
  • first verified slice

Architecture consistency audit

Role: Tech lead

A repo has several competing patterns and nobody knows the current owner path.

Agent brief: Bundle current source and docs, ask Oracle for live owner paths and invariants, then patch docs and tests locally.

Done when:

  • owner map
  • invariant list
  • docs patch
  • verification commands

Tips and gotchas

  • Preview before packing so the handoff is intentional.
  • Keep Oracle text-only; the local agent owns artifacts and commits.
  • Do not ask Oracle again on the same topic until you implemented, verified, hit a blocker, or narrowed scope.
  • Preserve the session slug and output path for auditability.

References

Source references