Setup

ThisCodex Setup Skill

Generated through the mandatory /prompt workflow:

/prompt --batch GPT-5.5 상세 ThisCodex setup skill: create a step-by-step installer-facing skill that invokes thiscodex init, keeps guided onboarding distinct from placement, uses tmux only, explains YOLO safely, and asks progress_report_cadence.

Goal

Guide thiscodex setup / thiscodex init without inventing paths or silently skipping decisions.

Required Flow

1. Run thiscodex init for guided onboarding.
2. Confirm repo root, workspace, BOT_WD, and Discord state dir before generating

aliases.

1. Use tmux for the daemon/TUI split. Do not use cmux for this flow.
2. Present safe mode first. Offer YOLO only as an explicit opt-in using the

bridge contract and operator-controlled sentinel.

1. Ask progress_report_cadence: per_task, 1m, 3m, 5m, off, or

custom. per_task means a meaningful subtask or milestone completion, not every raw model turn boundary.

1. Wire and trust the Codex hooks. Ensure ~/.codex/hooks.json has the

SessionStart helper (hooks/bot-session-init.sh — injects roster + active-meeting state + rules/INDEX.md) and the active-meeting Stop reread (hooks/meeting-stop-reread.sh — no flag; it auto-detects a bot session from the environment). Then run /hooks in the Codex TUI and approve them: a wired Codex hook does NOT run until trusted (a trusted_hash is written to ~/.codex/config.toml). Verify a Stop trusted_hash is present in ~/.codex/config.toml — if absent, the meeting reread is silently inactive. (See README §3.6.) This trust step is Codex-specific; do not skip it or report the bot ready without it.

1. Read docs/RECENT-CHANGES.md and apply anything not yet reflected — it is

the newest-first digest of contract/behavior changes a fresh install must adopt (e.g. the Stop-hook output contract + the trust requirement above).

1. When aliases are generated, tell the user to source the generated alias

script/block; only add it to a shell rc file if they explicitly want it permanent.

1. Finish with thiscodex doctor.

Subcommands

| When to use | Call | |---|---| | Start guided ThisCodex setup | /setup or /setup init — launches the interactive onboarding wizard. Covers repo root, workspace, BOT_WD, Discord state directory, safe/YOLO mode selection, progress reporting cadence, and Codex hook setup. | | View setup progress summary | /setup status — shows what's been configured so far (repo, workspace, aliases generated, hooks wired, doctor check done). | | Run setup verification | /setup doctor — verifies all paths exist, Discord MCP is wired, ~/.codex/config.toml is readable, hook trust hashes are present, and tmux/Python dependencies are installed. | | Re-wire Codex hooks | /setup hooks — re-runs the SessionStart + meeting-Stop hook wiring and trust approval in the Codex TUI. Use this if hooks were unwired or the trust hash was removed. | | Generate shell aliases | /setup aliases — generates convenience shell aliases (thiscodex_run, thiscodex_tui, thiscodex_connect, etc.) and shows you how to source or permanently add them. | | View guide documents | /setup guide — prints paths to SETUP.md, SETUP-BEGINNER.md, and RECENT-CHANGES.md for reference during setup. |

Guardrails

• Placement is not onboarding.
• Non-interactive mode is for CI or diagnosis only.
• Missing decisions stop with the next command instead of using guessed values.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: treylom
• Source: treylom/ThisCodex
• License: MIT

Install and usage instructions live in the source repository linked above.