crew-assistant

Decisions are the only thing that needs you — approve a draft, answer a reviewer's question, or choose what happens at the round limit, from the dashboard, chat or Slack

Independent review by default — the draft team writes on Claude and reviews on Codex, so the reviewer is not checking its own work

Code teams — a researcher plans before anything is written, an implementer changes a private clone, reviewers read the change and QA runs your check

Landing is yours to set — a new branch, a fast-forward of main as one commit, or a GitHub pull request the team shepherds through review and CI

Team members with memory — named specialists keep what a turn taught them as learnings, never about one project, and read one only when it applies

A live board — each request shows its stage, how long its role has run, its tool calls and changed files, and says why it is waiting

Sandboxed roles — every role runs headless through lib-agent-harness under the CLI's own OS sandbox, proved before any credentialed launch

Usage floors — roles leave part of each Codex and Claude window unused, and a task waits for the reset instead of failing

Connections, not a registry — lin, agent-slack, agent-fathom and agent-notion answer bounded read queries; credentials stay with each CLI

Private by default — local pairing codes, optional Tailscale Serve for named users, and no public Funnel