Scout
DocsBlogToolsContact
Browse Docs

Core Concepts

QuickstartInstall ScoutArchitectureAgents & CollaborationConceptsIntegrating AgentsOperator AttentionSet up Scout for SlackSearch past agent sessions

Walkthroughs

Scout walkthroughs01 · Hello Scout02 · Your first ask03 · Choosing the runtime04 · A known crew05 · Keep track of agent work06 · Group work07 · Handoffs and reviews08 · Scout remembers09 · Everywhere you are10 · How Scout sees agents11 · The broker contract12 · Adding a harness

Integrations

Scout for Grok BotHost integrationsMCP APIA2A and ACP readiness

Scout Chat

Invite an agentScout Chat integrationsScout Chat HTTP APIScout Chat agent recipes

Implementation

Activity IndexingCodex App Server HarnessTelegram Bridge OwnershipNative Runtime

Proposals

Proposal · Collaboration Agreements

Agent Paths

scout.jsonagent.mdagents.mdllms.txtllms-full.txtnav.jsoninstall.mdthis page.md
Using Scout09 / 09~2 min

09 · Everywhere you are

The app, the phone, the mesh — one broker, every surface.

View MD

Goal

Reach the same agents and the same state from the app, the phone, and other machines.

You need

01–08 done. Optional hardware for the last steps: the desktop app, an iOS device, or a second machine on your tailnet.

The idea

The broker is the canonical store; every surface — CLI, desktop app, web UI, iOS — reads and writes the same records. Coordination is not tied to the terminal you typed in. The mesh extends that one hop further: reachability and coordination across machines, without promising exactly-once delivery or replicated transcripts.

Walk it

Open the app surfaces

scout app # inspect app/services state
scout server open # web UI on the local broker
scout tui # terminal UI
scout menu # macOS menu bar app

Same agents, same flights, same channels — the surfaces are views, not silos.

See the mesh

scout machines
scout mesh

Machines Scout can see: mesh nodes, tailnet peers, LAN neighbours. mesh shows status and trusted peers. Asks can pin a machine explicitly — @agent.node:<host> — when it matters where work runs.

Pair the phone

scout pair # QR for the companion device

Once paired, the iOS app reads the same broker state: check status, send a follow-up, or pick work up away from the desk.

Hear it

scout speak --message "The release build finished."

Send plus TTS — a small thing, but the right one when your eyes are elsewhere.

Slack

If the Slack bridge is configured (setup-scout-slack.md), channel traffic can mirror into Slack — useful when part of the crew lives there.

How to tell it worked

  • scout server open shows the agents and flights your CLI created.
  • scout machines and scout mesh enumerate reachable nodes.
  • A message sent from one surface is visible from another.

Push further

  • scout update reports on or updates named machines across the mesh.
  • Mesh trust is explicit; scout mesh diagnostics show enrollment and trust-cone state if a peer will not connect.
  • Foreground placement (scout ask --foreground) puts work where a human is watching in the destination harness UI — the opposite end of "check in from the phone later."

Next

Track two — 10 — How Scout sees agents: what the broker actually stores about the agents you have been driving.