Activity
Mon
Wed
Fri
Sun
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
What is this?
Less
More

Memberships

Athlete AI Community

231 members • Free

2 contributions to Athlete AI Community
Codex and Garmin Connect
Hi Kevin, everyone 👋 Really loving this community, and glad I stumbled upon it as an AI and sporting enthusiast. One question, as I was following along wonder whether anyone has gone the Codex and Garmin Connect route? These are the tools I have been using in my AI journey and not sure whether worth switching to using Claude (and Strava as source).
@Kevin Rudd any specific reason you revert backl to Codex after coding it up in Claude Code?
@Kevin Rudd Totally get the switch-cost thing, same here, Claude Code as daily driver is hard to leave. But on the context-window worry: the thing that helped me most wasn't a bigger window, it was needing it less. Instead of building the whole feature in one context, I offload the heavy lifting to helpers and keep only their summaries. Main context stays clean, so compaction stops being the thing you dread, and it makes the 1M vs 400k gap matter a lot less. Two patterns I lean on: - Sub-agents; a helper spun up for one job (read the big file, trace the data flow, do the research). Runs in its own context, hands back a short summary, then it's gone. One-shot and disposable - the main context never sees the hundred pages behind the answer. - Swarms; persistent helpers with fixed roles that stick around. They keep their memory and their role across the task, so you can coordinate them and pass work back and forth. For bigger builds where several "people" need to pull together over time. Net effect: the main context holds the plan and the conclusions, not the raw material. I've run full-day sessions this way without hitting the wall. Haven't pushed Codex hard myself yet — but if the 400k window is the main blocker, this pattern basically sidesteps it. The thing I'd test first is whether Codex's sub-agent tooling is as clean as Claude's.
I had my AI red-team the Garmin setup — here's a hardened version (Win + Mac)
(works with any AI you use) Like many of you I wanted my Garmin recovery data (sleep, HRV, resting HR, body battery) going into my AI coach — it's the data Strava can't give you, and for me it changed the conversation from "how far did you run" to "why was your Wednesday night 4.5 hours of sleep." Before running the setup from the classroom guide, I did what the guide itself kind of teaches us: I asked my AI to review it first — and then to red-team the result. A proper adversarial security review. It found real things worth fixing before I'd type my Garmin password anywhere. So we rebuilt it, audited it, and I'm sharing the result so you don't have to choose between your data and your peace of mind. Same idea, same open-source library (python-garminconnect), one script — but hardened: - Read-only, and provably local. The only network connection is to Garmin. No upload endpoints, no analytics. The script is ~350 lines — you (or your AI) can read every one. - Your password is typed once, hidden, never stored — not in files, not in environment variables, not in your shell history. The script even refuses to run in terminals that can't hide your password. - Your login token never gets printed and is saved with locked-down permissions. (A printed token = a year of account access sitting in your terminal scrollback.) - Dependencies pinned to exact versions, so a compromised future release of some library can't silently install itself on your machine. - Smarter failure behavior: if the network is down, it tells you it's the network — so you never get trained into re-typing your password "just in case." That habit is exactly what phishing lives on. What you get: a garmin/ folder of clean markdown notes — one wellness note per day, one per workout, plus a data.json. Point your AI coach at it and every morning it knows how you slept before it tells you what to do. Setup: unzip, follow the README. Five minutes, Windows and Mac covered, including how to schedule it to run automatically every morning (with catch-up for days your machine was off). The only thing you ever type is your Garmin login, once.
PS. Feel free to use it, copy it and improve on it. If you need for Linux or WSL just let me know.
1-2 of 2
Patrick Laake-Bjurquist
2
14points to level up
@patrick-laake-bjurquist-3153
Training to out-run the demons ;-)

Active 11h ago
Joined Jul 3, 2026
Powered by