SETUP / ALL CLI
Install the complete three-CLI runtime—or use only the plugin.
The shell installer prepares Claude Code, Codex CLI, and Grok Build adapters plus project guidance, director-relay, director-open, and the read-only director-doctor. A plugin-only install still keeps the two core Skills functional through bundled fallbacks.
The default is --hooks none and the installer does not change persistent permissions, approval mode, sandbox settings, or hook trust. director-open grok 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 grok TWO CORE SKILLS / FALLBACKS
Start with two core Skills.
The shared contract stays small; Grok Build 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 use Grok inspection and repository evidence before choosing an implementation.
- 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, installed CLIs, native agent and shared Skill counts, and known Grok Build, Claude Code, and Codex CLI hook surfaces without repairing or mutating them.
RUNTIME / GROK BUILD
Map v2.1 onto native Grok Build surfaces.
Director Mode supplies portable guidance and state; Grok keeps ownership of discovery, permissions, sandboxing, agents, Workflows, and history.
DIRECTOR-HANDOFF/V2 / STATUS DRIFT
Resume Grok natively; relay across providers.
Use grok --continue or grok --resume when the provider does not change. A Claude Code↔Codex CLI↔Grok Build handoff always opens a new native receiving session; the 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.
Grok-first rule: native Grok Build history uses --continue or --resume. grok import is a useful Claude Code→Grok Build shortcut, but a Director packet remains the portable format when the route may later include Codex CLI or return to Claude Code.
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 Grok 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 Grok authority on native Grok surfaces.
- Default installation uses --hooks none and registers zero Director Mode hooks.
- Installing or selecting either core Skill does not rewrite permissions, approval mode, sandbox, network access, or hook trust.
- director-open grok 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.
- Audit Claude hooks too: Grok can inherit compatible Claude hooks even when .grok/hooks is empty.