-
-- All plans work across multiple personal machines and Dev Containers — - one subscription, all your devices. + All plans work across multiple personal machines — one subscription, + all your devices.
Already a subscriber?{" "} @@ -234,6 +240,34 @@ const PricingSection = () => { Manage your subscription
+ + {/* Rolling out for your team */} ++ Let's figure out if Pilot Shell is the right fit for your team and get everyone set up. +
+- Share AI assets across your team. Rules, skills, commands, and - agents — managed from a central Git repository and synced to every - project. -
-- {f.desc} -
-- Let's figure out if Pilot Shell is the right fit for your team and - get everyone set up. -
-- Master Claude Code — guides, workflows, and best practices -
-- {article.description} -
- - {/* Tags */} -No articles match your search. Try a different query or category.
-- Complete technical reference for Pilot Shell. Everything from - installation to hooks, MCP servers, and the full CLI. -
-
-
- {c.cmd}
-
- |
- - {c.desc} - | -
- Full command reference for the pilot binary at ~/.pilot/bin/pilot -
-
- The pilot binary manages
- sessions, worktrees, licensing, and context. Run{" "}
- pilot or{" "}
- ccp with no arguments to start
- Claude with Pilot enhancements. All commands support{" "}
- --json for structured output.
- Multiple sessions can run in parallel on the same project — each
- tracks its own worktree and context state independently.
-
- Slug format: The{" "}
- <slug> parameter for
- worktree commands is the plan filename without the date prefix and{" "}
- .md extension. For example,{" "}
-
- docs/plans/2026-02-22-add-auth.md
- {" "}
- → add-auth.
-
- Local web dashboard at localhost:41777 — monitor and manage your - sessions -
-- The Console runs locally as a Bun/Express server with a React web UI. - It's automatically started when you launch Pilot and stopped when all - sessions close. All data — memories, sessions, usage — is stored in a - local SQLite database. Nothing leaves your machine. -
- -- {item.desc} -
-- The Console sends real-time alerts via Server-Sent Events when - Claude needs your input or a significant phase completes. You don't - need to watch the terminal constantly — the Console notifies you. -
-- Settings tab:{" "} - Configure model selection per component — Planning (Opus), - Implementation (Sonnet), Verification (Sonnet), each sub-agent - independently. Enable the{" "} - Extended Context (1M) toggle - to use the 1M token context window across all models simultaneously.{" "} - - Requires Max 20x or Enterprise subscription. - -
-- Seamless continuation across auto-compaction cycles -
-- Claude Code reserves ~16.5% of the context window as a compaction - buffer, triggering auto-compaction at ~83.5% raw usage. Pilot hooks - intercept this cycle to preserve state — you never lose progress - mid-task. Multiple Pilot sessions can run in parallel on the same - project without interference. -
- - {/* Compaction cycle */} -
- {step.name}
-
- - {step.desc} -
-
- Pilot rescales the raw context usage to an{" "}
-
- effective 0–100% range
- {" "}
- so the status bar fills naturally to 100% right before compaction
- fires. A ▓ buffer indicator at
- the end of the bar shows the reserved zone. The context monitor
- warns at ~80% effective (informational) and ~90%+ effective
- (caution) — no confusing raw percentages.
-
- - Never rush due to context warnings. - {" "} - Context limits are not an emergency — auto-compaction preserves - everything and resumes seamlessly. Finish the current task with full - quality. The only thing that matters is the output, not the context - percentage. -
-- 15 hooks across 7 lifecycle events — fire automatically at every - stage -
-- Hooks are the enforcement layer. They run at each stage of Claude's - work cycle — automatically, without prompting. Blocking hooks can - reject an action or force a fix. Non-blocking hooks warn without - interrupting. Async hooks run in the background. -
- -
- {group.event}
-
-
- — {group.trigger}
-
-
- {hook.name}
-
-
- {hook.type}
-
- - {hook.desc} -
-- Closed loop:{" "} - When compaction fires,{" "} - PreCompact captures your - active plan, task list, and key decisions to persistent memory.{" "} - SessionStart restores - everything afterward — work continues exactly where it left off. No - progress lost, no manual intervention. -
-- Works with any existing project — no scaffolding required -
-
- $ {INSTALL_CMD}
-
-
-
- Run from any directory — local mode installs globally to{" "}
- ~/.pilot/ and{" "}
- ~/.claude/. After
- installation, cd into any
- project and run{" "}
-
- pilot
- {" "}
- or{" "}
-
- ccp
- {" "}
- to start. Dev Container mode should be run from inside the project
- directory.
-
{s.desc}
-- See{" "} - - releases - {" "} - for all available versions. Useful when a specific version is - known stable. -
-
- curl -fsSL .../uninstall.sh | bash
-
-
-
- Removes binary, plugin files, managed commands/rules, settings,
- and shell aliases. Your project's custom{" "}
- .claude/ files are
- preserved.
-
- Real-time diagnostics and go-to-definition, auto-installed and - configured -
-
- Language servers (LSP) give Claude real-time diagnostics, type
- information, and go-to-definition on every file edit. All three are
- auto-installed and configured via stdio transport — no manual setup.
- They work alongside the{" "}
- file_checker.py hook: hooks
- catch formatting and linting errors, LSP provides type-level
- intelligence.
-
{lsp.server}
- - {lsp.note} -
-
-
- Add custom language servers
- {" "}
- via .lsp.json in your
- project root. All servers use stdio transport and support
- auto-restart configuration.
-
- Capture non-obvious discoveries as reusable skills -
-
- When Pilot solves a non-obvious problem — a tricky debugging session,
- an undocumented API pattern, a workaround for a framework quirk —{" "}
-
- /learn
- {" "}
- extracts that knowledge into a reusable skill. Future sessions load
- and apply it automatically. Triggered automatically when relevant, or
- invoked manually after significant investigations.
-
-
- Skills are plain markdown files
- {" "}
- stored in .claude/skills/.
- They're loaded on-demand when relevant, created by{" "}
- /learn, and shareable across
- your team via the Teams dashboard. Skills
- follow a frontmatter format that describes when they apply.
-
- External context always available to every session -
-
- Five MCP servers are pre-configured and always available. They're
- lazy-loaded via ToolSearch to
- keep context lean — discovered and called on demand. Add your own in{" "}
- .mcp.json, then run{" "}
- /sync to generate documentation.
-
- {server.name}
-
-
- — {server.purpose}
-
- - {server.desc} -
-
- {server.example}
-
-
- Tool selection:{" "}
- Rules specify the preferred order — Probe CLI first for codebase
- questions, lib-docs for library API lookups, grep-mcp for production
- code examples, web-search for current information. The{" "}
- tool_redirect.py hook blocks
- the built-in WebSearch/WebFetch and redirects to these MCP
- alternatives.
-
- Opus where reasoning matters, Sonnet where speed and cost matter -
-- Pilot automatically routes each phase to the right model. Rather than - always using the most powerful (and most expensive) model, it applies - reasoning where reasoning has the highest impact — and uses fast, - cost-effective execution where a clear spec makes quality predictable. -
- - {/* Routing table */} -- {row.why} -
-
-
- Fully configurable
- {" "}
- via the Pilot Shell Console Settings tab (
- localhost:41777/#/settings
- ). Choose between Sonnet 4.6 and Opus 4.6 for the main session,
- each command, and each sub-agent independently. Enable the{" "}
- Extended Context (1M) toggle
- to switch all models to the 1M token context window simultaneously
- — useful for very large codebases. Requires Max 20x or Enterprise
- subscription.
-
- What you need before installing Pilot -
-- Pilot Shell installs on top of Claude Code. - If Claude Code is not already installed, the Pilot Shell installer will install it automatically - via the{" "} - - native installer - - . -
-- Pilot enhances Claude Code — it doesn't replace it. You need an - active Claude subscription. Solo developers, teams, and enterprise - organizations are all supported. -
-{tier.note}
-
- Pilot installs once and works across all your projects. Each
- project can have its own{" "}
- .claude/ rules and skills.
-
- - Dev Container option: - {" "} - A pre-configured isolated environment with all tools ready. No - system conflicts, works on any OS. -
-- Direct execution — no plan file, no approval gate -
-
- Quick mode is the default interaction model. Just describe your task
- and Pilot gets it done — no spec file, no approval step, no directory
- scaffolding. Zero overhead on simple tasks. All quality guardrails
- still apply — hooks, TDD, type checking — but nothing slows down the
- interaction. When you need a plan, use{" "}
-
- /spec
- {" "}
- — not Claude Code's built-in plan mode (Shift+Tab).
-
-
- When to use /spec instead:
- {" "}
- Use{" "}
-
- /spec
- {" "}
- for bug fixes (root cause investigation with test-before-fix),
- complex features that need a plan before implementation, or
- refactors with many interdependent changes.
-
- Production-tested best practices loaded into every session -
-
- Rules are loaded automatically at session start. They're not
- suggestions — they're enforced standards. Coding standards load
- conditionally based on the file type being edited, keeping context
- lean. Your project-level rules in{" "}
- .claude/rules/ are loaded
- alongside Pilot's built-ins and take precedence when they overlap.
-
{rule.file} —{" "}
- {rule.desc}
- | - Standard - | -- Activates On - | -- Coverage - | -
|---|---|---|
| - {s.standard} - | -- {s.activates} - | -- {s.coverage} - | -
- Custom rules:{" "}
- Create{" "}
- .claude/rules/my-rule.md{" "}
- in your project. Add{" "}
- paths: ["*.py"]{" "}
- frontmatter to activate only for specific file types. Run{" "}
- /sync to auto-discover
- patterns and generate project-specific rules for you.
-
-
- Monorepo support:
- {" "}
- Organize rules in nested subdirectories by product and team
- (e.g.{" "}
-
- .claude/rules/my-product/team-x/
-
- ). Team-level rules must use{" "}
- paths frontmatter to scope
- to the right files.{" "}
- /sync generates a{" "}
- README.md in your rules
- directory to document the structure.
-
- Plan, implement, and verify complex features with full automation -
-- - Replaces Claude Code's built-in plan mode (Shift+Tab). - {" "} - Best for complex features, refactoring tasks, or any work where you - want to review a plan before implementation begins. The structured - workflow prevents scope creep and ensures every task is tested and - verified before being marked complete. -
- - {/* Usage example */} -- The only manual step is{" "} - Approve. - Everything else runs automatically. The Verify → Implement feedback - loop repeats until all checks pass, then prompts for squash merge. -
-- Full exploration workflow for new functionality, refactoring, or - any work where architecture decisions matter. -
-- Investigation-first flow for targeted fixes. Finds the root cause - before touching any code. -
-
- When starting a{" "}
-
- /spec
- {" "}
- task, you can choose to work in an isolated git worktree. All
- implementation happens on a dedicated branch —{" "}
-
- main
- {" "}
- stays clean throughout. Pilot auto-stashes any uncommitted changes
- before creating the worktree and restores them after. After
- verification passes, choose to squash merge back. If the experiment
- doesn't work out, discard the worktree with no cleanup required.
-
- Learn your existing codebase and sync rules with it -
-
- Run{" "}
-
- /sync
- {" "}
- to explore your project structure, discover your conventions and
- undocumented patterns, update project documentation, and create new
- custom skills. This is how Pilot adapts
- to your project — not the other way around. Run it once initially,
- then any time your codebase changes significantly.
-
| - Phase - | -- Action - | -
|---|---|
| - {p.phase} - | -- {p.action} - | -
- Share rules, commands, and skills across your team via the Console - dashboard -
-- The Teams page in the Pilot Console lets your team share custom - assets — rules, skills, commands, and agents — via a private Git - repository. Browse assets, push local files, install team assets, and - manage versions — all from a visual dashboard. No CLI needed. -
- -{f.desc}
-- Open the Console dashboard and navigate to the Teams page. Click{" "} - Configure Repository to connect your team's Git repo. - Or use the CLI: -
-| - Type - | -- Source Path - | -- Purpose - | -
|---|---|---|
- {a.type}
- |
- - {a.path} - | -- {a.desc} - | -
- Assets install to the project's{" "}
- .claude/. Stays with the
- repo, visible to all contributors.
-
- Assets install to ~/.claude/{" "}
- and apply across all your projects on this machine.
-
- Assets are auto-versioned — each push creates v1, v2, v3… - Teammates install the latest version from the Teams dashboard. - Background sync keeps everything up to date when you open the - page. -
-`+e+`-`}ej.exports=MK;function MK(t,e,r){var n=r||{},s=n.env||process.env.NODE_ENV||"development",i=n.onerror;return function(a){var o,c,l;if(!a&&JA(e)){Fx("cannot 404 after headers sent");return}if(a?(l=qK(a),l===void 0?l=UK(e):o=zK(a),c=LK(a,l,s)):(l=404,c="Cannot "+t.method+" "+$K(FK(t))),Fx("default %s",l),a&&i&&jK(i,a,t,e),JA(e)){Fx("cannot %d after headers sent",l),t.socket&&t.socket.destroy();return}HK(t,e,l,o,c)}}function zK(t){if(!(!t.headers||typeof t.headers!="object")){for(var e=Object.create(null),r=Object.keys(t.headers),n=0;n