DevCrew puts five focused agents inside the chat tool your team already uses — Slack, Teams, Telegram or Discord. Describe a need; get scoped, reviewed, tested work back in the same thread.
The crew
Product
Needs → requirements
Interviews you in the thread: one need in, a clean set of requirements out — ready to become tickets.
Scoper
T-shirt estimates
Reads the ticket, inspects your actual codebase, answers with a size and the touch points — in the thread.
Dev · opt-in
Small tickets → merge requests
For XS/S scoped work: opens a branch, writes the code, pushes a review-ready MR — you merge. Bigger tickets? Keep using Claude Code, OpenAI or your usual flow — the crew plugs into whatever you use.
Reviewer
Merge reviews
Watches your repos and reviews every MR against your conventions. Findings land where reviews live.
E2E
Proof it works
After merge, runs the flow for real and posts a short captioned video in the thread. No "works on my machine".
One work item, end to end
What you plug in
01 A worker
One Docker container on any box you own — your laptop, a VPS, CI spare. It dials out; no inbound ports, no VPN. Your code never leaves your machines.
02 Git access
A GitHub or GitLab token scoped to the repos DevCrew should see. Read for scoping, comment for reviews — nothing else.
03 Your tracker
GitHub Issues, GitLab, Jira, Linear or YouTrack — plus Redmine. Tickets stay where your team already works.
Everything the crew writes carries an AI disclosure mark. Everything it reads stays on your worker.
Early access
We're onboarding a few teams first.
Tell us where your team lives — it decides what we ship first.