ReviewQueue Team Pack vs manual queue polling
Manual polling works for solo pilots and low-volume queues but scales poorly when reviewers are in meetings or across time zones. Team Pack scripts push structured Slack or Telegram alerts on each pending request — at the cost of webhook setup, env-var discipline, and wiring the notify step into your agent wrapper.
Manual polling (`reviewqueue list` in terminal or chat), ReviewQueue Team Pack notification scripts
Manual polling (`reviewqueue list` in terminal or chat)
Running `reviewqueue list` in a terminal or pasting queue JSON into the web viewer requires no extra dependencies and fits a single reviewer who lives next to the agent machine. It fails when approval volume rises: risky commands sit in `pending/` until someone remembers to check, agents time out waiting, and on-call engineers miss overnight queues. Chat screenshots of terminal output are poor audit evidence compared to JSONL exports.
ReviewQueue Team Pack notification scripts
The Team Pack ships `notify_slack.py` and `notify_telegram.py` that read pending request JSON and POST id, risk category, argv, and cwd to your webhook or bot. Scripts exit 1 when env vars or request ids are missing so CI wrappers can fail loudly. Tradeoffs: you must create and rotate webhooks securely, call the notify script after each queued command (or wrap `reviewqueue exec`), and still run approve/reject from a terminal or shared git-synced queue. Notifications do not replace human judgment — they reduce time-to-first-review.
Recommendation
Manual polling works for solo pilots and low-volume queues but scales poorly when reviewers are in meetings or across time zones. Team Pack scripts push structured Slack or Telegram alerts on each pending request — at the cost of webhook setup, env-var discipline, and wiring the notify step into your agent wrapper.
When to combine
Many teams start with manual `reviewqueue list` polling during pilot week, then add Team Pack notification scripts once approval volume justifies a dedicated Slack channel. Keep the shared-queue git-sync guide if reviewers work from different machines — notifications alone do not sync pending state across hosts.