Command overview
beacon endpoint pi collects telemetry from Pi by reading the JSONL session records Pi commits under ~/.pi/agent/sessions and converting them into Beacon endpoint events.
Command syntax
beacon endpoint pi sync is for historical backfill, scheduled catch-up, or machines where the extension was not loaded.
Every event is marked harness.collection_method=poll. Beacon sees what Pi wrote after the fact, so nothing here can hold or deny a tool call.
Reading is local and offline. Nothing this command does reaches the network.
Commands
Flags
Both subcommands accept:sync also accepts:
Sweeping
Sweep once
Preview without writing anything
--print is a dry run in both directions: it neither writes the runtime log nor advances the cursor, so running it twice shows the same events and running it does not quietly consume the work a later real sweep would do.
Sweep continuously
sync under whatever scheduler the platform already uses, or leave --watch running.
Status
Show Pi sessions and collection progress
Cursor behavior
The cursor keeps a scheduled sweep from re-appending every session’s whole history. It stores the last collected line per session file, plus the file size and modification time for a cheap unchanged check.
Re-reading is safe: each event ID is derived from the source file, session id, line number, and event position, so the same Pi record maps to the same event every time.
Related
Pi
Telemetry coverage, discovery, and known gaps for the runtime.
Hooks
Install the managed Pi extension for live telemetry.