10 posts shown
Five of us build swamp. None of us write code. Agents write it, review it, test the binary. The work didn't shrink — it shifted to the decisions that were always the most valuable.
Five people, $3,000/month, zero lines written manually. GitHub just moved to per-token billing. The era of flat-rate pricing absorbing your agent's inefficiency is ending. Your agent isn't the…
The PR-as-contribution model was built for a world where writing code was the bottleneck. AI agents broke that assumption. GitHub shipped a kill switch on PRs. Hashimoto built Vouch. We closed the…
Encoding judgment the agent lacks into AWS operations
Mechanical friction is dissolving, but do not mistake easy for simple
We use swamp to build swamp. That sounds like marketing until you look at how an issue actually moves through our process — not as a GitHub thread with comments piling up, but as a state machine with…
Skills are context. They're the thing an agent reads before it decides how to use swamp. If the skills are wrong, everything downstream is wrong — so we test them in CI the same way we test code,…
Agents open PRs in our repo. Other agents review them. That means untrusted input flowing through models with merge authority — so we built a pipeline with four independent AI reviews, scoped tools,…
Every release binary gets dispatched to a separate repo running CLI tests, adversarial security tests, and benchmarks. Three recent bugs — all with full unit test suites passing — never reached a…
Most people hit "always allow" within the first hour. Agent trust is a system design problem, not a containment problem. Three layers of permissions, conventions, and context let the agent work…