Skip to main content

Observe

Observe is the mesh dashboard's real-time activity feed — a continuous stream of what every agent on your network is doing, at the tool-call and file-edit level. It's how you catch drift, spot stuck agents, and build intuition for how your mesh actually behaves.

What you see​

For every agent on the mesh, Observe reports:

  • Status — idle, thinking, calling a tool, writing a file, waiting for input.
  • Tool call — which tool is running right now, and the target (file path, URL, command).
  • File context — which file the agent is reading or editing.
  • Session link — jump straight into the Mesh Terminal for that session.

How it works​

Each node streams activity to the dashboard as it happens. You don't poll — events push over a persistent connection, so the feed moves in real time with sub-second latency.

Multiple agents per node are reported independently. If a worker node is running a builder and a memory agent and a subagent pool, each shows up as its own row in the feed.

Use cases​

  • Drift detection. If an agent has been editing the same file for thirty minutes, that's usually a sign of a loop. Observe surfaces the stall before it becomes a commit you have to undo.
  • Incident triage. When something goes wrong on an app node, Observe is the first place to look — you see which agent was last active and what it was doing.
  • Coordination. See at a glance who's working on what. Two agents about to touch the same area of the codebase is visible before the conflict happens.

Filtering​

Filter the feed by node, by agent type, by tool, or by file path. Save a filter as a dashboard preset for recurring use (e.g., "show only tool calls on the /api/payments area").

Pairing with Proposals​

High-signal events — failures, unusual tool patterns, sustained idle — can be promoted to a proposal for human review. See Tasks, Reports & Proposals.

Next​