Browse, monitor, and operate Groundcrew tasks without leaving Raycast. Groundcrew dispatches coding agents to work in isolated git worktrees; this extension is a control panel for the tasks and workspaces its CLI manages.

• Browse Groundcrew Tasks — search tasks from every source, open details, and jump to task URLs, PRs, and worktrees.
• Groundcrew Status — active, preserved, and missing workspaces with queue and slot health. Run lifecycle actions per task (Start, Stop, Resume, Clean Up, and bulk "Clean Up All Idle Workspaces"). Enter opens a live task's cmux workspace, or resumes an idle/interrupted one.
• Start Groundcrew Task — start a task by ticket number (tem-3925), even one not in the browse list.
• Open Groundcrew Workspace — open an existing pull request or branch in a worktree.
• Groundcrew Doctor — run crew doctor to diagnose prerequisites, config, and Linear reachability.

Tip: Assign a hotkey to a command in Raycast (Extensions → Groundcrew → Groundcrew Status → Record Hotkey) to jump straight in without opening Raycast first.

• macOS with Raycast.
• Groundcrew CLI, installed and configured per the Groundcrew docs:

  npm install -g @clipboard-health/groundcrew

Two optional preferences:

• Groundcrew Executable Path — absolute path to crew (or to the shim below). Leave blank to auto-discover from PATH, /opt/homebrew/bin, /usr/local/bin, then nvm.
• Editor Application — the app used for "Open in Editor" on a worktree (e.g. Visual Studio Code). Leave blank for the macOS "Open With" picker.

Raycast launches tools with a stripped environment: a bare PATH (/usr/bin:/bin:/usr/sbin:/sbin) and none of your shell's exports. So crew, the node that runs it, its Linear key, and the git / gh / cmux / tmux it shells out to can all be missing. Read commands (Browse, Status) often survive on a Homebrew/nvm crew, but crew start / resume need the session backend and fail with "neither cmux nor tmux is on PATH."

The reliable fix is a small shim that restores the environment, with Groundcrew Executable Path pointed at it. Create ~/.local/bin/crew-raycast:

Tweak the two marked lines for your machine, then paste the whole block into a terminal:

mkdir -p ~/.local/bin
cat > ~/.local/bin/crew-raycast <<'EOF'
#!/bin/sh
# Restore the environment crew needs under Raycast's stripped PATH.

# TWEAK 1 — source the file that exports your provider keys (delete this line if
# you don't use one). Common choices: ~/.secrets, ~/.zshenv, ~/.config/groundcrew/env.
[ -f "$HOME/.secrets" ] && . "$HOME/.secrets"   # e.g. exports GROUNDCREW_LINEAR_API_KEY

# TWEAK 2 — put YOUR node directory first, then the dir holding git/gh/cmux/tmux.
#   node dir:  dirname "$(readlink -f "$(command -v node)")"
#   the rest:  dirname "$(command -v cmux)"   (Homebrew is usually /opt/homebrew/bin)
# Use the stable install path, NOT a version manager's per-shell dir (e.g. fnm's
# ~/.local/state/fnm_multishells/<id>/bin), which vanishes when the shell exits.
export PATH="/path/to/your/node/bin:/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin"

# Absolute node + crew so the `#!/usr/bin/env node` shebang never has to be found.
exec "$(command -v node)" "$(command -v crew)" "$@"
EOF
chmod +x ~/.local/bin/crew-raycast

Verify it from a bare environment (mimicking Raycast) before wiring it up — crew doctor should report every check ok:

env -i HOME="$HOME" PATH="/usr/bin:/bin" ~/.local/bin/crew-raycast doctor

Then set Groundcrew Executable Path to the shim's absolute path (e.g. /Users/you/.local/bin/crew-raycast). Your terminal keeps using its own crew, so nothing else changes.

Groundcrew Doctor pinpoints what's missing. Nearly every failure is the stripped environment above, and the shim fixes all of them:

git clone https://github.com/shubhsherl/groundcrew-raycast.git
cd groundcrew-raycast
npm ci
npm run build

Then set the Groundcrew Executable Path under Configuration. To update later, git pull and re-run npm run build. Remove it anytime from Raycast → Extensions.

npm install
npm run dev     # ray develop — hot-reloads a dev copy while running
npm run build   # ray build — compiles and installs the extension into Raycast
npm test        # vitest