# Runbooks

Runbooks uses Claude Code agents to plan and execute coding tasks in isolated sandboxes. Describe what you want, review the generated spec, and let agents implement it.

## Why Runbooks

Individual AI tools like Claude Code are powerful but create challenges at team scale: conversations disappear when you close the session, each developer gets different solutions to the same problem, and implementation knowledge stays siloed.

Runbooks solves this with three capabilities:

**Multiplayer AI**: Multiple developers collaborate in shared sessions. Experienced AI engineers guide others on using better prompts, teams align on approaches together, and everyone sees the AI's reasoning. No more inconsistent patterns from isolated AI conversations.

**Persistent knowledge**: Every solution becomes an organizational asset. Context files teach agents your codebase patterns. Successful runbooks become templates that capture proven workflows. New team members leverage accumulated knowledge immediately.

**Spec-driven execution**: Review and approve plans before any code changes. Step-by-step execution with clear milestones replaces ad-hoc prompting. Standardized templates ensure consistent approaches across teams.

## Quick start

1. [Create your first Runbook](https://docs.aviator.co/runbooks/getting-started)
2. Review and refine the generated plan
3. Execute steps and merge the resulting PRs

## How it works

**Planning**: Describe your task in the chat interface. Agents analyze your codebase, gather context, and generate a step-by-step plan.

**Execution**: Run the plan [step-by-step](https://docs.aviator.co/runbooks/how-to-guides/step-by-step-execution) with review at each stage, or use [one-shot mode](https://docs.aviator.co/runbooks/concepts/one-shot-mode) for simpler tasks.

**Collaboration**: [Invite team members](https://docs.aviator.co/runbooks/concepts/collaborating-with-the-team) to review plans, provide feedback, and assign steps.

## Sandboxes

Agents execute in isolated environments with your codebase:

* [Cloud sandboxes](https://docs.aviator.co/runbooks/concepts/cloud-sandboxes) - Managed by Aviator, no setup required
* [SSH sandboxes](https://docs.aviator.co/runbooks/concepts/ssh-sandboxes) - Self-hosted on your infrastructure

## Use cases

* [Code migrations](https://docs.aviator.co/runbooks/concepts/use-cases/code-migrations) - Framework upgrades, API changes
* [Bug fixes](https://docs.aviator.co/runbooks/concepts/use-cases/bug-fixes) - Investigate and fix issues
* [Refactoring](https://docs.aviator.co/runbooks/concepts/use-cases/code-refactoring) - Improve code structure
* [Test coverage](https://docs.aviator.co/runbooks/concepts/use-cases/improving-code-coverage) - Add missing tests
* [Flaky tests](https://docs.aviator.co/runbooks/concepts/use-cases/flaky-test-resolution) - Fix unreliable tests
* [Build optimization](https://docs.aviator.co/runbooks/concepts/use-cases/improve-build-times) - Speed up CI

## Configuration

* [Context files](https://docs.aviator.co/runbooks/how-to-guides/context-management) - Help agents understand your codebase
* [MCP servers](https://docs.aviator.co/runbooks/how-to-guides/mcp-servers) - Add custom tool integrations
* [Tool permissions](https://docs.aviator.co/runbooks/how-to-guides/claude-code-tools) - Control agent capabilities
* [Personas](https://docs.aviator.co/runbooks/how-to-guides/persona-management) - Customize agent behavior
* [Templates](https://docs.aviator.co/runbooks/concepts/templates) - Reuse runbooks across tasks

## Prerequisites

* GitHub account with repository access
* Runbooks access ([cloud](https://app.aviator.co) or [on-premise](https://docs.aviator.co/manage/on-premise-installation))

{% embed url="<https://youtu.be/AHV-T6t1ulk>" %}