explaingit

clipboardhealth/groundcrew

Analysis updated 2026-06-24

31TypeScriptAudience · developerComplexity · 4/5Setup · moderate

TLDR

CLI from ClipboardHealth that polls Linear tickets, spins a fresh git worktree per ticket, and runs Claude or Codex agents in sandboxed parallel sessions.

Mindmap

mindmap
  root((groundcrew))
    Inputs
      Linear tickets
      crew config ts
      Linear API key
    Outputs
      Git worktrees
      Agent runs
      PR ready code
    Use Cases
      Parallel ticket agents
      Sandboxed Claude
      Backlog automation
    Tech Stack
      TypeScript
      Docker
      Safehouse
      Linear API
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Run multiple Claude or Codex agents in parallel on different Linear tickets without merge conflicts.

USE CASE 2

Auto pick tickets from a Linear project by label and blocker status, then launch a coding agent per ticket.

USE CASE 3

Sandbox each agent with Safehouse on macOS or Docker on Linux to keep host writes contained.

USE CASE 4

Throttle in-progress agents by a configurable cap so model usage and infra stay bounded.

What is it built with?

TypeScriptDockerLinearClaudeCodex

How does it compare?

clipboardhealth/groundcrewjavlonbek1233/amaliy-ish-7javlonbek1233/axon
Stars313131
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderateeasyeasy
Complexity4/51/51/5
Audiencedevelopervibe codervibe coder

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Needs a Linear API key, sandbox tool installed per OS, and a crew config ts listing every repo before crew setup repos clones them.

In plain English

Groundcrew is a command-line tool from ClipboardHealth that connects your Linear ticket backlog to AI coding agents. The basic loop is: it polls a Linear project, picks up tickets that match its rules, creates a fresh git worktree for each one, and launches an agent like Claude or Codex inside that worktree to do the work. Because each ticket lives in its own worktree, several agents can run at the same time without overwriting each other's changes. The default posture is local-first sandboxing. On macOS the agents run under a tool called Safehouse, on Linux or WSL they run inside Docker Sandboxes, and there is an explicit none mode for users who want to skip isolation, though the built-in doctor command warns when that is configured. Out of the box the tool ships with definitions for the claude and codex CLIs, and you can drop a custom CLI definition into the config file to add more. Setup is done through a crew.config.ts file, either in your XDG config directory or at the root of any repo you run crew from. The main fields you must fill in are the Linear project slug, the directory where workspaces live, and a list of known repositories. You then run crew setup repos to clone those repos, export GROUNDCREW_LINEAR_API_KEY with your Linear token, and either run crew doctor to check the setup, crew run --dry-run for a preview, or crew run --watch to poll forever. The tool also has a careful secrets flow. A small allowlist of build-time tokens, currently NPM_TOKEN and BUF_TOKEN, is forwarded into the setup phase so that commands like npm install can reach private registries, and then those values are unset and the holding file is deleted before the agent process itself starts. The agent never inherits those values. Selection of which ticket runs is governed by Linear labels, blocker status, model usage limits, and a configurable in-progress cap, so you can throttle how many tickets are running at once.

Copy-paste prompts

Prompt 1
Write a crew config ts for groundcrew that watches my Linear project, clones two repos, and runs Claude for tickets labeled agent-ready.
Prompt 2
Walk me through how groundcrew launches an agent inside a Docker Sandbox on Linux. What gets mounted, what is blocked.
Prompt 3
Add a third CLI definition to groundcrew for a custom OpenRouter agent. Show the config schema and the CLI launch command.
Prompt 4
Explain the groundcrew secrets flow that forwards NPM_TOKEN to npm install but hides it from the agent process. Trace it through the source.
Prompt 5
Compare groundcrew vs Sweep vs Aider for running a coding agent against a Linear backlog. Where does groundcrew win and where does it lose.

Frequently asked questions

What is groundcrew?

CLI from ClipboardHealth that polls Linear tickets, spins a fresh git worktree per ticket, and runs Claude or Codex agents in sandboxed parallel sessions.

What language is groundcrew written in?

Mainly TypeScript. The stack also includes TypeScript, Docker, Linear.

How hard is groundcrew to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is groundcrew for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.