Skip to main content

Installation

Works with any existing project — no scaffolding required.

One-Command Installation

curl -fsSL https://raw.githubusercontent.com/maxritter/pilot-shell/main/install.sh | bash

Run from any directory — it installs globally to ~/.pilot/ and ~/.claude/. After installation, cd into any project and run pilot or ccp to start.

What the Installer Does

7 steps with progress tracking and rollback on failure:

StepTitleDescription
1PrerequisitesChecks Homebrew, Node.js, Python 3.12+, uv, git
2DependenciesInstalls Probe (code search), RTK (token optimizer), codebase-memory-mcp (code intelligence), playwright-cli, language servers
3Shell integrationAuto-configures bash, fish, and zsh with the pilot alias
4Config & Claude filesSets up .claude/ plugin — rules, commands, hooks, MCP servers
5VS Code extensionsInstalls recommended extensions for your language stack
6Automated updaterChecks for updates on launch with release notes and one-key upgrade
7Cross-platformWorks on macOS, Linux, Windows (WSL2)

Permissions Mode

Pilot Shell sets Claude Code to bypassPermissions mode by default. This enables the /spec workflow to run autonomously — planning, implementing, and verifying without pausing for permission prompts.

In Quick Mode (regular chat), you control the permission level. Press Shift+Tab to cycle through modes:

ModeBehavior
PlanClaude proposes changes, you approve before execution
Accept EditsFile edits auto-approved, other actions still prompt
NormalFine-grained permission prompts for each tool call

To set a persistent default, change defaultMode in ~/.claude/settings.json:

{
"permissions": {
"defaultMode": "acceptEdits"
}
}

The installer merges permissions additively — your customizations to allow, deny, ask, and defaultMode are preserved across updates.

Use /spec instead of plan mode

Claude Code's built-in plan mode (Shift+Tab → "plan") is unstructured — plans aren't saved as files, have no consistent format, and disappear when the session ends. Use /spec as a drop-in replacement: plans are saved as structured markdown in docs/plans/, persist across sessions, and drive a complete workflow with TDD and verification. See the spec workflow guide.

Dev Container

Pilot Shell works inside Dev Containers. Copy the .devcontainer folder from the Pilot Shell repository into your project, adapt it to your needs (base image, extensions, dependencies), and run the installer inside the container. The installer auto-detects the container environment and skips system-level dependencies like Homebrew.

Install Specific Version

export VERSION=7.5.7
curl -fsSL https://raw.githubusercontent.com/maxritter/pilot-shell/main/install.sh | bash

See releases for all available versions. Useful when a specific version is known stable.

Uninstall

curl -fsSL https://raw.githubusercontent.com/maxritter/pilot-shell/main/uninstall.sh | bash

Removes binary, plugin files, managed commands/rules, settings, and shell aliases. Your project's custom .claude/ files are preserved.