← Back to Bagel

Community

Bagel gets better every time someone brings a format we haven't seen. The project is Apache 2.0, so use it commercially, fork it, ship it. It is developed in public. Whether you have five minutes or a whole weekend, there is a useful help below.

Bagel by Extelligence is an open-source MCP server for analyzing robotics, drone and IoT data with auditable SQL. Reports from actual workflows help improve its tools and documentation.

Share a workflow someone can reproduce

Tell us what you tried, what worked, and where Bagel fell short. A specific report is useful whether the outcome was successful, incomplete, or a failure. Share only recordings you have permission to distribute; a minimal synthetic fixture can be enough.

  1. Task and setup: state your question, Bagel version or commit, container tag or digest, client/model if used, host and format.
  2. Input: link a shareable sample and its license, or explain what cannot be shared. Include topic/schema details and the time range needed to reproduce the behavior.
  3. Steps: include the exact prompt, commands, tool requests, executed SQL and any preview approval.
  4. Outcome: report returned values and artifact paths. If comparing sizes or timings, give exact units, before/after measurements and what the measurement includes.
  5. Limits: describe missing topics, skipped checks, manual corrections, errors and remaining uncertainty. Separate measured observations from suggestions.

If you write a public review, describe your own experience and disclose any affiliation with the project. Please do not claim results you did not obtain or turn one sample's result into a general benchmark. We do not need a positive rating to learn from a report.

copyable report outline
Task:
Bagel version / commit / image digest:
Host, client and model (if used):
Sample, license, format and topic schemas:
Exact prompt / commands / SQL:
Expected result:
Observed result and evidence:
Manual steps, missing checks and limitations:
Affiliation (if any):

Open an issue for a bug or reproducible finding ↗ or discuss a workflow on Discord ↗. Start from a task guide or the shareable incident example.

Good first steps

Add a data format · a weekend

Adapters follow a consistent source / topic / message / logging family. If Bagel cannot read your recordings yet, that is the highest-value contribution on the board.

Open a format request ↗

Report a bug you hit · ten minutes

A bag that fails to parse, a query that returns the wrong shape, a container that will not start. Include the format, the service you ran and the prompt.

File an issue ↗

Sharpen a runbook · half an hour

Documentation lives in doc/ next to the code. If a guide lost a step or your environment needed one more command, a docs pull request is very welcome.

Browse doc/ ↗

Answer a question in Discord · five minutes

Maintainers and users hang out there regularly. Helping someone get their first bag answered is real contribution, no commit required.

Join the server ↗

Contribution flow

01 · Fork and branch

Branch from main. Keep the change focused. One concern per pull request makes review fast.

02 · Match the house style

Ruff via pre-commit, tests beside the code they cover, and a coverage gate in CI. Run the suite in the container matching your change.

03 · Open the pull request

Explain what you verified and how. Stacked work lands through a tip landing PR as the final review gate.

04 · Review and land

Maintainers review in the open. Releases follow semver, with prerelease tags for larger waves of change.

terminal
git clone https://github.com/<you>/bagel.git && cd bagel
uv sync                      # dependencies from uv.lock
pre-commit install           # ruff on every commit
pytest                       # non-ROS subset on a laptop

# full suite inside the matching container
docker compose run ros2-jazzy pytest

Security

Found a vulnerability? Please report it privately first. See the security policy. Credentials are redacted from Bagel's errors, logs and metadata by design.

Where to find us

DiscordDay-to-day conversation with maintainers and users.↗GitHub issuesBugs, format requests and feature proposals.↗GitHub repositorySource, releases and published container images.↗
Looking for the docs? →