← BagelCONTENT HISTORY

Update to Bagel

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.2.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when investigating a robot log or flight log with bagel — finding events, anomalies, or \"what happened around X\" in rosbags, MCAP, CAN, MDF4, ULog, or Betaflight files. Routes to the server's triage capability.",
  "included_files": [],
  "name": "triaging-robot-logs",
  "skill_md_contents": "---\nname: triaging-robot-logs\ndescription: Use when investigating a robot log or flight log with bagel — finding events, anomalies, or \"what happened around X\" in rosbags, MCAP, CAN, MDF4, ULog, or Betaflight files. Routes to the server's triage capability.\n---\n\n# Triaging robot logs\n\nThe bagel MCP server ships its own step-by-step triage workflow. Do not\nimprovise one: fetch and follow it.\n\n1. Call `run_poml_capability` with `poml_path=\"./src/agent/triage/investigate.poml\"`.\n2. Follow the returned instructions exactly (describe-first, windowed queries,\n   snippet/GIF evidence).\n\nIf the bagel tools are missing or the connection fails, the server is probably\nnot running — the user must start the Docker container for their data format\nfirst (see references/formats.md for the format → image → extra-args table,\nincluding the CAN `dbc` requirement).\n"
}

SHA-256 of public snapshot: f4dcfde9faf837e5c5a3a4e1f3c9c6c80a88db96b3d05c1aae55142a2b697d00