RideReviewer
Learn
Get fasterHow to use RideReviewerCycling training analysisFind your current limiterComing soon
Understand recoveryWhen endurance rides become tempoRecovery between hard ridesComing soon
Train with heart rateCycling training zonesHeart rate higher than usual
Train with powerPower durability across ridesComing soonCompare repeated effortsComing soon
Connect your ridesGarmin cycling analysisIntervals.icu cycling analysis
How to useReview My Intervals.icu Rides →

Analyze your Intervals.icu rides in ChatGPT or Claude

Use RideReviewer to compare recent cycling sessions, explore recurring patterns, and decide what to try next. Add your goals, how the rides felt, and the time you have available to the conversation.

Review My Intervals.icu RidesRead-only connection · Up to 30 recent rides on initial import

Start with a question about your riding

  1. “Compare my recent endurance rides. Are they staying easy, or repeatedly becoming harder than intended? Show the evidence and what remains uncertain.”

  2. “Compare similar recent rides. What changed in power and heart rate, where those metrics are available? What else do you need to know before interpreting the difference?”

  3. “I have three hours to ride this week. Based on my recent rides and my goal, suggest one practical experiment and explain why.”

An example of the analysis approach: When endurance rides become tempo.

How to use Intervals.icu with RideReviewer

  1. 1

    Get your access code.

    Enter your email to get started.

  2. 2

    Open RideReviewer in ChatGPT or Claude.

  3. 3

    Connect Intervals.icu.

    Choose it as your active source and authorize read-only access.

  4. 4

    Ask your first question.

    Start with one of the examples above and add your goal or recent riding context.

A focused history of completed cycling activities

Authorization is read-only and limited to completed cycling activities. RideReviewer does not request wellness, calendar, or workout-writing access.

After OAuth completes, RideReviewer automatically imports at most 30 recent completed cycling activities. The initial search is bounded to 365 days, including outdoor, indoor, and virtual cycling when those activities are present. Later rides are brought in only when you request a manual refresh.

It compares relevant rides across duration, sequence, heart-rate response, elevation, speed or pace, and available power or cadence. Missing metrics remain unavailable rather than being inferred.

RideReviewer keeps Garmin and Intervals.icu histories separate. You can have one active source at a time; switching sources does not merge their imported histories.

For question patterns that work across either client, use the RideReviewer prompt playbook. If Garmin is your source, see the distinct guide to Garmin cycling analysis. For the analysis method itself, read how RideReviewer compares patterns across rides.

FAQ

Before you connect Intervals.icu

What does RideReviewer read from Intervals.icu?

Only completed cycling activities used for ride analysis. It does not read wellness data and does not write calendars or workouts.

How many rides are imported?

The automatic initial import includes at most 30 recent completed cycling activities. You can manually refresh later to bring in newer rides.

Can I use both Garmin and Intervals.icu at once?

You can connect both over time, but only one source can be active at a time. Their imported histories stay separate and are not merged.

Can I use the connection in ChatGPT and Claude?

Yes. RideReviewer supports the same source-neutral ride-analysis workflow through ChatGPT and Claude.

Does RideReviewer change anything in Intervals.icu?

No. The OAuth connection is read-only. RideReviewer does not write wellness data, calendar entries, or workouts.