What's new

The session list, the sidebar and the session page briefly showed Greenwich time before switching to yours, and the browser logged an error when opening the site. Times now arrive in your time zone, and the list's days follow your own midnight.

In Chrome with WebMCP, the browser's own agent now sees your account tools when you are signed in: who you are, your sessions, and publishing or hiding a session.

It can also filter the sessions list by kind, driver or only yours, and the filters live in the page address, so you can keep or share the link. Answers come in the MCP format, with structured data instead of pasted text.

Your agent (Claude Code, Cursor or any MCP client) can now use the site's MCP with your account's token. It then sees your private sessions and gets three new tools: who am I (account and upload quota), my sessions (each marked public or private) and change the visibility of one of your sessions.

Only you can change your sessions: someone else's agent gets "forbidden". Without the token, the site's MCP stays read-only, and guest accounts cannot connect an agent. How to get the token and add it to Claude Code is in "Connect your agent".

The site address is enough for an agent to find the MCP server: the app publishes its catalog at /.well-known/ai-catalog.json, the server card at /mcp/server-card and an llms.txt whose tool list is generated from the real server, so it never goes stale.

The server also introduces itself on connect: what it is, where to start and its limits.

Google sign-in is ready and shows up on the site as soon as the Google account is switched on on the server. Once it is live:

• Continue with Google sits at the top of Sign in and Create account. One click, pick the account and you are back on the page you were on.
• One tap. With Google already open in your browser, Google itself offers to sign you in from the corner of the screen, without leaving the page.
• Same account. If you already have an account here with the same e-mail as your Google account, you land in it, with your sessions and saved laps. The Google e-mail counts as confirmed.
• Guests lose nothing. A guest who signs in with Google keeps what they already did.
• Your Google photo and name show up in the account menu.

E-mail and password keep working as before.

Release notes now open inside the app, keeping the sidebar (on desktop) and the tabs (on mobile): tap What's new in the sidebar or the sparkle icon at the top of Sessions.

On the site, What's new joined the header. In both places the New badge lights up when a note you have not seen comes out, and goes away once you open the page.

With sign-up open, the site got several layers of protection. All in one place:

• Private sessions by default. What you upload only shows up for you until you tap Publish. Profile, driver list, API and your agent follow the same rule.
• Saved laps have an owner. Each account sees, edits and deletes only its own laps.
• Anti-bot verification (Cloudflare Turnstile) on sign-up and login, plus an attempt limit per account and per address to stop anyone guessing passwords.
• Per-account quotas: up to 50 MB per file, 200 files per day and 2 GB in total. If you go over, the upload says which limit you hit.
• Site behind Cloudflare. Every request goes through it, and the app server only accepts connections that arrive that way.
• Admin panel. Whoever runs the site sees each account's usage, blocks accounts that abuse it and deletes what they uploaded.
• Your agent only sees what is yours. The agent cursor uses a pairing code, and each code only sees the activity of its own account or its own machine. Without a code, nobody gets anything.
• MCP on your machine. Running the app locally without login, the agent gets every tool (saving laps and importing included), but only from inside your own computer. Over the internet, MCP still needs an account.

Switch the language in the EN / PT selector and everything follows: home page, sessions, telemetry, map, comparison, saved laps, import, notices, the Racing Line (HUD and race moments), the coach report and the Where you lose table.

Dates, numbers and session names follow the chosen language. These release notes have an English version too; a note without a translation shows in Portuguese.

The LMU Harness code is published under the FSL-1.1-MIT (Functional Source License). You can read, run, modify and use the app for yourself or your team; what the license does not allow is offering a competing service with it. Two years after each version, that code becomes MIT.

The repository has a README in English and Portuguese, a guide to connect agents (docs/agents.md), a contributing guide and a security policy to report issues privately.

The home page now shows how to run LMU Harness on your own computer: it reads your Le Mans Ultimate logs straight from disk, and your agent (Claude Code, Codex, Cursor or any MCP client) works with you over local MCP.

The Install section has the commands, and Agents shows how to hook up each client. If you just want to look, the live demo link is still there.

On the iPhone app, laps that come only from the lite replay (.lmur) now carry the same "from replay" label as .Vcr laps. The /api/v1/telemetry error message for a missing lap now shows how to ask for one.

Anyone arriving at LMU App now finds a home page that shows what you can do here before landing on the session list.

And this page was born: every new delivery gets a note here, in plain language. When there is news you have not seen yet, a New dot shows up in the menu.

The home page downloads half of what it used to: it no longer carries the session list, draws the track animation in the browser and arrives compressed. The in-browser agent features (WebMCP) only load when the browser supports them, after the page finishes opening.

The home page, What's new, sign-in and the uploader approval now open as site pages, with the site header and footer. The sidebar and the top bar stay in the app only: sessions, laps, comparison, import and saved.

Sign-up is now open to everyone, and with it come a few rules to keep the site fast and safe:

• Private sessions by default. What you upload now only shows up for you: in the list, on the session page, in the API and to your agent. When you want to show it, tap Publish on the session page (and Make private to hide it again). Sessions that were already on the site stay public.
• Per-account limits: up to 50 MB per file, 200 files per day and 2 GB in total. If you go over, the upload tells you why.
• Anti-bot verification on sign-up and login, and an attempt limit to stop anyone trying to guess passwords.
• Saved laps and driver are yours. Each account sees, edits and deletes only its own laps and picks its own driver (the "You" in the sidebar).
• Continue without an account. You can enter as a guest to browse sessions and save laps, without uploading files. A guest account goes away after 7 days without use; create an account to keep everything.

Cloned the repo? bun install && bun run start and the app opens at http://localhost:3000, with no account or login. It finds the Le Mans Ultimate folders on your computer, imports the new sessions and keeps watching while it runs.

To connect your agent: claude mcp add --transport http lmu http://localhost:3000/mcp. Codex, Cursor and the others are in docs/agents.md.

The site has two new pages, linked in the footer:

• Privacy (/privacidade): what we collect (e-mail, name, the logs you upload and the IP to limit abuse), who else handles it (Cloudflare, Resend and Google, if you sign in with Google) and how to delete your account.
• Terms (/termos): the rules for using the hosted site.

The home page opens with the studio in action: an agent asks where you lose time, calls the tools, and the track, the telemetry and the guilty corner light up as the answers arrive.

Further down, a full lap runs as you scroll, with you and the leader side by side, the delta growing and, at the end, the replay going back to the corner where the time is. The final call ends with the start lights.

If your system asks to reduce motion, everything stays still, already on the final frame.

You can connect Claude (or another agent) straight to the app over MCP at /mcp. It lists your sessions, reads laps and telemetry, compares laps and brings the coaching report, all read-only.

In Chrome with WebMCP, the browser agent also drives the app: it opens a session, compares your lap with the leader's and filters the sessions of a driver.

And to send sessions from an agent or the terminal, the step-by-step is at /import and /llms.txt.

The home page now shows the cursors of everyone looking at it with you, each with a color and a numbered "Driver". A small counter shows how many people are here now, and the eye button hides the cursors (remembered). No name, IP or account: only the mouse position, which disappears when you leave. Cursors stay hidden on phones.

When your agent (Claude Code, Codex, Cursor or another MCP client) calls a tool, a purple Agent cursor shows up in the open app and moves to what it is reading: the telemetry for compare_laps, the coach card for get_coach_report, the session list for list_sessions.

If the agent is looking at another session, the app asks whether you want to Follow instead of switching pages on its own. On your machine it works with no setup; on a hosted app, use the code under Connect an agent in the sidebar.

The app got lighter everywhere. A session page leaves the server in about 15 ms (it was ~43 ms) and the 3D replay in ~20 ms (it was ~247 ms).

Hovered a session? The app already starts fetching the data, and the click opens right away, without waiting for the server again. When something takes a while, you see the page skeleton and a progress bar at the top instead of a frozen screen.

Telemetry also arrives compressed: downloads are about 9 times smaller.

On a phone, the robot icon at the top of Sessions opens Connect an agent: pairing code, copy button, New code, the MCP URL and whether the agent is connected.

The agent cursor and the Follow prompt now sit above the tabs and stay on screen.

Before, comparing your lap with another driver's needed the replay .Vcr file, which is heavy and is not kept in the cloud. Now lap-by-lap comparison and Where you lose time work with the lite replay the Uploader already sends.

Telemetry comes at 10 Hz and barely changes: the average speed difference from the original replay is 0.05 km/h. Lap time, braking points and stretches match.

The app is still open to everyone, but now you can sign in with an account. Signing in gets you:

• Sent by on every session, so you know who that file came from.
• The Mine filter, with only the sessions you sent.
• Connect account in the LMU Uploader: approve once in the browser and your next uploads go out under your name.

And if the internet drops mid-upload, the Uploader retries on its own until the session is up.

In the sidebar, click a driver's name under Drivers and the session list shows only the races and practices they drove.

Handy to find that race of your teammate or to study who runs up front. To go back to the full list, just close the Driver filter at the top of the list.

The app moved off one driver's PC and now runs in the cloud: just open the link, nothing to install.

To send your races, download the LMU Uploader for Windows. It finds the game folders on its own and you choose which sessions to send.

• The replay is processed on your PC before it goes up, so the upload is light and fast.
• Sessions you already sent are marked, with no duplicates.

P1 at Fuji Speedway, 12 laps, 20 cars on the grid and a Mercedes-AMG LMGT3 ahead of everyone. The whole race is in the app: results, telemetry and replay.

• Open the session and see lap by lap where the win was built.
• Compare your laps with Henrique's, corner by corner.
• Watch the race again on the Racing Line, in 3D.