Updates · · 7 min read

Why Your Race Engineer (Ray) Runs on the AI You Already Pay For

Capture 1.4.2 lets you talk to your telemetry. Ray runs on your own Claude Code or Codex. Here's how it works, and why I built it that way.

Update, November 17, 2026. Two things changed. Capture no longer downloads its own copy of the AI’s CLI: you install Claude Code or Codex yourself with the vendor’s official installer, and you keep it up to date. Capture checks that it’s the vendor’s signed program and recent enough for Ray. And Ray no longer works with Gemini CLI, because Google ended the personal “Login with Google” for Gemini CLI on June 18, 2026. Ray works with Claude Code or Codex. The install steps are in the Race Engineer docs. The post below is updated to match.

Ray, the Race Engineer, on the radio with a happy face: "Radio check. I'm Ray, your Race Engineer. Ask me about any lap."

You: I’m a second off my best at Silverstone. Where is it going?

Ray: Most of it is in Stowe and Copse. In Stowe you brake at the same marker as your best lap, but you come off the brake early and roll into the apex too slow. In Copse you peak at 69% from 227 km/h, so the stop is long and soft. Brake harder and shorter. Want me to overlay your best lap on your last three through Stowe?

That’s an example, but it’s the kind of answer Ray gives inside Capture now.

You finish a stint, the laps come in, and you ask your Race Engineer what happened. Ray reads your sessions, laps, setups and reports, and answers with charts drawn from your own data.

Talk to your telemetry. Improve. Repeat.

There’s one thing about Ray that surprises people: the brain behind it isn’t ours. Ray runs on the AI you already pay for: Claude Code or Codex, on your computer, with your own subscription. This post explains how that works and why I chose it.

What Ray does in Capture

Open Race Engineer in the sidebar and ask a question. A new conversation starts empty. Ray looks up your latest session, setups and reports on its own, and suggests a few questions to start with. If your latest session is still uploading, Ray tells you instead of answering from an older one.

You can also add laps and setups from your library. Add one lap, then a second one as the reference. Ray can show the braking through a zone, several laps overlaid in a corner, where you gain or lose time along the lap, and a session summary.

The full tour is in the Race Engineer docs. This post is about the part you can’t see.

Why not our own AI

The easy way to build this is to put a model behind a Braking Lab server and charge for it. I didn’t, for three reasons.

Good answers need frontier models. A cheap model can talk about trail braking. It can’t reliably read a brake trace and tell you something true about it. The models that can are expensive per call.

I would have to meter you. If Braking Lab paid for every call, every question would cost me money. So I would count your questions, cap them, or raise the price. You would think twice before asking, and a Race Engineer you hesitate to ask is not much use.

You already pay for one. Many sim racers already pay for a personal Claude or ChatGPT plan. Those plans are a flat rate. Ray uses that plan, so no Braking Lab meter runs on top of it. The usage counts against your AI plan’s limits, like any other use of that AI.

So the Braking Lab server never calls a model. It holds your data and the tools to read it. The thinking happens in the AI you chose.

Why a CLI and not an API key

There are two ways for a program like Capture to use your AI. You can paste an API key, or Capture can run the AI’s own command-line tool.

An API key bills per call again. That is the meter I wanted to avoid. And a key in a settings field is one more secret to leak.

A CLI is the official way to use your subscription from another program. Claude Code and Codex each sign you in through their own page in your browser. Capture never sees your password. I built the integration to follow the vendors’ rules for this: the official program, unmodified, signed in by you and billed to you. Braking Lab never puts its own login in front of yours, and never handles your AI credentials.

How it works

This is the part I spent the most time on. An AI agent on your computer is powerful. Ray needs almost none of that power, so Capture takes it away.

Capture runs the official CLI you installed. You install Claude Code or Codex with the vendor’s own installer, and you update it the same way. Capture finds it and checks that it’s the vendor’s signed program, at a version recent enough for Ray. It changes nothing in the program. It runs it with a private Capture profile, with its own sign-in.

That means you sign in once more, even if you already use Claude Code in a terminal. It’s on purpose. Capture never reads or changes your own CLI setup, and your MCP servers, hooks, instructions and plugins don’t leak into Ray.

Ray gets one tool. The CLI’s built-in tools are off: no files, no shell, no web. Ray has exactly one tool, which reads your Braking Lab data through our MCP server. Capture sits in the middle. It forwards each call, and before it exposes anything, it checks that the account on the other side is yours.

Writes ask you first. Ray can save setups and create exercises, and you can turn both off in Settings. A new setup version always shows a confirmation in Capture, tied to that exact setup. An exercise needs your click. Text from the model never counts as your approval.

Charts come from your laps, not from the model. When Ray shows a braking zone or a lap delta, it names the laps. Capture checks that those laps belong to your account, then measures and draws the chart itself. Ray never writes those numbers. If Ray adds a figure of its own in a summary card or a table, Capture marks it as an AI estimate.

Conversations stay on your computer. You can delete one or all of them. Your questions, and the data Ray reads to answer them, go to your AI provider through its own CLI, as with any other use of that AI.

The trade-offs

This design is not free. Here is what it costs you.

  • You need a personal AI plan. Claude Code needs a personal Claude Pro or Max plan. A Team or Enterprise plan or an API key doesn’t connect. Codex uses your ChatGPT account, but Capture refuses it if your company manages your Codex settings. Capture itself needs Plus or Ultra.
  • Your AI plan has limits. Ray stops at your plan’s usage limit and tells you so.
  • You install and update the CLI. Capture doesn’t do it for you. When your copy is missing or too old for Ray, Settings shows the vendor’s install command.
  • One more sign-in. The private profile means a second login, as described above.
  • Your provider sees the conversation. Braking Lab doesn’t run the model, so your AI provider processes your questions and the data Ray reads.

Which AI to pick

Use the one you already have. Claude Code and Codex start on the model and thinking time we recommend: Opus 5.5 for Claude Code and GPT-6-Sol for Codex, both at medium. You can change the default in Settings, or for one conversation from the composer.

I’ll keep testing Ray against real sessions on both. When a better default shows up, I’ll update the recommendation.

Try it

Capture 1.4.2 is out for Windows. Download it, install Claude Code or Codex, connect it in Settings, and ask Ray about your last session. Then tell me how it went on Discord. The good and the bad. The bad helps more.

#capture#race-engineer#ai#claude-code#codex#gemini
Updated on November 17, 2026

Related Posts

The driver you are, the one you can become. A license card beside a radar of six attributes, the strong point Control at 100 and where to improve Braking at 50, a weekly chart, and a question for Ray, your Race Engineer
Updates

Driver Profile: the driver you are, and the one you can become

Driver Profile scores six attributes of your driving from your own Capture sessions. See your strong point, where to improve, and how each score moves.

· 6 min read
Prep your race like the pros: Capture overlays for iRacing and LMU, the race preparation's practice targets, the lap replayed in a chase camera, and a brake warm-up
Updates

Race preparation, overlays and 3D replay: what's new in Braking Lab and Capture

Race preparation sets a target for every practice session, and Capture measures it as you drive. Plus overlays for iRacing and LMU, and a 3D lap replay.

· 6 min read
Paddock: Race Day, From the First Click
Updates

Paddock: Race Day, From the First Click

I rebuilt how Braking Lab looks and feels. Here's what changed, why, and what I left alone on purpose.

· 11 min read