Connect the repo
A project points at one repository. Point your coding agent at the same project id and it knows where to report.
// project management for teams that build with agents
A project is a folder that reports on itself.
StacOps reads the work as it happens. Your coding agent logs what it did, GitHub reports what shipped, and the project timeline writes itself. You approve, comment, and reorder. Nobody writes a status update.
sign in invite only
Status decks go stale because a person has to write them.
StacOps removes the person from that step. The tools already doing the work report the work.
- agents report in
Your coding agent writes the log
Claude Code talks to StacOps over MCP. It logs progress, moves tasks, flags blockers, and clocks its own time while it works. No hooks to install, no end-of-day recap to write.
- repo as source
One project, one repo
Connect the repository and commits, pull requests, and merges land on the project timeline next to everything else. What shipped is a fact the project already knows.
- humans decide
You approve, you do not author
The machine proposes. People approve, comment, reprioritize, and reorder the queue. Judgment stays human; transcription stops being a job.
- since you left
A recap that knows when you last looked
Home opens on what changed since your last visit: what needs you, what is blocked, what slipped, and what is quietly waiting on someone else.
- 01
- 02
Work the way you already work
Write code, open pull requests, run sessions. Progress, blockers, decisions, and time land on the timeline as they happen.
- 03
Read, approve, reorder
Open Home and see what moved since you were last here. Approve what is waiting, comment where it matters, drag the queue into the order you actually want.