Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meshpilot.app/llms.txt

Use this file to discover all available pages before exploring further.

A loop is a cross-agent flow. One operator intent — or one external trigger — kicks off a sequence where multiple agents collaborate, each drafting their slice, all gated through your single Inbox. Loops are the cockpit’s orchestration moat made visible. They’re the thing a Zapier-style builder can’t do at marketer-grade UX.

​
The KPI strip

Active loops

Waiting on operator

Completed today

Blocked / failed

Upcoming within 24h

​
The three loops shipping today

A new Shopify order on a cash-on-delivery payment method triggers the Voice agent to place a confirmation call. The transcript is summarised, fraud signals are flagged, and a proposal lands in your Inbox to either confirm, reschedule, or cancel the order.

​
What’s on the page

  • Loop-type tabs for the three flows above.
  • Active loop board — each running loop with its current state, the agent currently holding it, and what it’s waiting on.
  • Per-loop timeline — a step-by-step view of how a loop unfolded, end to end.
  • Outcome summary — what the loop produced after completion.

​
What Loops will not be

Loops are not a Zapier-style node-graph builder. The cockpit shows you the loops we ship; you don’t author new loop types in a canvas. New loop shapes ship as product, not as configuration.

Open Loops

See your active flows.