Most of what changes here comes from watching real routes go wrong.
When a request produced a bad route or no route at all, this is where the fix
is written down. Newest first.
24 October 2026
Owner funnel. Live milestones, problems, retention and hourly activity now have period filters and count drill-downs.
23 October 2026
First-party analytics. Usage events stay on our server,
retry after connection failures, and exclude chat text and place names.
Saves and shares are counted where they succeed. Owner devices are
excluded from conversion and return-visit measurements.
12 October 2026
Repeat downloads keep their scope. Downloading a multi-day
GPX again still includes every day. Changing the route reopens the format
choices for the new version.
Refinements stay readable. The short change summary stays
visible in folded chat alongside later routing warnings.
Save explains sign-in. Signed-out riders can open the
sign-in explanation directly from the route's Save control.
Clearer dark mode and keyboard access. Chat, buttons and
input hints have stronger contrast. The information pages follow your
system appearance. Examples work with the keyboard, dialogs return focus
when closed, and typing Undo in the command box edits your text.
Restored routes open safely on phones. A route whose
measurements are still missing shows “View route” until they are ready.
11 October 2026
A star is now a star. A rider asked for a route in the
shape of a star and got a zigzag of towns, because place names cannot
draw a picture. Stars, hearts, circles, squares and triangles are now
worked out as geometry around the place you name, at the width or length
you ask for, and the roads are fitted to it. Ask for it bigger, turned or
moved and it is redrawn. Any other picture, a letter, a cat, a house,
is drawn from an outline the assistant sketches, as a simple paper
cut-out. A shape can start at your address or your current position
and finish somewhere else, and a corner that lands off the road network
is dropped instead of failing the whole picture. Hate symbols and
obscenities are refused.
"Around me" asks first. The button used to plan a
default loop the moment it found you. It now says where you are and
asks what you want from there.
Type while it plans. The box no longer locks while a
route is being built: a message typed then is sent as soon as the route
is ready, and the app's own corrective notes no longer appear as if you
had written them.
Straight edges follow the line. Routing between two
far-apart corners takes the fastest road, which wanders off the line you
wanted. Each edge is now routed plainly first and, when that strays from
the line, again through up to six intermediate points; the straighter
of the two is kept unless it costs half as much distance again. The
extra points are not stops and do not appear in the list. A shape that
comes out much longer than asked is shrunk once to fit.
Hide the route panel. On a desktop the panel on the
right now has a handle on its left edge. One click hides it and gives the
whole width to the map, and the handle stays at the edge of the window to
bring it back.
10 October 2026
Chat on the left, route on the right. On a desktop the
conversation and the route details no longer share one column. The left
panel is the chat with the composer under it, the map sits in the middle,
and once a route exists its distance, climb, profile, stops, weather and
download buttons open in a panel of their own on the right. The footer
links sit under the composer instead of behind it. Phones are unchanged.
What cannot be routed is said on the first turn. A rider
near Lahti asked fifteen times for 100 km on cross-country ski tracks
only, and got fifteen ordinary gravel loops with no word about why. The
router follows OpenStreetMap roads and paths and cannot be restricted to
ski tracks, pistes, one trail type, or a route drawn as a shape. A quick
check now reads every request for that kind of ask, and the reply says
plainly what was not possible and what was planned instead.
The panel is a conversation until there is a route. A
rider asked for a 50 km ride "in a form of a cat", was asked which town
to start from, and saw an empty panel: a reply with no route in it was
not shown, and their answer "gdansk" went into a box that still said
"Describe the route you want". Before a route exists, the panel now shows
the exchange as it happens, with a "Use my location" tap under a
question about where to start. Once the route is built it folds to the
last line above the figures, and "Show chat" opens it again. On a
desktop the box you type in now sits under that conversation, in the
panel, instead of floating over the map.
A newer planning model. Routes are now planned by a
model released in September, at half the cost of the previous one and the
same speed, and more honest about what it has not been able to do.
5 October 2026
Places along the way. Under the distance figures, "Find"
lists what OpenStreetMap knows within 250 m of your route: viewpoints,
castles, lakes, waterfalls, cafés, bakeries, drinking water, shelters,
picnic sites, each with its km along the ride. Tap one to see it on the
map, or add it as a stop and the route goes through it. While the list
is open, "take me past a café" picks a real one by name. Nothing is
looked up until you ask.
"About an hour" is a distance now. A stroller walk
"for approximately an hour" in Bredene came out at 2 km, and a "3 hours
exactly" ride in Mallorca had no target at all, because only distances
were read. A duration now sets the distance at the activity's pace,
and the route is stretched or shortened to it like any other.
A route 10% short is stretched. 26 km for a 30 km ask
and 35 for 40 used to pass, because a bare "30 km" allowed 15% either
way. The margin is 10% now, the same one the app uses before it tells
you a route is off.
Where the roads run out, the planner says so. A 30 km
loop in Matina, Costa Rica came back at 53 km with 45% on the same
roads, twice. When a fix for that fails because the map simply has no
other roads, the reply now says that a loop this size is not on the
map here, instead of offering to try harder.
2 October 2026
Motorcycle routes. A rider near Buffalo asked for a
motorcycle loop and was routed onto bike trails, eight times over,
because every profile was a bicycle or a pair of boots. Say motorcycle,
motorbike or scooter and the route now follows roads for motor vehicles,
with a choice of fastest roads or back roads without motorways. The
wind panel steps aside, the clothing advice is for a jacket and gloves,
and a FIT export is filed as motorcycling.
An assistant can no longer claim a change it did not make.
When a route is changed through ChatGPT or another assistant, the result
now carries the measured before and after: distance, repeated roads, and
a plain statement of anything that was asked for but not achieved. The
assistant is told to describe the change from those numbers.
A sight the map cannot find is left out, not swapped for the
town centre. "Salem Common" used to become "Salem", twice, with a
zero-length leg between. Such stops are now dropped and named as
unresolved, and the planner is asked for real places instead.
Assistant-planned routes get the same distance fixes as the
app: too long is shortened and too short is stretched by
measurement before the model is asked again. A date in the request sets
the departure for the wind and weather, and a walking route is reported
as walking.
1 October 2026
Route AI inside ChatGPT. Connected as an app, a planned
route now appears as a map in the chat, with its distance, climbing and
time, a Download GPX button, and one-tap requests to make it flatter,
longer or shorter. Route AI can also be opened from ChatGPT's sidebar as
a planner. No account is needed any more to plan through an assistant;
connecting one raises the daily limit.
Changing someone else's shared route now makes a copy.
An assistant given a shared link used to rewrite that route in place, for
whoever shared it. Only the route's own creator changes it in place.
A GPX uploaded to ChatGPT opens in Route AI, routed on
real roads and ready to change or export. Opening Route AI from the
ChatGPT sidebar shows your latest route.
A slow plan no longer times out in an assistant. When
routing takes longer than 25 seconds, the assistant is told the route is
on its way and the map card fills in by itself when it is ready.
30 September 2026
Weather, what to wear, and when to go. A rider asked for
it after a ride. Next to the wind, the route now shows the temperature
and rain along the way, whether you finish after dark, what to wear for
it, and a better time to set off when there clearly is one. You can also
just ask in the chat: "what should I wear?" or "when is it best to go?"
A street loop no longer detours to a village of the same
name. A walk between three streets in Vienna picked up a
"Jungenberg" 60 km away and came back as 158 km. A stop far from all the
others is now looked up again near them, even when no distance was
given.
24 September 2026
Downloading a GPX on a phone no longer wipes the
conversation. The phone reloads the page when it comes back from
the download, and the planner forgot what you had asked, including the
distance. "Another loop to the north" after a 200 km ride came back at
139 km. The conversation and the distance now survive the reload.
A loop that comes out short is stretched to fit. A 200 km
ask came back at 161 km, and asking again gave 172. The planner now
keeps the places it chose and widens the loop, measuring each try on the
real roads, until it lands on the distance you asked for.
The automatic check no longer stops after trimming a dead
end. Removing a dead-end stop quietly ended the check, so a
route the trim had left too short was never lengthened.
The keyboard comes back on iPhone. After a route was
built, tapping the message box sometimes showed only Paste and AutoFill.
The box now lets go while the route is being built, so the next tap
opens the keyboard.
22 September 2026
The loop trim stopped removing real stops. The check
added on the 19th also caught the short ride into a village centre and
back, and on a ride down one bank of the Main and back up the other it
dropped three villages and the river with them. It now only acts on a
detour of about 2 km that closes on itself, and never on the far end of
a loop.
A place the map cannot find goes via its town. "Kelkheimer
Stadtwald" and "Státní hrad a zámek Český Krumlov" both failed to
geocode and were dropped from the route. The planner now strips the
forest and castle words in German and Czech, and when a name still
cannot be placed it routes through the town named after it and says
so.
A second tap on the send button no longer cancels the plan.
Two riders stopped the planner within two seconds of sending, which is a
double tap, not a decision. A stop inside 1.5 seconds is ignored.
19 September 2026
Loops around a stop are trimmed. Asking for a route
through a forest put a stop at the forest's centre, off any track, and
the ride went in one way and out another: a loop of a few hundred metres
to a few kilometres that gained nothing. The old check only caught stops
the route rode to and back on the same road. It now also catches a stop
the route makes no progress through, and drops it.
A lake named as a stop lands on its shore. The stop used
to be the lake's centre, in the water, and the route rode out to the
nearest bank and back. It now goes to the shore on the side you arrive
from.
17 September 2026
A tap on the map no longer throws away a route that is still
being built. Geocoding and routing a city ride takes ten to
twenty seconds. A rider who tapped the map in that window started a
hand-drawn route and silently lost the planned one. The tap now says
so and waits.
"Three laps of the park" is answered honestly. A route
passes a place once, so the planner routes it once and says the laps are
yours to ride.
16 September 2026
A stop that lands in the wrong town is caught. Asking for
a loop from a bike shop in Murrieta placed the start at the same chain's
store 94 km away, and every other stop followed it. A stop that lands
farther away than the ride could reach is now looked up again near the
others, and falls back to the town named after it.
Stops just off the road network no longer fail the route.
A place pin inside a park or a fenced block is moved a few hundred metres
onto the nearest road instead of stopping with "island detected".
No more 0 km routes. When most of a plan's stops cannot be
found on the map, the planner asks for different ones instead of drawing a
route from the start to itself.
"12.5-mile", "7,5 km" and "40-km" now set the target.
Imported GPX files keep their shape. A 124 km gravel ride
used to come back as 97 km because only ten evenly spaced points were
kept. Points are now kept where the track bends, up to sixteen, and the
imported distance becomes the target. The automatic review no longer
rewrites a route you brought yourself.
"Around me" no longer sends twice. The request left its
text in the box, so it looked unsent and was sent again.
15 September 2026
"10k run" and "100 mile ride" are understood. A 10k run
with no recognised distance became a 608 km route.
A name that cannot be found is not tried again. The
planner remembers what failed to geocode in this trip and picks
elsewhere.
Import GPX stays reachable once a route exists, next to
the composer.
13 September 2026
A tour exports whole. Download GPX gives every day in one
file, one track per day; "This day" is still there. A rider planning a
300 km walk downloaded day one four times before we noticed.
Every day is drawn on the map, the other days faded.
My routes is its own page: search, thumbnails, open,
duplicate, share, export, delete.
A cleaner result panel: export actions stay in view, the repeated-roads
note is an offer rather than a warning, and the chips suggest what to
change next.
About and the AI-assistant setup are pages of their own.
12 September 2026
An over-long route is fixed by arithmetic first. The stop
that costs the most distance is dropped and the route measured again
before the model is asked.
The route is checked after every change, not once per trip.
The map gets the screen; the composer sits on it. Replies say what
changed rather than describe the route.
Earlier in September 2026
Improving an imported route keeps the route; a proposal that would
replace all your stops puts them back and says so.
A loop's stops are put in riding order before routing.
Asking for a beach stops at the beach, not at its village.
The reply comes back in the language you wrote in.