병렬 AI 코딩 에이전트 관리를 위한 로컬 UI

Manage 10 features at once — isolated branches, automatic commits, CI watching, and PRs — from a dashboard or the terminal. Quick Start · How It Works · Features · Trust & Safety · FAQ 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. shep feat new "add stripe payments" --push --pr shep feat new "add dark mode toggle" --push --pr shep feat new "fix login redirect bug" --push --pr # Three agents running in parallel. Zero branch conflicts. You monitor from one place. - Node.js 22+ and npm (or install via nvm ) - Git and GitHub CLI ( gh ) — install guide - An AI coding agent, authenticated and ready: - Claude Code: claude · Cursor CLI:cursor · Gemini CLI:gemini - If prompted to log in, complete auth first — Shep can't authenticate on your behalf. - Claude Code: Sandbox mode note: Some agents restrict network access by default. If operations like npm install fail, configure allowed hosts in your agent's settings or disable sandbox for Shep features. See Agent Permissions. # Try it instantly — no install needed npx @shepai/cli # Or install globally npm i -g @shepai/cli # Start Shep — opens the web dashboard at localhost:4050 shep cd ~/projects/my-app # Any git repo. Shep uses the repo you're in. shep feat new "add a /health endpoint that returns uptime and version" --push --pr # Shep creates a worktree, runs your agent, commits, pushes, and opens a PR. Not in a git repo? Shep initializes one for you — git init , creates a branch, and starts working. Or use the dashboard — describe what you need, configure automation, and hit create: shep feat new "add stripe payments" --push --pr shep feat new "add dark mode toggle" --push --pr shep feat new "refactor auth middleware" --push --pr # All three run simultaneously in the same repo. Each in its own worktree. Launch from CLI or dashboard — monitor everything in one place. Open any feature in your IDE, terminal, or file manager with one click: Or work across multiple repos: shep feat new "add payments" --repo ~/projects/backend --push --pr shep feat new "add checkout UI" --repo ~/projects/frontend --push --pr Manage multiple repos from one dashboard. Start a local dev server per feature, chat with Shep for questions or HTML previews — all without leaving the UI: The default flow is simple: prompt → implement → commit → push → PR. You describe Agent codes Shep commits Shep pushes Shep opens a feature → in a worktree → the changes → to remote → a PR Shep creates an isolated git worktree, hands your prompt to the agent, and handles everything after: committing, pushing, and opening a PR. If CI fails, Shep reads the logs, fixes the issue, and retries (configurable). Every step of the pipeline is configurable. Turn things on or off per feature or set defaults: | Flag | What it does | Default | |---|---|---| --push | Auto-push after implementation | off | --pr | Auto-create PR after push | off | --fast | Skip spec-driven phases, go straight to coding | on | --allow-merge | Auto-merge the PR after CI passes | off | --allow-all | Enable all automations | off | --model | Choose which AI model to use | agent default | --attach | Attach reference files for context | — | Use shep settings workflow to set your defaults so you don't repeat flags. For complex features, enable the full structured pipeline with requirements, research, and planning phases: # Disable --fast to get the full pipeline shep feat new "redesign the payment system" --no-fast --push --pr This adds approval gates where Shep pauses for your review: Prompt → Requirements → Research → Plan → Implement → Commit → PR ▲ ▲ ▲ Gate 1: PRD Gate 2: Plan Gate 3: Merge Each gate produces a YAML artifact you can read, edit, and approve before the agent continues. Use --allow-prd and --allow-plan to auto-approve individual gates, or keep them manual for full control. Run multiple features at once. Each gets its own git worktree — isolated branch, isolated files, zero conflicts. Monitor all of them from one dashboard. One command: shep feat new "do X" --push --pr . Agent implements, Shep commits, pushes, opens a PR. Done. Use Claude Code, Cursor CLI, or Gemini CLI. Swap per feature, per repo, anytime. If it runs in a terminal, Shep can orchestrate it. Two ways to manage everything. The dashboard at localhost:4050 shows a visual graph of all repos and features with real-time status, diff review, and interactive chat. The CLI gives you the same control from the terminal. Shep watches your CI pipeline after push. If it fails, the agent reads the logs, diagnoses the problem, and pushes a fix