For your workDevOps
DevOps project management for the work between incidents.
Toil, upgrades, certificate renewals and postmortem actions sit in one ranked queue. Claude takes the next ready task, and on your own machine a fleet turns the small ones into pull requests overnight.
A month of Premium free, no cardAgents never take a seat
Why the toil never gets done.
Toil never makes the sprint because incidents eat the week.
Our runbooks are out of date the week after we write them.
Postmortem action items vanish once the meeting ends.
An extra engineer for the chores, on your own machine.
Clears toil while you sleep
Dependency bumps, pinned images, flaky tests and config tidying: fleet workers take them from the ready queue, each in its own worktree, and never merge.
Answers from your runbooks
Runbooks, architecture notes and past postmortems are read when they are added, so @Claude in chat answers with the page it found it on.
Turns a postmortem into work
Paste the timeline and notes into the project’s chat. Claude proposes the actions as tasks, and you keep the ones that matter.
Runs a production change the same way
Plan, second pair of eyes, staging, checks, apply. A change workflow stops at each gate and waits in Approvals for a person.
Start from a sentence. Keep what fits.
Say what the project is for and Claude drafts it: the statuses, fields and views below, ready to rename, switch off or add to.
Statuses
Fields
Views
- Write the change plan
- Second engineer reviews the plan (a person checks)
- Apply to staging
- Smoke tests and dashboards
- Approve the production apply (a person checks)
- Change log entry
Production change, as a workflow. The clay steps stop for a person. How workflows work
Before you give it the keys.
Will an agent touch production?
Fleet workers only open pull requests from their own worktrees and never merge. Applying a change stays with your team and your pipeline.
Can we keep the on-call checklist here?
Yes. A routine is a recurring checklist ticked by day, so each shift sees what the last one checked.
Does it replace our incident or paging tool?
No. It holds the work around incidents: actions, toil, runbooks and upgrades. Keep paging where it is.
Which code tools does it work with?
GitHub branches and pull requests show on their tasks, and Azure DevOps, Trello and Monday boards sync both ways.
Hand the toil to the fleet.
A month of Premium free, no card, and your first chores queued before the next on-call shift.