ReviewQueue Team Pack rollout for agent approval teams
Run `pip install -e ".[dev]"` from the ReviewQueue repo (or your packaged install), then `reviewqueue init` on each machine where Cursor, Claude Code, or similar agents execute shell commands. Confirm `~/.reviewqueue/pen…
Day 1 — Install the free CLI on every agent host, Day 1 — Wrap the agent shell and validate the queue, Day 2 — Wire Slack or Telegram notifications
Day 1 — Install the free CLI on every agent host
Run `pip install -e ".[dev]"` from the ReviewQueue repo (or your packaged install), then `reviewqueue init` on each machine where Cursor, Claude Code, or similar agents execute shell commands. Confirm `~/.reviewqueue/pending/` exists and is writable. The Team Pack does not replace the CLI — it adds notification scripts, rollout guides, and an audit rollup template on top of the free toolchain.
Day 1 — Wrap the agent shell and validate the queue
Point your agent wrapper at `reviewqueue exec -- <command>`. Safe commands pass through immediately; risky patterns like `git push`, `rm -rf`, and deploy commands queue until approved. Test with `reviewqueue exec -- echo ok` (immediate) and `reviewqueue exec -- git push origin main` (queued). Practice `reviewqueue list`, `reviewqueue approve <id>`, and `reviewqueue reject <id>` — rejected commands exit with code 2 so automation can detect denial.
Day 2 — Wire Slack or Telegram notifications
Create a Slack Incoming Webhook or Telegram bot plus chat id. Export `SLACK_WEBHOOK_URL` or `TELEGRAM_BOT_TOKEN` and `TELEGRAM_CHAT_ID` on the notify host — never commit webhook URLs or bot tokens to Git. Copy `scripts/notify_slack.py` or `scripts/notify_telegram.py` from the Team Pack. After a risky command queues, pass the request id: `python scripts/notify_slack.py --request-id <id> --queue-dir ~/.reviewqueue`. The script posts id, risk category, argv, and cwd so reviewers can act without polling the terminal.
Day 3 — Shared queue via private Git (optional)
When multiple reviewers or agent hosts need one inbox, follow `guides/shared-queue-git-sync.md`: initialize a private repo with `reviewqueue init --queue-dir .`, commit `pending/` and `audit.jsonl`, and clone it to `~/.reviewqueue` on each machine. Agents set `REVIEWQUEUE_DIR=~/.reviewqueue` and push pending files after submit; reviewers `git pull`, approve, and push status updates. Use branch protection and signed commits if your org requires them. Prefer a single `#reviewqueue` Slack channel to avoid duplicate approvals.
Week 1 — Audit rollup and policy tuning
Run `chmod +x templates/audit-rollup.sh` then `./templates/audit-rollup.sh -o audit-rollup.md` for a 30-day markdown export via `reviewqueue export`. Review rejections and tune which commands your team treats as risky. Feed notable approvals into IncidentScribe or DestructGuard policy updates when incidents still occur. The pack's `guides/team-onboarding-checklist.md` mirrors this schedule as a printable checklist.