Skip to main content
Monad Mesh is Monad’s Agent Team Runtime and the product’s primary runtime. It owns team identity, session bindings, collaboration, delegation, observation, approvals, and recovery across every agent runtime and client. Members can be backed by any agent runtime. Monad Agent Runtime is the first-party one Monad ships; the rest attach through adapters. This category covers everything that crosses an agent boundary: another first-party agent, a provider-native runtime, an editor, or another machine you own. Pick by trust boundary, not by convenience:

​
Observation has two planes

A teammate agent is not a black box: Monad keeps both the provider’s own frames and a provider-neutral projection of them. Raw frames never enter the chat message log and never enter model context; the convenience plane is what the UI renders. Details: mesh-observation.md, authoring: mesh-adapter-authoring.md.

​
Delegation, end to end

The local agent gets a result, not the remote’s raw reasoning stream. That stream stays in the observation planes where a human can inspect it.

​
Documents

Related: ../../usage/mesh-agents.md for operating mesh agents, ../../concepts.md for the product-level vocabulary.