Fleet

An Eidos AGI product

The Universal
Remote for AI

Your AI. Your tools. Your call.

Choose where your AI runs. Reach the browser and tools you want it to use. Keep the route, permissions and results in view.

Open Fleet Explore the grid

Sign in with Eidos SSO. Connect the tools you choose.

AI × machineVISION / DEMO

Your AI, wherever
you want it to run.

Pick an AI × machine. The browser tab can stay right here.

Example combinations — not a live inventory
RUN ON ↓
AI →		CodexClaudeGrok
This MacLocal runtimeExampleExampleExample
DesktopAnother machineExampleExampleExample
RemoteRemote workspaceSelected exampleExampleNeeds qualification

Codex runs in the example remote workspace. Your browser stays on This Mac.

AI RUNTIMECodex

Remote workspace

AUTHORITYFleet

Selected route

BROWSER HANDSThis Mac

One permitted tab

Interactive vision, not a live connection. Provider support and remote-to-tab pairing require qualification.

Trace the browser request
Choose the client.Connect your tools.Keep the controls.FLEET BY EIDOS AGI

01 / The reach

Different surfaces.
One place to reach them.

AI doesn’t live
in one window.

Some work happens in a browser. Some runs in a terminal. Some needs the machine on your desk.

Fleet brings those connections into one place, so your AI can work with the tools you already use.

01

The web, within reach.

Read pages and interact with websites through a connected browser. Your selected profile and permissions define the reach.

02

The terminal, on your machine.

Reach CLI tools through Fleet Executor. Run a bounded command in the right machine and account context, then inspect the result.

03

Know which machine is doing the work.

See your connected machines, browser connections and work context. Know where the next action belongs before sending it.

02 / The connection

A clear route from
intention to evidence.

Follow the route.
Inspect the result.

An AI can run on one machine and reach a browser on another. Fleet checks the selected route. The browser adapter does the interaction.

Follow a requestILLUSTRATIVE · NO LIVE CONNECTION
  1. 01

    Request

    The selected AI sends its intent.

  2. 02

    Access

    Check the scope and exact target.

  3. 03

    Execution

    The permitted tool acts.

  4. 04

    Receipt

    Inspect the recorded result.

Choose a capability and example target. Play the flow, or step through it yourself.

Motion starts only when you play. Pause or replay at any point.

Illustrative request

“Read this page
in my browser.”

Explore the route. This preview does not connect to a real AI, account or machine.

OPERATION RECEIPTEXAMPLE
Target
Example browser · Example Mac
Access
Browser read
Request
demo-browser-read
Outcome
Page text returned

The receipt describes a browser operation. It does not prove that an AI completed a task.

Read the evidence

How far did
the request get?

Choose an outcome. Watch where the evidence ends, and what the next move should be.

Illustrative evidence checkpoints for three request outcomesA returned result reaches all four checkpoints. Access denied stops before dispatch. An uncertain outcome has dispatch evidence but no confirmed result. This chart shows logical stages, not elapsed time or performance.
Example paths · evidence checkpoints, not timing or performance. No real requests or machine status.

A result is evidence of this operation.

Returned page text confirms the browser read. It does not establish that an AI completed a broader task.

INSPECT THE RESULT

03 / The pieces, together

A tool can act.
A message can ask.

One Fleet.
Different jobs.

Reach tools through Fleet. Send intent through Fleet Post. Let an interactive adapter do the work at the receiver.

EXISTING CAPABILITY · CONNECTIONS REQUIRED

An AI client asks Fleet to use a connected browser or machine. Permissions stay attached to the route.

  1. INPUTYour AI client
  2. AUTHORITYFleet
  3. INTERACTIONBrowser or executor
  4. DESTINATIONYour permitted tool
  5. FOLLOW-UPInspect the receipt

Fleet routes work; the connected adapter operates the tool. A command result is evidence of that command.

Fleet core

The route and the authority.

Connect clients, browsers and machines. Choose access to the exact resources, then inspect the operation's receipt.

Fleet Post In development

Messaging, with a memory.

The design owns messaging intent, one durable outbox and reconciliation evidence. It can notify an interactive adapter to work at a receiver. Fleet Post does not drive that receiver's UI.

Fleetkick Separate browser component

AI beside the page.

A Chrome side panel for local AI sessions and page interaction. Its Fleet/Helios integration connects a browser profile through explicit site and client grants. Browser and extension must remain running; the sidebar can close.

Different evidence. Different claims.

  1. 01Message delivered

    The intended receiver accepted the message.

  2. 02Response complete

    The receiver finished its response.

  3. 03Effect verified

    The intended change was independently observed.

One does not prove the next. Transport acceptance or exit 0 alone does not prove message delivery.

Ideas being explored

A bigger reach.
The same clear boundaries.

MacBook first. Mini as a qualified secondary.Proposal

Explore a browser-control bridge with MacBook as primary and Mac mini as secondary. A secondary needs its own verified browser, profile and receiver account. Switch only before dispatch; an uncertain action stays with its original request and route for reconciliation.

An AI elsewhere. Your browser right here.Exploration

Choose an AI provider and runtime machine at their grid intersection, then connect that chat to this browser tab through a qualified adapter. A Paseo session is one route under exploration. Runtime location, browser profile and permission are separate choices; pairing and provider acceptance still need verification.

Personal and company work, deliberately bounded.Design direction

Reach remote tools while keeping the selected account, workspace and authority attached to each operation. Company routing remains a separate track; personal browser or message access must not silently cross into it.

04 / Your call

Universal reach.
Deliberate control.

You choose what connects, who can use it, and where actions can run. Fleet keeps that context attached to the work.

I

Access is a choice.

Connecting a client does not grant every action. Permissions stay tied to the selected resources.

II

The target matters.

A machine, account and browser profile are part of the route, not interchangeable destinations.

III

Evidence stays visible.

Queued is not complete. Uncertain outcomes need inspection before another action.

Put your intent in motion

Bring your AI.
Choose its reach.

Open Fleet, connect a supported AI client through MCP, and choose the browsers and machines it can reach.

Open Fleet
Read the connection guide