Plan your next race with Claude on your own record

Journal · 2026-09-15 · R. Klug · All notes

Read in: Deutsch · Français · Español · Italiano

An assistant planning your marathon block is only as good as what it knows about you. Give it a race date and a weekly mileage and you get a template. Give it your actual record — months of nights, every session with heart rate and raw beat intervals, how your body responded to the last hard week — and the conversation changes category. That is what the ampulse connector is for: your record, in your assistant’s hands, placed there by you.

The setup, in three steps

• Record as usual. Loop on the wrist for nights, a chest strap for sessions, the PM5 or FTMS machine when you’re indoors. Everything lands as files on your iPhone.
• Link a folder. In ampulse, Settings → Connect Your AI links a folder the app keeps current — an iCloud Drive folder reaches your Mac by itself.
• Install the connector. Download ampulse.mcpb, double-click, and pick that folder when Claude Desktop asks. The connector is a local, read-only MCP server with fifteen tools — Claude retrieves exactly the records your questions need.

What planning on a record looks like

Training for a marathon, a half or a 10k, the working loop is weekly: you ask, Claude reads, you decide.

• “Review last week against the plan — sessions, nights, and how heart rate at easy pace compared to the previous three weeks.”
• “Build week 6 of the half-marathon block. Respect what the record shows about how I absorb back-to-back quality days.”
• “Compare this season’s long runs at 4:45/km with last season’s. What changed in heart rate drift?”
• “Why did Tuesday feel so hard? Read the session and the nights around it.”

Because the connector serves session intervals, night data, heart rate, power and GPS — not just weekly totals — the answers can cite actual measurements. And the plan can come back as artifacts you use directly: a week as a table, workouts as .zwo files ready for Zwift, or interval schemes for the erg. Ask for the format and the assistant writes it.

Built like everything else in ampulse

The connector runs on your computer and reads files — there is no ampulse relay and no health-data server in between. What you ask Claude to read is shared with the assistant provider, like anything you put in a conversation, and the folder reflects your latest completed export rather than a live sensor feed. The same mechanism works beyond Claude Desktop: the AI dossier is a Markdown file you can hand to any assistant that accepts files. In every variant, the record leaves your device only by your hand.

One habit worth keeping

Treat the assistant’s plan the way ampulse treats a sensor: as a signal with a quality check. Check important conclusions against the underlying record — the numbers are right there, and being able to open them is the point of the whole setup.

Full connector details and requirements are on the connector page.