You already plan your training with Claude.
It forgets by Tuesday.
Brick is the memory. Your season, your rules and every session you actually did — held in one place your agent can read, reason over, and change.
Built for self-coached triathletes and marathoners. Full MCP server, and a real app underneath for when you'd rather drag things around yourself.
The advice is fine. The amnesia isn't.
Your agent is genuinely good at reasoning about training. It just has no idea what week you're in, what you did on Saturday, or that you told it three conversations ago that Friday is a rest day. So every answer starts from zero, and half of them contradict the last one.
That should be fine as long as you're feeling recovered. Just be careful not to stack too much intensity in one block, and make sure you're getting enough rest around your key sessions. How has your week felt so far?
It depends where you are in your training plan. If you're in a build phase you might target threshold work; if you're recovering, keep it easy. What does your plan say for today?
Your long run is already on Sunday. Moving the ride there puts the day at 195 TSS against your 180 ceiling, and it's your third load week without a recovery. I can move it and trim Sunday's open water to 2,200 m, or put it on Friday — which your frame protects. Which?
You're in a recovery week — week 11, load down to 520 TSS. Today is 45 minutes at Z1. Keep it genuinely easy.
What your agent gets the moment it connects.
Not a chatbot bolted onto a training app. A full MCP server exposing the same operations the interface uses — so anything you can do by dragging, your agent can propose, and anything it proposes comes back as a diff you approve.
Block, week, phase
Which block you're in, how far through, whether this is a load week or a deload — the context that makes every other answer correct.
Actual, not planned
Sessions you completed, skipped or shortened, imported from Strava or a .fit file. Not what the plan hoped for.
Rules and ceilings
The daily and weekly ceilings you set, protected rest days, how many key sessions you'll take. It reasons against your rules, not general advice.
Load projected forward
Fitness, fatigue and form to race day, so "can I afford this" has a number instead of a vibe.
Thresholds and zones
FTP, threshold pace, CSS — with whether each was tested or estimated, so it knows how much to trust them.
Propose, never announce
Every change comes back as a diff with its cost — week load before and after, ramp before and after. Nothing moves until you say so.
For when you'd rather just drag it.
Saturday's brick on its way to Sunday. Before you let go, Brick tells you what the day becomes — 195 TSS against the 180 ceiling you set — and the footer is already objecting.
Swipe the week sideways →
You describe the shape. It fills the season.
Set which days hold key sessions, what's protected and how much load you'll take. Brick has no plans of its own — only yours, applied across every block to race day.
Swipe the frame sideways →
Get in early, and tell us what's missing.
Brick is being built in the open. The waitlist is a real one — a small first group who'll get access while it's still shapeable, and whose feature requests will actually change what gets built next.
No launch date promised, no drip campaign, no newsletter. One email when there's something to use.
It's worth saying who this isn't for:
- If you want your first training plan, use Runna. It's good at that.
- If you want to be told what to do today, this will feel like work.
- If a coach already writes your week, they have a tool.