COMMUNITY COMPANION / CODEX-FIRST
Direct Codex without friction.
Director Mode Lite v2.1 centers two core Skills—director-mode and session-relay—then adapts the same lightweight operating contract to Codex, Claude Code, and Grok Build.
SETUP / ALL CLI
Install the complete three-CLI runtime—or use only the plugin.
The shell installer adds project guidance, native adapters, director-relay, director-open, and the read-only director-doctor. A plugin-only install still keeps the two core Skills functional through their bundled guide, relay, and doctor fallbacks.
The default is --hooks none and the installer does not change persistent permissions, approvals, sandbox settings, or hook trust. director-open codex is a separate, explicit launch choice for a trusted workspace.- $
git clone https://github.com/claude-world/director-mode-lite.git - $
cd director-mode-lite - $
./install.sh --cli all --hooks none /path/to/project - $
cd /path/to/project - $
.director-mode/bin/director-doctor --json --no-probe - $
.director-mode/bin/director-relay status --json - $
.director-mode/bin/director-open --print codex
TWO CORE SKILLS / FALLBACKS
Start with two core Skills.
Everything else is an adapter or optional workflow. Codex remains the runtime of record for this companion.
- 01 / DIRECT
director-mode frames the work
State outcome, context, constraints, evidence, and the next decision; then let Codex inspect the real repository and choose an appropriate approach.
- 02 / RELAY
session-relay carries state
Create or receive a privacy-bounded director-handoff/v2 packet when work should cross a provider or survive a context boundary.
- 03 / FALLBACK
Plugin-only remains useful
Without a .director-mode runtime, the Skills fall back to bundled references/GUIDANCE.md, scripts/director-relay.py, and scripts/director-doctor.py.
- 04 / DIAGNOSE
director-doctor only observes
It reports runtime assets, CLI discovery, agent and Skill counts, and known hook registrations; it never repairs files or changes permissions.
RUNTIME / CODEX
Map v2.1 onto native Codex surfaces.
Director Mode supplies portable guidance and state; Codex keeps ownership of history, approvals, sandboxing, subagents, and execution.
DIRECTOR-HANDOFF/V2 / STATUS DRIFT
Resume Codex natively; relay across providers.
Stay with Codex resume or codex exec resume when the provider does not change. A Claude↔Codex↔Grok handoff always opens a new native receiving session; a source vendor session ID is metadata, never a portable resume token.
Protocol director-handoff/v2 records root_id, parent_id, hop, and route for multi-hop lineage while continuing to validate v1 packets.
Before takeover, director-relay status --json compares the captured branch, HEAD, Git status, and diff statistics with the live worktree. It reports status drift without blocking continuation.
Codex-first rule: use codex resume --last, codex resume <session-id>, or codex exec resume for Codex history; use a packet and a new native session when crossing providers.
Packets default to review_status: unreviewed. --reviewed only records that the user-supplied summary and captured path metadata were reviewed before sharing; it does not mean GPT World or the receiving CLI reviewed the packet.
BOUNDARY / ADVICE ONLY
Zero default hooks; no permission mutation.
Director Mode Lite stays guidance-first and leaves Codex authority on native Codex surfaces.
- Default installation uses --hooks none and registers zero Director Mode hooks.
- Installing or selecting either core Skill does not rewrite permissions, approval policy, sandbox, network access, or hook trust.
- director-open codex is an explicit launcher, not a persistent settings migration or a hook-based permission emulator.
- director-doctor is read-only; status drift is evidence, not a gate.
- Organization policy and pre-existing global hooks can still override a launch—inspect the active CODEX_HOME.