{"id":18136,"plugin_id":"plugins_6a8623a0fe288191833ee0ca3fa883e7","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:39.252Z","digest":"173088a566befa782f3477afd016f82c0b8980658f339bad663aac24fdc34eb0","against":null,"payload":{"description":"Use when subscribing to live robot data (MQTT, rosbridge) through bagel, managing standing pipelines that survive restarts, or when questions about live-buffer sizes and disk usage come up.","included_files":[],"name":"operating-live-sinks","skill_md_contents":"---\nname: operating-live-sinks\ndescription: Use when subscribing to live robot data (MQTT, rosbridge) through bagel, managing standing pipelines that survive restarts, or when questions about live-buffer sizes and disk usage come up.\n---\n\n# Operating live sinks\n\nLive data flows into per-topic rolling disk buffers on the bagel server;\nstanding pipelines run against them.\n\n- Discover what a live source publishes with `list_live_topics`, then\n  `subscribe_live_topics` to start recording; each topic gets a rolling buffer\n  (`JSONL_BUFFER_SIZE_PER_TOPIC_BYTES`, default 1 GB per topic).\n- The subscription's directory path is returned; pass it as the `path` for\n  queries and pipelines over the live data.\n- Standing pipelines that must survive container restarts belong in the\n  `STARTUP_PIPELINES_FILE` manifest: they are re-established on boot.\n- Artifacts (snippets, exports) land under the artifacts directory and are\n  never cleaned up automatically: they are the user's deliverables. See\n  references/settings-knobs.md for every knob and its default.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}