DIRECTOR MODE LITE / INSTALL
Install into a repository you control. The default path adds no hooks or hidden gates and does not change permissions; director-open remains a separate explicit trusted-workspace choice.
v2.1.0 / guidance-first / zero-hook default / verified 2026.07.27
The shell installer provides the complete project-local surface. The two core skills keep bundled guide, relay, and doctor fallbacks in a plugin-only install.
| SURFACE | NATIVE HOME | SHARED METHOD | SESSION BOUNDARY |
|---|---|---|---|
| Claude Code | CLAUDE.md / Claude assets | Director Brief + skills | Native resume in Claude |
| Codex CLI | AGENTS.md / Codex assets | Director Brief + skills | Native resume in Codex |
| Grok Build | .grok agents / compatible assets | Director Brief + skills | Native resume in Grok |
| Cross-provider relay | .director-mode/ or bundled fallback | director-mode + session-relay | New receiver-native session |
Review the source, choose an explicit target repository, and run the v2.1.0 all-CLI installer. It supplies 35 skills and 14 agent adapters per CLI.
git clone https://github.com/claude-world/director-mode-lite.git
cd director-mode-lite
./install.sh --cli all --hooks none /path/to/projectPlugin-only keeps director-mode and session-relay functional through bundled guide, relay, and read-only doctor fallbacks. Use the shell installer for the complete generated surface.
Run director-doctor, validate the relay JSON, and compare captured branch, HEAD, status, and diff evidence with the live worktree.
.director-mode/bin/director-doctor --json --no-probe
.director-mode/bin/director-relay --help
.director-mode/bin/director-relay validate
.director-mode/bin/director-relay status --json
.director-mode/bin/director-relay show
.director-mode/bin/director-relay continue --to codex
# Plugin-portable core Skills
director-mode
session-relayPackets default to review_status: unreviewed. doctor, validate, and status do not mark a packet reviewed and never change hooks, permissions, approvals, or sandbox settings.
Use native resume inside one provider. Use a relay when another provider or a fresh session has a bounded advantage.
BRIEF + CHECKRecord the goal and verified state, then run repository-native checks.
CREATE + STATUSCreate a v2 packet; add --parent on a later hop, validate it, and inspect live drift with status --json.
NEW SESSIONReview the packet explicitly, then start a new receiver-native session for a cross-provider handoff.
Presence checks prove assets are available. They do not prove packet review, runtime authority, or code correctness.
Review the installer and commit or back up the explicit target before running it.
Use zero hooks by default; add only a hook whose event, input, output, timeout, and failure behavior you understand.
Run director-doctor for a read-only inventory of CLI availability, assets, and effective hook locations.
For older installs, use --update --hooks none to remove Director-owned registrations while preserving custom or modified hooks.
Choose director-open separately in a trusted workspace; no skill or relay command invokes it implicitly.
The update command removes Director Mode registrations and unmodified owned hook assets. It preserves unrelated, custom, and modified hooks; inspect the diff afterward.
./install.sh --update --cli all --hooks none /path/to/project
git -C /path/to/project status --short
git -C /path/to/project diff -- .Resume natively with the same provider; use an inspected, explicitly reviewed packet to begin a new session with another CLI.