Claude + Intervals.icu

Claude as an Intervals.icu coach with real training data

Claude can reason well, but it should not coach from memory or copied screenshots. STAS connects Claude to Intervals.icu so it can review real workouts, current load, fatigue, calendar context, and planning rules before giving advice.

Connect Intervals.icu

Quick answer

If your training already lives in Intervals.icu, the best Claude setup is not a long prompt. Connect STAS, let Claude read the prepared training context, then ask focused questions about condition, the next workout, or the current week.

Intervals.icu stays the training data and calendar source.
STAS prepares workout history, fitness, fatigue, form, and plan context.
Claude can explain decisions instead of only generating a static plan.
When you approve a plan, STAS can write it back to the Intervals.icu calendar.

Why Claude needs Intervals.icu data

A generic Claude answer can sound confident while missing the facts that matter for training.

Recent load matters

The same workout can be fine after an easy week and risky after a heavy block.

The calendar matters

Claude should know what is already planned before it suggests another hard session.

Sport mix matters

Cycling, strength, long runs, and easy days all affect fatigue differently.

Your rules matter

Time limits, race goals, travel, and recovery preferences change the right answer.

What STAS gives Claude

STAS is the bridge between raw Intervals.icu data and a useful coaching conversation.

Training history

Recent workouts, weekly volume, intensity, pace, heart rate, laps, and sport breakdown.

Fitness context

Fitness, fatigue, form, current condition, and trend signals from Intervals.icu data.

Planning context

Current calendar events, goals, strategy, and the practical constraints you have saved in STAS.

Write-back actions

Claude can help create or rewrite plan events, and STAS can save approved changes to Intervals.icu.

Recommended setup

Connect your watch to Intervals.icu

Use Garmin, COROS, Suunto, Polar, Amazfit, Apple Watch bridges, or another route that keeps workouts in Intervals.icu.

Connect STAS to Intervals.icu

STAS reads the training data and prepares a coach-friendly context layer for Claude.

Add STAS as a Claude connector

Open the Claude.ai card in your STAS profile and add the connector from Claude settings.

Ask for a concrete review

Start with current condition, the next workout, or a week rewrite instead of asking for a generic plan.

What changes compared with plain Claude?

Plain Claude

Good reasoning, but it depends on what you paste into the chat and can miss training history.

Claude with STAS

Claude sees structured Intervals.icu context and can discuss the actual plan and recent load.

Best use case

Use it when you want an explanation, a plan adjustment, or a safer decision around fatigue.

FAQ

Can Claude read Intervals.icu directly?

Not in a useful coaching flow by default. STAS gives Claude a structured connector to the training context in Intervals.icu.

Is this only for runners?

Running is the main entry point, but STAS can also handle cycling and mixed endurance weeks when the data is in Intervals.icu.

Can Claude write workouts back to Intervals.icu?

Yes, through STAS plan actions. You should review the result before relying on it as your training calendar.

Do I need Telegram for this to work?

No. Intervals.icu plus Claude is enough for the first useful result. Telegram adds reports and daily context later.

Let Claude coach from your real Intervals.icu data

Connect Intervals.icu to STAS, then use Claude with workout history, fatigue context, and the current calendar instead of pasted summaries.