← BagelCONTENT HISTORY

Update to Bagel

Snapshot Oct 24, 2026 · 13:23 UTC · version 0.2.2

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for operating-live-sinks

Skill instructions — Now says: - Stop topics with `unsubscribe_live_topics` (omit `topics` to stop all). A standing pipeline finishes its queued runs and its end-of-stream run first; ...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Bagel and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 23:14 UTC

No removed lines (ordering may have changed)

After

Oct 24, 2026 · 13:23 UTC

- Stop topics with `unsubscribe_live_topics` (omit `topics` to stop all). A standing pipeline finishes its queued runs and its end-of-stream run first; the recorded buffer stays on disk, and the connection closes once nothing is su...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -13,6 +13,10 @@
   (`JSONL_BUFFER_SIZE_PER_TOPIC_BYTES`, default 1 GB per topic).
 - The subscription's directory path is returned; pass it as the `path` for
   queries and pipelines over the live data.
+- Stop topics with `unsubscribe_live_topics` (omit `topics` to stop all). A
+  standing pipeline finishes its queued runs and its end-of-stream run first;
+  the recorded buffer stays on disk, and the connection closes once nothing is
+  subscribed.
 - Standing pipelines that must survive container restarts belong in the
   `STARTUP_PIPELINES_FILE` manifest: they are re-established on boot.
 - Artifacts (snippets, exports) land under the artifacts directory and are
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\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"
AFTER
"---\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- Stop topics with `unsubscribe_live_topics` (omit `topics` to stop all). A\n  standing pipeline finishes its queued runs and its end-of-stream run first;\n  the recorded buffer stays on disk, and the connection closes once nothing is\n  subscribed.\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"
Full snapshot data
{
  "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- Stop topics with `unsubscribe_live_topics` (omit `topics` to stop all). A\n  standing pipeline finishes its queued runs and its end-of-stream run first;\n  the recorded buffer stays on disk, and the connection closes once nothing is\n  subscribed.\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"
}

SHA-256 of public snapshot: 6ff1dfefe7466b59f8ecdde570390505c3565676742e982585c12ac1cdd50e86