Plaid’s Hamilton cloud coding agent writes thousands of PRs and accounts for about 20% of all merges
Plaid built Hamilton, an internal cloud coding agent engineers tag from Slack or GitHub. It reuses the same local agent harnesses inside Plaid-hosted environments (CI first, then a CodingAgents service with sandboxed headless and interactive tmux runtimes). Multi-agent orchestration splits high-level prompts across repo selection, plan approval, implementation, and CI-fix sub-agents. Hamilton non-stop writes thousands of PRs and accounts for roughly 20% of all merges; the revised platform ~3×’d daily cloud-agent PR volume versus the first CI-based version. Sister post (May 2026) puts company-wide AI-generated PRs at 80% (~90% of code) and PRs per engineer up 50%.
The numbers (as reported)
| Hamilton share of merges | Roughly 20% of all merges |
|---|---|
| Volume | Thousands of PRs written non-stop |
| Platform uplift | ~3× daily cloud-agent PR volume vs first CI platform |
| Company AI PRs (May 2026 sister post) | 80% of PRs AI-generated (~90% of code); +50% PRs per engineer |
Facts
- Company / subject
- Plaid
- Tools
- Unstated
- In-house tools
- Hamilton
- Codebase
- Not applicable
- Work type
- Company rollout
- Stack
- Slack, GitHub, CI, tmux, Bazel
- Published
- 2026-05-19
- Last checked
- 2026-11-04
What the source claims Practitioner (own blog/paper)
Claimed by the builder, writing about their own work. Not checked independently.
- Hamilton accounts for roughly 20% of all merges ~20% of merges
“Hamilton now non-stop writes thousands of PRs for our engineers and accounts for roughly 20% of all merges.”
- New Hamilton platform ~3×’d daily cloud agent PR volume versus the original CI-based platform ~3× daily cloud PR volume
“Hamilton on our new platform immediately ~3x’d our daily cloud agent PR volume as compared to our original platform”
Caveats
Self-reported. Commercial coding harnesses are not named (tools left Unstated; Hamilton is internal). The 20% merge share and “thousands of PRs” lack absolute denominators. Sister adoption post is a secondary URL for company-wide context.
More stories by tool: Unstated
Related topics: Company rollouts and cost
Source
Plaid Engineering (Clay Allsopp)
Also: https://engineering.plaid.com/a-year-of-ai-engineering-adoption-97e754d22d85