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 →

Turn Intervals.icu Rides Into Clear Training Decisions

RideReviewer can compare your completed cycling activities to find a recurring pattern, suggest a likely limiter, and propose one experiment to test next.

Review My Intervals.icu RidesConnect through read-only OAuth. Initial import: up to 30 recent rides.

What the connection reads—and what it never writes

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

Completed cycling activities

RideReviewer reads completed rides needed for your analysis.

No wellness data

Wellness information is outside this connection.

No calendar writes

RideReviewer does not add or change calendar entries.

No workout writes

RideReviewer does not create or edit workouts in Intervals.icu.

Connection flow

Import once, then refresh when you want new rides

After OAuth completes, RideReviewer automatically imports at most 30 recent completed cycling activities. Later rides are brought in only when you request a manual refresh.

A focused history of completed cycling activities

RideReviewer uses completed cycling activities as training evidence. The initial import is capped at 30 recent rides, including outdoor, indoor, and virtual cycling when those activities are present.

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.

Ask about your rides in ChatGPT or Claude

RideReviewer delivers the same source-neutral analysis workflow through ChatGPT and Claude: observed evidence, a cautious interpretation, visible limitations, and one practical experiment to test next.

For question patterns that work across either client, use the RideReviewer prompt playbook.

Choose one active ride source at a time

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.

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.

How to start

  1. 1Get your access code.
  2. 2Open RideReviewer in ChatGPT or Claude.
  3. 3Choose Intervals.icu and authorize read-only access.

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.