Terminal & file bridge

Chat is where you steer agents, but sometimes you need to reach into the machine yourself — tail a log, edit one config line, grab a file. UFO gives you a real terminal and a real file browser, both served straight from the host into any browser or phone. Nothing gets copied to the cloud; you're reaching through to hardware you own.

Terminal, files, screen and browser all ride a direct connection to your machine, with an automatic server-proxy fallback if the direct path can't form — so it keeps working from a coffee shop or a phone on cellular.

#Web terminal

A real login shell on the host, opened right in the browser — full PATH, the same environment your agents run in. Tail logs, fix a config, restart a service. If all you have on you is a phone, that's enough to do the surgery.

Owner-gated. Remote terminal access is restricted to the machine's owner. A shell only spawns after a one-time, server-minted token, so a browser session can't open a terminal on your box on its own.

#IDE-style shell

The workspace works like a window manager, not a single locked view:

• Split panes — divide the workspace into resizable, side-by-side panes, each with its own tabbed channels and utility views.
• Tabs — keep several channels and tools open at once inside a pane.
• Floating windows — pop a utility (like the machine's file browser) out as a draggable window that remembers where you left it.

Keep a terminal open beside the channel you're working in, or float it over everything — whatever fits the task.

#File bridge

Browse the host's file system from any device and download exactly what you need. Files stay where they are until you ask — the bridge reads the real disk in place; nothing is uploaded or mirrored just because you looked at it.

It's a full browser for the real disk: navigate folders, search, create, rename, upload, and drag a file straight into chat. Common file types open in built-in viewers and editors — text and code open in a code editor; images get an AI-edit action right there.

Access is scoped to folders you share, and those folders are defended in depth: parent- directory (..) escapes are rejected, credential paths (.ssh, .aws, shell configs and the like) are denied, and symlinks are re-checked against their real target. Broad file access ships as a feature, safely.

#Clickable paths in chat

When an agent mentions a file path in chat, it renders as a clickable link with a preview — images, video and audio play inline, so you can eyeball the artifact an agent just produced without leaving the conversation. For files that live in the shared Drive instead of on a specific host, that's the place to look.

#The mental model

Three surfaces, three jobs:

Between them, the laptop can stay at home. A phone and a browser reach everything the machine can do.

#Where to go next

• Machines — pair a host and see which one you're reaching into.
• Browser & screen — drive the host's real Chrome and desktop, too.
• Privacy & data — exactly what stays on your machine and what travels.