Agent Uplink

IN DEVELOPMENT

Agent Uplink

Your agents.
Your machines.
Connected.

Bring the tools and files on your computers within reach of your cloud agents. You choose what gets through.

Read the setup guide
Illustrative workspace

01 / THE CONNECTION

Keep your workflow.
Extend its reach.

Your agent can run in the cloud. Your workspace can stay on your computer. Agent Uplink is building the permissioned connection between them.

  1. 01

    Your agent

    An authorized agent or application requests a specific device and service.

  2. 02

    Agent Uplink

    The relay checks scoped grants and routes traffic to the enrolled machine.

  3. 03

    Your computer

    The local client connects outbound and exposes only configured capabilities.

No inbound desktop portMutual TLS device identityExplicit device and service grants

02 / LOCAL CAPABILITIES, REMOTE REACH

A connection to what
your agent needs.

One transport foundation, with purpose-built adapters. Capabilities are under active development, not a general-availability promise.

MCP

Tools where they live.

Connect authorized consumers to allowlisted local MCP services, with HTTP and stdio bridge work underway.

Implementation in progress
FILESYSTEM

Your files. Defined boundaries.

Scoped filesystem mounts over a shared TypeScript client, with adapters for Files SDK, Mastra, AI SDK and just-bash.

Implementation in progress
ACP

Reach your local agents.

Route agent sessions to allowlisted CLI agents supervised on your enrolled computer.

Implementation in progress
COMPUTER USE

Beyond the terminal.

Explicitly authorized computer-use adapters and synthetic fixtures. Dedicated desktop VM verification is still required.

Implementation and support limits

03 / A CLEAR BOUNDARY

A gateway.
Not another agent platform.

Keep your model, orchestration and conversation history where they belong. Agent Uplink focuses on access to local capabilities.

Deliberate accessDevice, service and operation scopes, backed by local configuration.

Honest failure semanticsTransport delivery is not proof of a completed action. Ambiguous effects are not automatically replayed.

An explicit trust modelThe relay terminates encrypted connections and is trusted with service traffic. This is not end-to-end encryption.

04 / BUILDING IN THE OPEN ABOUT OUR LIMITS

Early days.
Solid boundaries.

The authenticated transport and ordered rotation have local verification evidence. Adapter, cluster, platform and release work remain. Agent Uplink is not yet a production-ready release or a generally available hosted service.

Previously Agent Tunnel. Same project, a new name.

Explore the planned capabilities