stream
The stream domain has 1 action. On the meta surface they are all reached through arcane_stream; on the individual surface each one is its own tool; on the dynamic surface run them with arcane_execute_action and the canonical ID.
Summary
Section titled “Summary”| Action | Title | Kind |
|---|---|---|
stream.snapshot | Listen to Arcane’s live feed | read |
Actions
Section titled “Actions”stream.snapshot
Section titled “stream.snapshot”Listen to Arcane’s live feed
Listen to Arcane’s multiplexed live feed (environments, dashboard, activities, events, version) for a few seconds and return the events received
- Kind: read
- Required parameters: none
- Meta tool:
arcane_streamwith"action": "snapshot" - Individual tool:
arcane_stream_snapshot - Arcane route:
GET /api/stream - Operation ID:
streamClient - Usage: Use to watch live state for a short window (seconds, default 5, max 120, stops early after maxEvents, default 100, and stopped says why it ended). For history use event.list or activity.list, and for one-off reads environment.list, dashboard.get or server.app_version. Each event’s data is an envelope with channel and one payload (environment, dashboard, activity, eventLog or version) carrying its own type: environments, dashboard and activities (one per environment, with environmentId) and version start with a type ‘snapshot’ of current state, but the events channel only sends eventLog type ‘changed’ with no event content, so follow it with event.list. Heartbeats (envelope type ‘heartbeat’, no channel) come every 15 s. Narrow channels (e.g. ‘environments,version’) to cut noise. Unknown channel names and channels the API key lacks permission for (dashboard, activities, events) are silently dropped, so a short window can return nothing, and limit caps activities per activities snapshot.
- Related actions:
event.list,activity.list,environment.list,dashboard.get,server.app_version