SetupsBeta

Your engineer tunes your setup with you

Ask what to change and why. Your Race Engineer combines the setup, telemetry, feedback and your own history before proposing a focused test for iRacing or Le Mans Ultimate.

Open Setups Read the docs 

Every recommendation is a hypothesis, not a guarantee. Validate each change on track before committing to it.

Setups

Setups you can talk to

Upload a setup once, then change it conversationally — every version tracked, every change explained.

  • Versioned Setup Vault

    A private home for your setups, organized with one optional session type and your own reusable tags. Every remix creates a new version with a clear diff against its parent — nothing is ever overwritten.

  • Contextual Setup Decisions

    Ask about camber, balance or a handling symptom. The engineer answers the setting you asked about first, may offer one verified alternative, and waits for an explicit request before changing anything.

  • iRacing

    Upload your garage export (.htm) and get every remix as a clear garage recipe — the exact changes to apply in-sim, ready to copy.

  • Le Mans Ultimate

    Upload your .svm and download every remix as a ready-to-load setup file. Full round trip, no manual steps.

A Recommendation Before a Change

The engineer assembles the evidence that exists for this exact decision, then gives you a small, testable hypothesis — not a magic number.

  • Reads the current setup and checks which settings are actually adjustable
  • Uses compatible telemetry, driver feedback, personal experiment history and reviewed setup knowledge when available
  • Answers the parameter you asked about first, with at most one primary alternative and one or two settings per test
  • Uses physical click directions and confidence labels, and changes nothing until you explicitly ask it to create the next version

One Vault, Every Version

Your setups live in a private, versioned vault — organized by sim, car, track, intended session and your personal vocabulary, with the full history of how each one evolved.

  • Upload iRacing garage exports (.htm) or Le Mans Ultimate files (.svm) — the sim is detected automatically
  • Every version shows exactly what changed against its parent, parameter by parameter
  • Status is derived from evidence: draft with neither readable values nor a confirmed session, ready with readable values and no confirmed session, tested with a confirmed session
  • Give the whole setup one optional type and up to eight personal tags — user-declared labels for finding it, never evidence about how the car behaves

Le Mans Ultimate: Full Round Trip

LMU setups are fully round-trippable — what you download is a valid setup file the game loads directly.

  • Export your setup from the LMU garage and drop the .svm into your vault
  • Ask your Race Engineer for changes — it edits only adjustable values
  • Download the new version as a ready-to-load .svm
  • Load it in the garage and drive — then iterate again after the stint

iRacing: Recipes You Apply in the Garage

iRacing setup files are encrypted by the sim, so remixes arrive as a garage recipe — the exact changes, section by section, ready to apply and save in-game.

  • Export your setup from the iRacing garage as .htm and upload it
  • Ask for changes and get a recipe: each setting with its from → to value
  • Copy the recipe, apply it in the garage, and Save As — the sim writes the setup file
  • Values keep the units of your uploaded export, metric or imperial — never converted

Frequently Asked Questions

Which sims are supported?

iRacing and Le Mans Ultimate. LMU setups (.svm) are fully round-trippable — upload, remix, download, load. iRacing setups are uploaded as garage exports (.htm) and remixed as garage recipes you apply in-sim.

Why does iRacing give me a recipe instead of a file?

iRacing's native setup format (.sto) is encrypted by the sim, so no external tool can write it. Instead of pretending otherwise, your engineer gives you the exact changes to apply in the garage — you hit Save As and the sim writes the file itself.

Which plan do I need?

Setups Public Beta requires a personal Plus or Ultra plan. A Basic account, or a Team seat on its own, does not give access.

Are my setups private?

Your vault is private: no other Braking Lab user can see your setups. Your Race Engineer is your own AI client, such as Claude or ChatGPT, connected through MCP, so the setup values and notes it reads pass through that client's provider. Braking Lab does not store the conversation, only two milestones of each remix: your request and the engineer's rationale. It also derives privacy-protected parameter observations: exact community values appear only after at least three distinct contributors support a car parameter, and deleting a setup or account withdraws its observations.

What does the Setup Interview start from?

A Le Mans Ultimate setup you already own. It derives a child version using bounded relative movements; protected reference files and absolute values are never copied into your vault.

What happens if my paid access ends?

Your existing setups remain manageable: you can list, inspect, compare, download, organize, edit and delete them, review existing experiment history, and retire a session association. Uploads, new versions, remixes, new associations, confirmations, evaluations and shared-evidence writes stay blocked until full access returns.

Ready to test your next setup change?

Open your vault, upload a setup, and start the conversation.

Open Setups Read the docs 

Explore other features