Small Teams Using Claude Code
Make Claude Code reliable across a 5-person team — same gate-check on every developer's machine.
The setup
Your 3-10 person team uses Claude Code for AI-assisted development. The problem: every developer's Claude Code session has different rules, so 'verify before done' is enforced inconsistently. CodeLoop ships one global rule that every developer's Claude Code session honours, plus a shared dashboard of run history.
Workflow
- Onboard the team. Each developer runs `npx codeloop init --global` once — writes ~/.claude.json + CLAUDE.md so every session enforces the same rule.
- Per-project init. Run `npx codeloop init` per repo so the verifier knows the stack.
- Shared dashboard. Each developer's verify runs sync to the team dashboard at codeloop.tech/dashboard so leads see who's hitting the gate-check threshold and who's stuck.
- Pre-PR gate. The GitHub Action runs the same gate-check on every PR; merging requires ≥ 94% confidence.
FAQ
How do I onboard the team?
Each developer runs `npx codeloop auth` (sign in with team email), then `npx codeloop init --global`. That's it. The team plan covers up to 5 active developers; add more seats for $4/mo each.
Does CodeLoop work with our existing CI?
Yes. The CodeLoop GitHub Action runs the same gate-check the local agent does. Your CI's existing tests run inside the verifier's `codeloop_verify` step.
Can the team see each other's verify runs?
Yes — opt-in per developer. The team dashboard shows aggregated runs (who's hitting gate-check fastest, what's flaky) without exposing the actual code under review.