DEVELOPMENT DOCUMENTATION / OVERVIEW
Local capabilities. Explicit access.
Agent Uplink connects authorized cloud applications to services on enrolled computers. The computer opens outbound connections; it does not need an inbound public port.
Choose your capability
| Capability | Purpose | Current boundary |
|---|---|---|
| MCP | Call local tools through Model Context Protocol. | HTTP and stdio export bridges exist; compatibility is profile-specific. |
| ACP | Interact with a fixed local CLI agent through Agent Client Protocol. | HTTP/SSE bridge with local interoperability evidence; acceptance work remains. |
| Computer use | Expose explicitly allowed screen and input operations. | Adapter and synthetic fixtures exist; real desktop verification is outstanding. |
| Filesystems | Access confined mounts through a shared TypeScript client. | 9P-over-WebSocket client and four SDK adapters; not universal SDK or platform certification. |
Start with the transport
Build the Rust binaries, validate configuration, provision device identity and consumer authorization, then run a controlled echo connection before enabling service exports. Follow Setup for the prerequisites and commands.
What Agent Uplink is not
It is not a model runtime, conversation store, agent scheduler, generic shell endpoint or unrestricted TCP proxy. Your application retains its orchestration and your computer retains local service policy.
Reading support claims
Implemented means code exists. Locally verified means the named scope has repository evidence. Neither means every operating system, backend, failure mode or production deployment is certified. The support matrix records the limits.
Source & review
Reviewed against eb2422008a3a on 2026-09-22. Based on README.md, docs/architecture.md, docs/tasks.md. Historical test evidence is not a new test run.