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 19 October 2026
The morning questions. Should today be hard or easy, did you sleep, where is your training load sitting. Three tools cover it.
Every activity Garmin has, at three depths.
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.
Threshold 5x1k · HM,
which is how the block is found again. The block’s name, method,
phases and milestones are written into each workout’s notes, so
the card reads them back from Garmin. The plan lives on your Garmin
calendar and nowhere else.Writing is to the workout library, the structured sessions you would otherwise build by hand in Garmin Connect, and, only when you ask, to four details of a run you recorded.
Your training history stays as recorded. No tool deletes a recorded activity or changes what it measured: distance, time, heart rate, splits and route stay as your watch recorded them, so a run you actually did cannot be lost through this however badly a request is worded. When you ask, Daash can rename a run, write its notes, correct its type (a trail run logged as a road run) or set the shoes on it, and every answer says what it was before, so it can be put back.
Garmin exposes far more than this connector asks for. The following is available to it and deliberately not requested, today:
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.
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.