Work, rest, or watch: give every ride one job

In its third-quarter update, Tesla described the Cybercab as a mode of transport, a productivity space, and, with its entertainment options, a second living room. The same week, Austin riders found two new controls on the cabin screen: a live rearview camera view you can open mid-ride, and a quiet mode that darkens the display for riders who want to rest. That is the cabin quietly admitting what riders already know. A ride can be for work, for rest, or for simply watching the road, and the worst rides are the ones that try to be all three.

Decide before the door closes

Most wasted robotaxi time is spent deciding what to do with it. You get in, check the arrival time, open the laptop, close it, ask your agent something, glance out the window, and arrive having done nothing well. The fix is boring: pick the ride's job while you're still on the curb. Look at the estimated trip length, look at your energy, and choose one of three jobs. Then set the cabin up for that job in the first minute and leave it alone.

Job one: a work block

A work ride has a single, finishable task. Not 'catch up on email' but 'clear the six messages from this morning's meeting' or 'review the draft and leave three comments.' Twenty to forty-five minutes is enough for one of those, not two.

• In the first minute, hand your agent anything that can run without you: the summary, the follow-up drafts, the calendar hold. Then stop talking to it until arrival.
• Headphones on, even if you are not on a call. In a shared, camera-equipped cabin they are both a privacy layer and a focus signal to yourself.
• Keep the cabin screen to trip status only. A big bright display in your peripheral vision costs more focus than it gives.
• Stop with five minutes left. Use that time to write the one line that tells future-you where you left off, so the handoff to the desk is clean.

Job two: rest

Rest is a legitimate use of a ride, not a failure of productivity. If you are between two demanding meetings, the most valuable thing the next twenty minutes can do is give you back some attention. Quiet mode exists because riders asked for it, especially on late rides.

• Darken the screen, silence notifications, and tell your agent you are unavailable until arrival.
• Do not 'just check one thing.' A rest ride with a two-minute email check is a bad work ride.
• If you need something to happen while you rest, dispatch it in one sentence at the start and review the result after you arrive, not during the ride.

Job three: watch

Some rides are for being present: a new city, a first ride, a route you'll drive yourself later, or simply a day when you want to see what the car is doing. The rearview camera view fits here. It was built for peace of mind in a cabin with no rear window, and it is a reasonable thing to want. It is not a work tool. If you find yourself monitoring the car's camera feeds while also trying to write, you have picked two jobs.

Match the job to the ride

• Under 15 minutes: watch or rest. Setup cost eats any real work block.
• 15 to 30 minutes: one small, finishable work task, or a true rest.
• 30 minutes and up: one meaningful work block with a five-minute landing, or a deliberate rest if the day demands it.
• Late night: default to rest. Fatigue plus a moving screen is where bad replies and sent-too-soon messages come from.

What this means for builders

Tesla is adding rider controls one request at a time: a camera view here, a quiet screen there, Grok Bot in every cab. The missing piece is intent. A cabin that asked one question at pickup, 'work, rest, or watch?', could set the screen, the notifications, the agent's behavior, and the audio in one move, and hand the session back cleanly at drop-off. That is a small feature with a large effect, and it is exactly the kind of cabin software that makes 'productivity space' true instead of a slide.

Riding mode only. This playbook assumes an unsupervised robotaxi where you are a passenger. If you are behind a wheel, supervised or not, none of it applies.