cyberjunkycyberjunky/python-garminconnect/CLAUDE.md

python-garminconnect

CLAUDE.md3.2k starsChanged 6 days agoMITView on GitHub

- NEVER add AI attribution to anything in this repo: no Co-Authored-By: Claude ... trailers in commit messages, no "Generated with Claude Code" footers in PR bodies or anywhere else. This overrides any default behavior. - Security fixes go on security/<topic> branches off master, one report per branch/PR. - Do not reference security-report numbers with # in commit messages or PR titles/bodies (GitHub auto-links them to unrelated issues). Use plain "report NNNN" wording instead. - Never mention security-report numbers in…

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
NEVER add AI attribution to anything in this repo: no Co-Authored-By: Claude ...
line 5
Very specific:
Do not reference security-report numbers with # in commit messages or PR titles/bodies (GitHub auto-links them to unrelated issues).
line 10
Very specific:
Never mention security-report numbers in code or code comments — describe the defect/behavior instead.
line 13

≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

CLAUDE.md

Project instructions

Git / PR conventions

NEVER add AI attribution to anything in this repo: no Co-Authored-By: Claude ... trailers in commit messages, no "Generated with Claude Code" footers in PR bodies or anywhere else. This overrides any default behavior.
Security fixes go on security/<topic> branches off master, one report per branch/PR.
Do not reference security-report numbers with # in commit messages or PR titles/bodies (GitHub auto-links them to unrelated issues). Use plain "report NNNN" wording instead.
Never mention security-report numbers in code or code comments — describe the defect/behavior instead. Report traceability lives only in the local SECURITY_AUDIT_LOG.md.

Security audit workflow

External audit findings are logged in SECURITY_AUDIT_LOG.md (local only, gitignored — never commit or publish it).

Download now (ZIP)

Dec 31, 2023[FEAT] - Integrate with Garmin — endurain-project/endurain7 reactions · 6 comments
May 15, 2026Widget+cffi fails with email MFA — unexpected title 'GARMIN Authentication Application' — Taxuspt/garmin_mcp5 reactions · 4 comments
May 18, 2026Garmin Support — seanmorley15/AdventureLog2 reactions · 2 comments
Dec 4, 2024Connection Failure - Change User Agent for Garmin API Changes — sealbro/dotnet.garmin.connect2 reactions · 2 comments
Feb 24, 2021Bump python-garminconnect to 0.1.19 to fix broken api — home-assistant/core2 reactions · 4 comments

45 more on GitHub

Oct 13, 2026[Feature] Improve Garmin integration for self-hosters — TraceApps/nutritrace1 reaction · 2 comments
Apr 11, 2026fix: update auth to use new garminconnect token API — Taxuspt/garmin_mcp1 reaction · 7 comments
May 30, 2025Try to use original file instead of always GPX — Dryusdan/garmin-to-fittrackee1 reaction · 1 comment
May 17, 2020Update to garminconnect 0.1.13 — home-assistant/core1 reaction · 2 comments
Oct 30, 2026deps: bump garminconnect from 0.3.16 to 0.3.20 — aaronspruit/garmin-activities-download0 reactions
Oct 29, 2026chore(deps): Bump garminconnect from 0.3.17 to 0.3.19 in /services/garmin — bhavinvirani/running-coach0 reactions
Oct 29, 2026build(deps): update garminconnect[workout] requirement from >=0.3.16 to >=0.3.20 — agogte/garmin_mcp0 reactions
Oct 29, 2026Bump the python-compatible group across 1 directory with 7 updates — aarogozin/garmin-health-sync0 reactions
Oct 29, 2026Login móvel Garmin retorna HTTP 429 sem exceder tentativas — yanscholze/zonas_app0 reactions
Oct 28, 2026Bump garminconnect from 0.3.17 to 0.3.20 in /tools — Flare0805/ember0 reactions
Oct 28, 2026Spec: Fahrt speichern – FIT-Export und Garmin-Connect-Upload — interias/VSpin0 reactions · 5 comments
Oct 27, 2026Build(deps): bump garminconnect from 0.3.19 to 0.3.20 — ecukalla/garmin-training-export0 reactions
Oct 27, 2026Bump garminconnect from 0.3.16 to 0.3.20 — MaksymDovbnia/garmin-mcp-readonly0 reactions
Oct 27, 2026Bump garminconnect from 0.3.2 to 0.3.20 — frictionlesscode/garmin-mcp0 reactions
Oct 27, 2026build: bump garminconnect from 0.3.19 to 0.3.20 — Lukas-Beike/ai-coach0 reactions · 1 comment
Oct 26, 2026build(deps): Bump garminconnect from 0.3.11 to 0.3.20 — greg070/python-strava-garmin-name-sync0 reactions
Oct 26, 2026chore(deps): bump garminconnect from 0.3.19 to 0.3.20 in /garmin — frankzotynia10/fitness-sync0 reactions
Oct 26, 2026chore(deps): bump garminconnect from 0.3.19 to 0.3.20 in /strava — frankzotynia10/fitness-sync0 reactions
Oct 26, 2026deps(deps): bump garminconnect from 0.3.3 to 0.3.20 — bradpenney/garmin-sync0 reactions · 1 comment
Oct 26, 2026chore(deps): Bump the python-minor-patch group across 1 directory with 9 updates — yamakii/garmin-performance-analysis0 reactions
Oct 25, 2026Bump garminconnect from 0.3.10 to 0.3.19 in /tools/garmin_import — iam-jcbradley/DebriefGolf0 reactions
Oct 25, 2026build(deps): bump the pip group across 1 directory with 7 updates — mlorentedev/garsync0 reactions · 1 comment
Oct 25, 2026build(deps): update garminconnect requirement from <0.4,>=0.3.15 to >=0.3.19,<0.4 — markuspaschi/endurance-training-bridge0 reactions
Oct 25, 2026Bump garminconnect from 0.3.18 to 0.3.19 — CarpetoX/garmin-recovery0 reactions
Oct 25, 2026Bump garminconnect from 0.2.25 to 0.3.19 — mganjoo/garmin-fitness0 reactions
Oct 24, 2026Update garminconnect requirement from <1.0,>=0.3.5 to >=0.3.19,<1.0 — nebulaototo/slipstream-kr0 reactions
Oct 24, 2026build(deps): bump the uv group across 1 directory with 3 updates — PatrykPodworski/garmin-cli0 reactions
Oct 24, 2026Update garminconnect requirement from >=0.3.11 to >=0.3.19 in /fetcher — Imgrund/hybridlog0 reactions · 1 comment
Oct 23, 2026chore(deps): bump garminconnect from 0.3.13 to 0.3.19 — javipaur/garmin-coach-mcp0 reactions
Oct 23, 2026Port Garmin integration from garth (unofficial SSO) to Garmin's official Personal API — e2kd7n/ride-optimizer0 reactions
Oct 19, 2026build(deps): Bump garminconnect from 0.3.17 to 0.3.19 in /sidecars/garmin in the upstream group — KaanEmec/vitamux0 reactions
Oct 14, 2026deps: update garminconnect requirement from <0.4,>=0.3.16 to >=0.3.17,<0.4 in /skills/garmin in the garmin group — dbhq-uk/garmin-skill0 reactions · 1 comment
Oct 6, 2026Bump garminconnect from 0.3.10 to 0.3.17 — alexpomsft/garmin-readonly-mcp0 reactions
Oct 5, 2026fix(deps): update garminconnect requirement from <0.4.0,>=0.3.16 to >=0.3.17,<0.4.0 — praxys-run/praxys0 reactions · 1 comment
Oct 5, 2026Upstream canary failed: garmin — KaanEmec/vitamux0 reactions
Oct 4, 2026chore(deps): bump the minor-and-patch group across 1 directory with 6 updates — johnmathews/journal-server0 reactions
Oct 3, 2026Update garminconnect requirement from >=0.3.11 to >=0.3.17 in /fetcher — Imgrund/hybridlog0 reactions · 2 comments
Oct 2, 2026Bump garminconnect from 0.2.26 to 0.3.5 — eltrain13/garmin-grafana0 reactions
Oct 1, 2026Bump garminconnect from 0.2.36 to 0.3.16 — tracpants/step-tracker-20260 reactions
Sep 25, 2026Feature request: download and import Garmin Connect Lifestyle Logging data — tcgoetz/GarminDB0 reactions · 5 comments
Sep 25, 2026chore(deps): bump the uv group across 1 directory with 2 updates — cvitan/paicer0 reactions
Sep 24, 2026fix(auth): login writes garth tokens that garminconnect 0.3 cannot read — dbhq-uk/garmin-skill0 reactions · 1 comment
Sep 22, 2026[GARMIN] Measure login strategy outcomes before changing skip policy — Szczepanov/adaptive-training-recommender0 reactions
Sep 22, 2026Fix auth flow since garth is deprecated — alexandru-dinu/garmin-stats0 reactions
Sep 14, 2026deps: bump garminconnect from 0.3.11 to 0.3.13 — aidiaz/soma0 reactions

On Bluesky · 2

Jan 2, 2025The Garmin library ( https://github.com/cyberjunky/python-garminconnect ) works great, but IIUC it is not using a public API, but basically… — @kajord.bsky.social1 likes and repost · 1 reply
Jan 2, 2025The Garmin library (https://github.com/cyberjunky/python-garminconnect) works great, but IIUC it is not using a public API, but basically… — @kajord.hachyderm.io.ap.brid.gy1 likes and repost · 1 reply

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free