![Shep](docs/screenshots/shep-card.jpg)

Shep

### Run multiple AI agents in parallel. Each in its own worktree. _Manage 10 features at once — isolated branches, automatic commits, CI watching, and PRs — from a dashboard or the terminal._ [![CI](https://github.com/shep-ai/shep/actions/workflows/ci.yml/badge.svg)](https://github.com/shep-ai/shep/actions/workflows/ci.yml) [![npm version](https://img.shields.io/npm/v/@shepai/cli.svg?color=cb3837&logo=npm)](https://www.npmjs.com/package/@shepai/cli) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![Discord](https://img.shields.io/discord/1473730318576914617?color=5865F2&logo=discord&logoColor=white)](https://discord.gg/ES6tdVFfur) [Quick Start](#quick-start) · [How It Works](#how-it-works) · [Features](#features) · [Trust & Safety](#trust--safety) · [FAQ](#faq)
Shep — Parallel AI Agent Sessions

--- ## Why Shep? You're already using AI coding agents. The problem isn't the coding — it's everything around it. Switching branches. Stashing changes. Watching CI. Assembling PRs. Losing context when you juggle three things at once. One agent session is fine. Five is chaos. **Shep gives each feature its own isolated world** — a git worktree, a branch, an agent session — and handles the boring parts: committing, pushing, opening PRs, watching CI, and fixing failures. You manage it all from one dashboard or the CLI. ```bash shep feat new "add stripe payments" --push --pr shep feat new "add dark mode toggle" --push --p

Agents

shep