REC FIELD NOTE → OLARES · FLEET EDITION
SATELLITE OF SLAVA+OLARES | X
CUSTOMER FIELD NOTE · LONDON · 2026 · FOR PROSUMERS, NOT ENGINEERS

Same metal.
Two jobs.
ONE SURFACE.

My Olares machines run Windows as a VM on top of Linux, and OlaresOS runs everything through a browser — management, apps, storage, even the terminal. This page is what happened when my desktop AI agents met that web surface: the barrier between Windows and Linux eroded — and with it, the barrier between chat and CLI.

51.5246°N · 0.0753°W — SHOREDITCH · Sept-Oct 2026
ONE AGENT · TWO FACES · SHORT PIPE · MANAGEMENT RIDES THE WEB · EXECUTION RUNS NATIVE · THE DOOR IS NOT THE WORKSHOP ·  ONE AGENT · TWO FACES · SHORT PIPE · MANAGEMENT RIDES THE WEB · EXECUTION RUNS NATIVE · THE DOOR IS NOT THE WORKSHOP · 
01

The stack I actually own

— hover the layers · the constraint that is the whole point
LINUX HOSTfactory floor
RTX·5090
OLARES UIweb surface
WINDOWS VMcockpit
ANY DEVICE
chrome remote
LAYER INSPECTOR
HOVER A LAYER — the orange signal rides the pipe from any device, through the cockpit and the web surface, down to the factory floor.
seamless signal flow: device → cockpit → web → host ↓
02

The lesson I almost misread

— an what it was really telling me
✕ ASKED THE BROWSER TO BE THE FACTORY

Long coding sessions through a puppeted root shell

Sit in Windows, let the desktop app drive Chrome into the Olares web terminal, type into Linux from a tab. It died cleanly — browser-control broke, Linux didn't, the agent executed nothing. A dead hand on a live machine.

✓ THE SAME DOOR, USED AS A DOOR

Management, review, light work

Watching state, installing apps, reading logs, grabbing results — the web UI is brilliant at exactly this. The door is not the workshop. But a very good door, on every machine, from anywhere, is still a feature.

My first UX-conclusion — no puppeted root shells, the terminal is a door — was true and incomplete. I had asked the browser to be the wrong room, then blamed the door.

Heavy execution runs native. Everything else already has an API— it's the whole UI.
03

The loop that actually runs

— click a step · no copy-paste, no "switch to the other tool"

From anywhere

Chrome Remote Desktop → my Windows VM. The desk follows me.

The apps hold the keys

Desktop apps have browser permissions. They open Chrome on their own.

OlaresOS is a web surface

Management + a real Linux terminal, in a browser tab.

The loop closes

Results come back into the same chat — we review them together.

STEP_01 — Chrome Remote Desktop lands me in my Windows VM. Whatever device I'm holding becomes my desk.
ONE PATTERN · FOUR BOXES — SELECT A UNIT
04

Where the boundary still sits

— flip the switch · what rides the web, what runs native
RIDES THE WEB
RUNS NATIVE
The cockpit pipe
  • Watching state across the fleet
  • Installing, configuring, checking apps
  • Light terminal commands, reading logs
  • Grabbing results back into the chat
  • All of the above, from anywhere
The factory floor
  • Long coding sessions, tests, builds
  • Codex CLI / Claude Code in tmux
  • Survives closed tabs
  • Every action leaves a diff, a log, an artifact
  • The agent sits where the code lives

Computer-use is for software that has no API. OlaresOS has one — its entire UI. So the browser agent gets the web surface; native CLI keeps the factory.

For the factory, the old rule stands. For everything else, Olares already built the API.it's the whole UI
05

What changed for me as a user

— the prosumer UX part
FEELING · 1

One agent, two faces

I no longer experience "ChatGPT-as-chat" and "ChatGPT-as-CLI" as two products. One creature, short pipe between its mouths.

FEELING · 2

The fleet shrank to one interface

Four boxes, one web face. "Check the Morefine" feels no different from "check the Olares One". My garage became a single surface.

FEELING · 3

The box taught me the boundary

I didn't arrive with this architecture. The machine pushed me into (OlaresOS = the real magic!) it — by failing politely. The best lessons are honest dead ends.

06

What I'd want Olares to productise

— the loop is real; make it first-class
P1
Productise the loop, don't fight it

A first-class path for desktop AI agents to work with an OlaresOS surface: management and review through the web UI, execution handed to CLI agents on the host — wired natively, never assembled by hand.

P2
Don't build "AI that types into our terminal"

You already built the API — it's the whole UI. The opportunity is a web surface that is legible, permissioned and agent-friendly across a whole fleet.

P3
Review artifacts that come home

Every run on the factory floor lands back in the cockpit as something readable: what changed, what passed, what failed, what needs my decision.

P4
One surface, many machines

Keep the web face identical across hardware. The day my agent manages four boxes as easily as one, "personal cloud" stops being a slogan.