What it can see, and what it can change

The connector is a set of questions Claude or ChatGPT can ask your Garmin account, and a small set of things it can put there. This is the whole list, in the order you would think of them, with what each one never touches.

Last updated 30 September 2026

Reads: Health, sleep, readiness, activities, fitness markers, your plan
Writes: The workout library, and only that
Never: Your recorded runs, your route maps, your body composition

About today

The morning questions. Should today be hard or easy, did you sleep, where is your training load sitting. Three tools cover it.

Daily summary. Steps and distance, calories, resting and min and max heart rate, body battery high and low, stress, intensity minutes, blood oxygen. The same numbers as the Garmin Connect home screen for the day.
Sleep. Total time, the stages with durations and percentages, sleep score, overnight HRV, resting heart rate, awake count. Needs the watch worn overnight; otherwise it says so.
Readiness. Garmin’s training readiness score and the six factors behind it; training status (productive, maintaining, strained, recovery and the rest); acute against chronic load and the ratio between them; the four-week load focus with its targets; overnight HRV against your personal baseline; body battery, stress, resting heart rate and sleep folded in. One call, so the answer to “threshold today or tomorrow?” comes from evidence.

About a run

Every activity Garmin has, at three depths.

The list. Runs, rides, swims, strength sessions and anything else recorded, with distance, duration, pace per kilometre and mile, average and max heart rate, time in each heart-rate zone, cadence, training effect, and running dynamics and power when the watch records them. By count or by date range.
One activity in detail. Every lap or split with its own distance, pace, heart rate, cadence, dynamics and power, plus the full heart-rate time-in-zone for the session.
Inside the recording. The per-second data behind the laps. For any lap longer than five minutes: heart rate across the first third against the last, at the paces run, which is how cardiac drift and fitness show up. Kilometre splits derived for you when the watch did not lap by kilometre. The GPS route is deliberately not requested.

About your fitness

The markers Garmin computes from everything above, so goals and training paces can start from what your body is doing rather than from what you remember.

VO2 max and fitness age.
Race predictions for 5k, 10k, half and marathon, as finish times and the pace each implies.
Lactate threshold heart rate and pace, the anchor for tempo and threshold sessions.
Endurance score and hill score, with the class Garmin puts you in, read off the boundaries Garmin ships with the score.
Running tolerance, Garmin’s estimate of the weekly load your body currently handles.
Personal records, with the caveat that Garmin only knows races it timed itself.

About your plan

A training block as one thing. Claude designs the plan with you, from your goal and your fitness markers, and the connector builds and schedules every session in one go. Each workout carries a short plan code in its name, like Threshold 5x1k · HM, which is how the block is found again. The plan lives on your Garmin calendar and nowhere else.
How the plan is going, week by week: each session done, done on another day, missed, today or ahead, with the next session and what slipped in the last week. Sessions can be moved or retuned without leaving the plan.
Scheduled workouts on the Garmin calendar, and the library they come from.
Progress: which planned sessions actually happened, week by week. A session counts if it was run within a day either side of its date, because people move things and a plan that calls that a failure gets closed.
The plan chart, drawn as an image for the conversation: each day’s sessions beside what was planned.

What it can change

Writing is confined to the workout library: the structured sessions you would otherwise build by hand in Garmin Connect.

Create a workout from a list of steps with pace or heart-rate targets, or a strength session from Garmin’s exercise catalogue.
Update one in place, keeping its id, so the dates it is already scheduled on stay put and the watch picks up the new version at the next sync. This is how paces get retuned as you get fitter.
Schedule it on a date, which is what sends it to the watch, and unschedule it again without deleting it.
Delete a workout, behind a real gate: the first request only reads the name back, and removing it needs a second request quoting that name. Removing the rest of a plan works the same way, and keeps every session already past.

Nothing here touches your training history. No tool deletes, edits or renames a recorded activity, so a run you actually did cannot be lost through this however badly a request is worded.

What it never reads

Garmin exposes far more than this connector asks for. The following is available to it and deliberately not requested, today:

Where you were. GPS routes and maps are excluded from every request, including the per-second recording.
Your body. Weight, body composition, blood pressure, hydration, nutrition, menstrual and pregnancy tracking.
Your things and your people. Devices, gear, badges, challenges, connections and anything social.

If one of these would make the coaching better, it gets added in the open, on this page and in the code, before it is read.

Where the answers go

Each question is answered live from Garmin and returned into your conversation. The server keeps one encrypted token per person so it can ask on your behalf, and nothing of what comes back. The privacy page has the exact list of what is stored, and how to delete it.