Series · 7 parts
Agentic OS
An Agentic OS is the set of practices, infrastructure, and feedback loops that let a new engineer (human or AI) run, code, test, validate, and deploy work autonomously and safely. This series dives into the methodology Mesmer developed for its customers, portable to any team.
Cadence: weekly · 5 of 7 published · 2 still to come
- PlaybookPart 1
Golden standard for agent readiness: treat agents as new hires
We build harnesses for engineering orgs, and this is the metric we've seen is reliable at predicting increases in speed and quality developing with agents, proven through 8 months of experimentation including +2000 engineers across +100 companies. Measure the onboarding of an agent as if it were a new hire, looking at time from access to a deployed first feature, with no help.
- PlaybookPart 2
You may be spending more tokens on context gathering than writing code
Five context-gathering patterns that burn tokens in agentic eng orgs, and the fix for each: scoped instruction files, context firewalls, zero-token polling.
- PlaybookPart 3
Most common agent errors
Five common ways teams produce wrong or stale context for their agents, and four principles that keep it from happening.
- PlaybookPart 4
How to maintain review quality with 10x PR volume
Four check categories, three outcomes per finding, and why a “required” AI review can report a pass when the model behind it is down.
- PlaybookPart 5
Most common failure modes for agents during QA
How we set up every coding agent to QA its own work: an isolated environment per change, realistic data, a written playbook, and a preflight.