How do async, high-trust teams work with AI agents?
By Soumen Sarkar · October 2026
Short answer: The same way they work with each other: work is written down where everyone can see it, decisions travel with their reasons, people act on the team's updates without waiting to be told, and anything reversible is decided on the spot. Agents fit that way of working better than any tool before them.
What do high-trust teams already know?
Some of the fastest teams in software have never worked in the same room or time zone. The habits that let them move without waiting were worked out long before agents:
- Open source projects are built by people who mostly never meet. The work happens in public, in writing: the Apache Software Foundation's maxim is that if it didn't happen on the mailing list, it didn't happen.
- GitLab runs as an all-remote company with asynchronous communication as its default. Work happens in issues and merge requests rather than in meetings, written with enough context that someone asleep or new can act on it, and its public handbook runs to thousands of pages.
- Amazon separates one-way doors from two-way doors: decisions that can be reversed are made quickly by whoever is closest to the work, and only the irreversible ones get slowed down. When people disagree, they can disagree and commit, so the work keeps moving.
- Mission command, the way modern armies lead, gives every unit the commander's intent, so people can act on their own when the plan meets reality instead of waiting for orders.
- Google's DORA research found that a high-trust culture, where information flows freely and on time, predicts how well a team delivers software.
The common thread: context is written down, intent is shared, reversible calls are made on the spot, and nobody waits to be told what they could have read.
Why do agents fit this so well?
An agent is the most async teammate there is. It works at 3am, doesn't need a meeting, and can read everything the team has written in seconds. Give it written context and shared intent, and it does exactly what high-trust teams ask of people: it acts without waiting.
The pieces map directly:
- Written context becomes the team record every agent reads before touching the code.
- Two-way doors become assumptions: the agent makes the reversible call, says so, and keeps going.
- Disagree and commit becomes a recorded decision the newest work follows.
- Commander's intent becomes a plan in work in progress and a handoff for whoever continues.
What's left to fix?
The slow part of a team now is a person's voice reaching the work: a developer's answer, a product manager's call, a customer's request. High-trust habits make that voice travel in writing, at any hour. That's what VibeFlock builds on, and what Campfyrr makes automatic, so a team of people and agents keeps pace with its fastest members.
Words used here
- Team record: The team record is everything a team has written down that a person or agent can search before asking: decisions, rules, handoffs, assumptions and the reasons behind changes.
- Decision: A decision is a call made in the work, recorded with its reason at the moment it is made, so it travels to everyone who touches the same ground.
- Handoff: A handoff is what unfinished work carries for whoever continues it: what's done, what's left, the next step, and what to watch out for.
- Assumption: An assumption is the best available answer to an unknown, stated and acted on, kept visible so anyone can correct it.
The principle behind this: Keep moving: The work never waits, and neither do we.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).