Log
What shipped, how it was built, and what we think about it. Written by people. Occasionally with agents, and we say so.
Why I built another issue tracker
I still love Linear. Years of using and studying trackers helped me work out what I wanted for my own projects and the agents building them.
I liked Superpowers. My docs folder didn't.
Jesse Vincent's Superpowers skills made my agent brainstorm, plan and test first. They also filed a dated plan in my repository every time I used them, and none of those plans knew when it was done.
Hydrant and Jira
Jira suits organizations that need breadth and control; Hydrant suits a small team running an explicit human-and-agent delivery loop.
Hydrant and monday.com
monday work management lets teams configure an operations system. Hydrant supplies a narrower issue system with fewer knobs.
Hydrant and Asana
Asana connects tasks to portfolios and company goals. Hydrant keeps a compact delivery loop for a much smaller team.
Hydrant and ClickUp
ClickUp consolidates work across a configurable hierarchy. Hydrant keeps one software-delivery loop deliberately bounded.
Our decisions file is a history, not a spec
We split current instructions from decision history so agents can start quickly without losing the reasons, reversals and rejected work behind them.
Hydrant and Basecamp
Basecamp gives a project one room for work and conversation. Hydrant keeps a narrower contract around each ticket.
The test was faster than React
A browser test saw the new URL, raced ahead of the screen, and blamed the picker it closed along the way.
Hydrant and Trello
Trello makes a board easy to shape and automate. Hydrant fixes more of the software-delivery meaning in advance.
Merged isn't done
One settings change passed review and merged cleanly, then stayed unfinished until the released product proved the same thing.
Hydrant and Obsidian
Obsidian is a local knowledge environment; Hydrant is a shared issue tracker for accountable delivery by people and agents.
What our agents cost in CI time
Agent throughput turned repeated test runs into a design problem for our delivery process, measured in runner time rather than guesses about money.
Look us up in Claude
Hydrant is listed in Claude's connector directory as a Community connector. Add it, approve one workspace, choose read only or read and write, and start asking.
Hydrant and Notion
Notion keeps projects beside the knowledge that explains them. Hydrant gives software tickets a narrower shared meaning.
Hydrant and GitHub Issues
GitHub Issues keeps tasks beside code and pull requests; Hydrant gives a small human-and-agent team a separate delivery workspace.
Hydrant and Linear
Both trackers work with agents. The useful choice is about the size and shape of the work around them.
Hydrant and Markdown files
Markdown task files are cheap, portable and reviewable; Hydrant supplies shared state and coordination that a repository must otherwise maintain.
Steal our workflow
We wrote down the steps our agents follow before they build and ship. You can use the same workflow and change the parts that don't fit.
We forgot to launch
Hydrant went live without an announcement. Seventeen days in, here is what shipped, what is on the bench and what is on ice.
What agents can't touch
A missing production secret stopped an agent's deployment. The useful part was what it did next: leave the release unfinished and ask.
Your work and your agents
Cockpit now keeps your tickets and your personally owned agents together, while Watchtower shows the team moving around them.
Atom feed. For people who still own an RSS reader, and agents.