shelbi wizard

shelbi wizard [OPTIONS]

shelbi wizard is the explicit interactive entry point for Shelbi's first project setup. It inspects the current Git checkout and machine, prints the preflight results, and presents one setup card:

Enter launch    c customize    q quit

Press Enter to create the detected plan and launch the dashboard. Press c to edit the prefilled project, repository, branch, remote, runner, orchestrator, and issue-tracker values. Press q, Esc, or Ctrl+C to leave without project state.

Creating the project also installs a Shelbi pre-commit hook in the repo and prints a one-time disclosure. The hook blocks commits to the default branch only from Shelbi's agent sessions, never from your own shell, and it leaves a user-authored hook untouched. Remove it with shelbi guard uninstall.

If both Claude Code and Codex are detected, the wizard first asks Which agent?. If the current directory is not a Git repository, it first asks permission to run git init -b main. A missing runner prerequisite stops setup before the card and prints an install-and-retry message.

The wizard also asks where the project's issues should live: GitHub Issues (a card is a GitHub issue your team can see and file) or File system (private markdown on this machine). GitHub is pre-selected, with the owner/repo pre-filled, when the origin remote is a GitHub repo; otherwise File system is the default. Choosing GitHub preflights gh (installed, authenticated, Issues enabled, and push access for label creation) before anything is written, and on a failure explains the fix and offers to retry or fall back to File system. The chosen backend shows on the setup card and is written as an issue_tracker: block in the project config. See shelbi init for the full behavior and shelbi issue-store migrate to move an existing board between backends.

The command is idempotent at the project-registration level. If any project is already registered, it exits quietly, without creating another one or opening the dashboard. Use shelbi project add to run the shared setup flow for an additional project.

wizard honors the global --root <PATH> (the Shelbi state directory). The global -p and -y flags parse but have no effect here: the card is always interactive. For an unattended setup use shelbi init -y.

Examples

Run setup explicitly from the repository you want Shelbi to manage:

cd ~/code/myapp
shelbi wizard

For automation, use the non-interactive detected-plan path instead:

shelbi init -y --runner codex

See also

• Set up your first project for every happy-path and edge-path screen.
• shelbi init for scriptable setup and config pick-up.
• shelbi project for additional projects.