Documentation

A reactive PR inbox in your terminal.

Instead of refreshing GitHub in a browser, events flow to you. New comments, CI failures, and review requests surface as they land, with read/unread tracking — the way an email client surfaces mail. Each task becomes a workspace: a git worktree plus an embedded terminal running Claude Code, Codex, Cursor, or a plain shell.

Inside those sessions, snippet workflows turn the agent instructions you repeat every day into one fast action. Recent remembers what you reuse, and each workspace’s ]N badge tracks up to 12 recently distinct workflows.

lazybox is source-agnostic. GitHub and Linear today, with an optional Slack mirror — all in the same inbox, with the same keys.

Start with the core workflows

The Core workflows path follows real tasks rather than teaching isolated controls. It shows how to:

• open an agent, shell, and editor in the correct task checkout without managing paths or worktrees;
• trust stable, accurate agent status and jump directly to the workspace that needs input or has failing CI;
• reuse recent snippets, read the per-workspace ]N progress cue, and create a new snippet safely through Ask Lazybox;
• carry a live issue session into its implementation PR, then complete the GitHub workflow inside the TUI;
• return to the same live tmux-backed session after restarting lazybox;
• keep 10 repositories and 15 concurrent sessions controlled from one inbox;
• choose among Claude Code, Codex, Cursor, or a custom CLI while retaining a one-action default; and
• learn leader shortcuts through which-key and generated, remap-aware help.

Start with the Quickstart if lazybox is not installed yet, then take the core path before diving into reference material.

Start from the issue. Keep your session in the PR.

Put an agent to work before a pull request exists. When the closing PR arrives, lazybox carries the live terminal, worktree, edits, and activity into the PR workspace — no restart or manual handoff. Follow the issue-to-PR workflow.

Pre-1.0, early-adopter dev mode

lazybox is daily-driven on macOS; Linux runs the same code paths but is less tested. Prebuilt binaries ship via a Homebrew tap and a curl | sh installer (see the Quickstart), or build from source. Expect sharp edges; logs land in /tmp/lazybox.log.

Who it’s for

Developers who live across several open pull requests and want the work to come to them — and who like driving an agent (Claude Code, Codex, Cursor) inside an isolated worktree per task.

Find your way around

The documentation is split into four sections, following the Diátaxis framework:

• Tutorials — learning-oriented. Start here if you are new. The Quickstart gets you from clone to a live terminal session, a reusable workflow, and a two-workspace broadcast in about five minutes; the Core workflows then connects that session to the complete task, Git, agent, and GitHub lifecycle.
• How-to guides — task-oriented recipes: add a repo, run an agent per workspace, use and create snippet workflows, keep that session when its issue becomes a PR, orchestrate a fleet of agents, configure per-repo env and mounts, drive a remote daemon over SSH, mirror to Slack.
• Reference — exhaustive, dry facts: the CLI, every keybinding, and the full configuration schema.
• Explanation — the “why”: the mental model, how lazybox compares to other parallel-agent tools, and the architecture.

Fastest path

brew tap AntoineToussaint/lazybox && brew trust AntoineToussaint/lazybox && brew install lazybox
gh auth login   # if you haven't already
lazybox

Then follow the Quickstart for what you see on first launch — including sending and repeating a built-in workflow. It also covers the curl | sh and build-from-source paths.