Pilot Shell CLI
A ready harness for Claude Code and Codex: spec-driven development, TDD, memory between sessions, quality gates and human checkpoints
- 2,143 ★ on the repository
- Last commit
Extended access
Why this level
- Changes the agent config and adds sub-agents and rules
- Runs checks and commands as part of the process
Install
- Works in
Manual install
curl -fsSL https://raw.githubusercontent.com/maxritter/pilot-shell/main/install.sh | bashBack up the agent config before installing.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Changes the agent config and adds sub-agents and rules
- Runs checks and commands as part of the process
This is third-party code. Review the repository files before installing.
What it does
The installer places a set of rules, sub-agents, skills and settings tuned for engineering work into the Claude Code and Codex config. It sets up a spec-driven process with task breakdown, tests and quality checks before moving to the next step. Memory between sessions keeps project context, and checkpoints require a human at important points. Settings are merged with yours rather than overwritten, and there is a separate uninstall script.
Who it is for. For developers who want to run serious projects in Claude Code or Codex under a strict process.
Good fit when
- You need a repeatable spec-driven development process
- You want TDD and quality gates inside the agent
- You need project memory between sessions
Not a fit when
- You need a quick one-off edit without a process
- You do not use Claude Code or Codex
Example request
Start a new task with the Pilot Shell process: spec first, then tests, then implementationLimitations
The installer changes the agent config, so back up the config directory and settings file before installing, as the README advises. The underlying agent still calls Anthropic or OpenAI models, whose availability from Russia should be checked separately.
How to disable. Run uninstall.sh from the repository; there are flags to also remove added tools and data.
FAQ
Will the installer wipe my settings?
Claude settings are three-way merged, but the README advises backing up the config directory and settings file first.
Which agents does it support?
Claude Code and Codex.
Discussion
No questions or reviews yet.
Related
CLI toolsA set of Claude Code utilities: background skills, expert agents, slash commands and prompt templates for development
A starter kit for Claude Code: a CLAUDE.md memory-bank template with ready hooks, subagents and skills you copy into your project
Hooks and skills make Claude Code plan before coding, test before shipping and escalate when it is not confident.
A ready-made Claude Code setup: agents, slash commands, skills, safety hooks, rules and MCP connections in one install
The Darkroom team standards, skills, checks and hooks for Claude Code and Codex, installed with one command.
A plugin that turns Claude Code into a 16 agent team: documentation first planning, TDD and 9 pre-merge quality gates.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Pilot Shell (this card) | no | 2,143 | |
| The Agentic Startup | no | 580 | claude Code plugins for spec-driven development |
| FableCodex | no | 437 | a Codex plugin with an evidence-backed goal ledger and a findings gate |
| AI PRD Workflow | no | 310 | eleven skills take an agent from an idea to verified code through a |
README in short
The README describes Pilot Shell as a context-engineering harness for Claude Code and Codex. Installation is a single script with version selection, an uninstall script and advice on backing up the config. It lists the delivered parts: rules, sub-agents, a three-way merged settings file, plus autonomy and skill-routing benchmarks. The approach centers on spec-driven development, TDD and quality gates.