Plan your season in Intervals.icu
with an AI assistant.
A cycling season has a shape before it has a single workout: the races you are aiming at, the weeks you will be away, the weeks an illness or an injury takes, and roughly how much you mean to ride in a week. Intervals.icu keeps all of that on the calendar beside your planned workouts. Getting it there has meant adding each item by hand.
Since 23 October 2026 your assistant can do it in conversation. Through IntervalSync it can add, change and remove a race, a note, a weekly target, a holiday, and a sick or injured period, and plan workouts beside them. It shows you each item first and sends nothing until you confirm. It does not decide your season. You do, and it writes down what you decided.
What can go on the calendar
Three tools handle calendar items, which are not workouts: create_calendar_item, update_calendar_item and delete_calendar_item. Each item has a category, a name and a start date.
| On your calendar | Category | What it takes |
|---|---|---|
| A race | RACE_A, RACE_B or RACE_C | A date. The letter is its priority. |
| A note | NOTE | A date and some text. |
| A weekly target | TARGET | Load, riding time, distance, or any of them. |
| A holiday | HOLIDAY | A start and an end. |
| A sick period | SICK | A start and an end. |
| An injured period | INJURED | A start and an end. |
- A period ends on an exclusive date, so a week of illness through Sunday ends on the Monday. Without an end it lasts one day, and none can run longer than 28 days.
- A weekly target takes a load (TSS) up to 10,000, a riding time up to 168 hours and a distance up to 2,000 km, and a new one needs at least one above zero. Time goes in as seconds and distance as metres, so 10 hours is 36,000: check the figures before you confirm.
- A race cannot be dated before the previous UTC day, which leaves room for your own evening.
Workouts stay with their own tools. list_planned_workouts reads the calendar, create_planned_workout adds a workout, and update_planned_workout and delete_planned_workout change or remove one. Each set refuses the other's kind of event. The calendar is read for the next 28 days unless dates are named, so for a season they must be.
The order that works
1. Save your goal and constraints first
Your training context is five sections kept in your IntervalSync account, in your words: goal, events, constraints, preferences and notes. Every assistant you connect reads it, so Claude on the laptop and ChatGPT on the phone start from the same page. A section is saved when you ask or agree, holds up to 4,000 characters, and a save returns the text it replaced. The Training Context page of your portal shows each section and who saved it, and removes any of it. It writes nothing to Intervals.icu and works on every plan.
The goal is what you are training for and its date. The constraints are the hours you have, your equipment, and anything to train around. Races listed under events are words your assistants can read. They are not on your Intervals.icu calendar.
2. Add the races
Put the A race on the calendar first, then the B and C races, each with a name and a date. Moving one later, or changing it from A to B, updates the same item.
3. Add the time away
A holiday or a work trip is a period. A training camp can be a note on its date.
4. Ask for the block structure, in words
Now ask how the weeks between the races could divide into blocks, what each is for, and a weekly load, time and distance for it. Nothing is written in this step. Ask what each figure rests on in your recent training and what is a guess. A weekly review later shows how the riding compared with the plan.
5. Write only what you confirmed
Then the writes, each item shown with its category, name, dates and values. Check a target's units and a period's last day before you say yes.
A prompt that plans and writes nothing
Replace the placeholders. It reads and proposes, and asks before each write. The prompt library has more.
I am planning my [YEAR] cycling season on my Intervals.icu calendar. First read my saved training context and tell me what it holds for my goal, events, constraints and preferences; ask about anything missing. Then read my calendar from [START DATE] through [END DATE] and list every race, note, target, holiday and planned workout already on it. Next, without writing anything, propose in words: the races to add, each with an A, B or C priority and a date; the time I will be away; and the blocks between the races, with the length and purpose of each and a weekly load, riding time and distance target. Say what each figure rests on in my recent training and what you are guessing. Do not change my calendar or my training context yet. When I agree to a part, show me each item you would add, with its category, name, dates and values, and send it only after I confirm that item.
Changing the plan, and when you are ill
To move a race, lengthen a holiday or adjust a target, your assistant lists the calendar for those dates without a category filter and reads the item's numeric id. An update changes only what you ask. The item's other fields, including a period's end, a target's values and its training availability, are sent back as they were. The answer carries the values it replaced, reads the item back from Intervals.icu, and flags any field that came back different or empty. Only a race can change category, and only between A, B and C. Each item has a stable id, so a retry updates it instead of adding a second.
When you fall ill mid-block, a sick period records it from the first day. It adds only that item: workouts planned on those days stay where they are, and update_planned_workout can give one a new date. It is a record, not medical advice. Whether to ride is for you and, if needed, a doctor.
Deleting is not like the rest
One item is deleted per call, confirmed by its category, name and date. Intervals.icu keeps no trash, so a deleted item is gone for good. The tool returns the item's full record, the only copy left, so one deleted by mistake can be added again from it. It then reads the calendar to check the item is gone. delete_planned_workout works the same way for workouts.
What it cannot do
- It does not decide your training. The blocks, the targets and which race counts as A are proposals from what it reads, and your call. IntervalSync only writes what you confirm.
- A deleted item is gone. There is no undo, and each call removes one item.
- It cannot add a race to a rider's calendar. These tools act on your own calendar. A coach's assistant can plan a rider's workouts if the rider allows it, but not their races, holidays or sick periods, and it never reads the rider's saved training context. How a Coach plan works has the rest.
Turning it on
Reading the calendar works on every plan. Adding, changing and deleting items and workouts come with the full-access trial, with Pro and with a Coach plan, and use the Calendar write permission you give IntervalSync when you sign in with Intervals.icu. A connection that already allows calendar changes needs nothing new. A read-only one needs Refresh Intervals permissions once, on the AI Vendor Connections page of your portal. If an answer is lost, look at the calendar in Intervals.icu before asking again.
To connect your assistant, follow the ChatGPT, Claude, Gemini or Grok guide.
Every tool your assistant can use · More prompts · All articles · Connect your training