WORKBENCH
Your Garmin data, ready for your agent or your own analysis.
Sync health data and activities into a SQLite archive on your computer or a persistent remote workstation. Keep the source JSON and original activity files. Ask your agent questions through MCP or the CLI, or work directly with SQL, scripts, notebooks and CSV.
- Review sleep, Body Battery, heart rate, steps and activities with dates, units and coverage.
- Compare two metric periods and review workout distance/duration totals by date and sport.
- Generate PNG charts, try experimental in-chat explorers, or let your agent build interactive charts for the question.
- Explore native fields from all 26 documented Personal API endpoints and retain original activity files for your own analysis.
This is the early v0.2.0 release. Read the release notes, start with the synthetic demo or a short sync, and check the tested hosts and assistant paths before relying on an integration.
A real question in Grok's Health Buddy, answered from my Garmin archive. Capture details.
Working with an agent? Give it this repository and ask:
Can you help me set this up? Read AGENTS.md and walk me through docs/SETUP.md on the computer I choose.
Setting it up yourself? Install Python 3.12+ and uv, then:
git clone --branch v0.2.0 --depth 1 https://github.com/0xBreadguy/garmin-data-workbench.git
cd garmin-data-workbench
uv tool install --from . garmin-data-workbenchFollow the setup guide to create your Garmin Personal API key and run a first sync. Guided setup supports Codex and Claude Code; other agents can use local MCP or shell commands. Built-in scheduling supports macOS; remote workstations can use an OS scheduler or provider routine.
For charts, replace the install command with uv tool install --from '.[charts]' garmin-data-workbench.
This checks out the release tag. Contributors can clone the default branch using CONTRIBUTING.md. Existing users should follow the upgrade instructions and preserve their archive, configuration and schedules.
Keep your key out of chat. On a remote workstation, processes sharing your OS user can read credentials and health data. Query results may reach your agent's AI provider. Choose the host before syncing.
Follow the isolated demo setup to generate synthetic data in a new archive, with its own checkout and environment. It makes no Garmin requests and preserves existing installations. An agent can start with:
Can we try this with demo data first? Leave my existing setup alone, and don't connect to Garmin or set up a schedule.
Ask your agent: “I slept over nine hours last night, but my score went down. Can you show me how that compares with the rest of the week?” Or query it yourself:
garmin-archive status
garmin-archive day 2026-01-01
garmin-archive sleep --from 2026-01-01 --to 2026-01-07
garmin-archive trend sleep_duration --from 2026-01-01 --to 2026-01-07Queries use stored data. Available history and fields depend on Garmin, your devices and what was recorded.
Historical renderer capture of the same week, plotted with garmin-archive chart sleep before v0.2.0. The approved image is unchanged; see its capture details. Sleep duration and score tell different parts of the story. Stages, scores and sleep need are Garmin estimates. You can try the same queries with demo data.
| Path | Current boundary |
|---|---|
| CLI and local archive | Offline CI covers macOS, Windows and Linux with Python 3.12. Live Windows credential/privacy validation is still incomplete. |
| Agents | Shell access or local stdio MCP. Codex and Claude Code have guided registration; each assistant connection needs its own query test. |
| Automatic sync | Built-in macOS scheduling. Other hosts need their own scheduler or provider routine. |
See assistant connections for remote access and the checks behind each compatibility claim. Garmin's Personal API is for individuals accessing their own data; review Garmin's FAQ and terms before live setup.
- Commands, SQL, exports and scheduling
- Personal API source and field coverage
- Assistant connections and handoffs
- Experimental in-chat and agent-authored charts
- Contribute · Agent instructions · Testing
- Architecture · Security
Found a problem? Open a bug report or setup report with a synthetic reproduction. Keep credentials, personal health data and routes out of public issues. Report vulnerabilities through the security policy.
Independent open-source project. Not affiliated with, endorsed by, or supported by Garmin.

