Overview

What Roscoe is

Roscoe is a local operator layer for Codex and Claude CLI. It does not replace your local tooling. It sits above that tooling and keeps lane state, the project brief, runtime defaults, and operator interventions coherent while work is in flight.

What Roscoe writes locally

Project contract: .roscoe/project.jsonInstall: npm install -g @roscoesh/cliLaunch: roscoe

Project brief

Intent, definition of done, proof expectations, provider split, approval mode, and runtime defaults are persisted under .roscoe/project.json.

Named worktrees

Task lanes can reuse isolated worktrees so parallel implementation runs do not collide in the main checkout.

Notification settings

Phone number and SMS enablement are optional. Roscoe remains fully usable from the TUI without them.

Read this docs site by operator task

The docs are organized by the real path an operator takes through the product, not by internal code modules.

Install & Run

Set up the CLI and start on the correct screen.

Home Screen

Choose the next workflow, verify providers, tune Roscoe defaults, and configure channels.

Onboarding

Create or refresh the project contract Roscoe will use later.

Lane Setup

Choose the repo, brief, provider, and worktree before launch.

Live Lanes

Operate active sessions, review drafts, and intervene when needed.

Runtime Controls

Retune provider split, governance, and proof posture at the project level.

Operating model

• Roscoe is local-first.
• The TUI is the default operator surface.
• Onboarding defines the contract; live lanes enforce it.
• The CLI stays small and is mainly for direct entry, scripting, and worktree management.