| name | kortix-computer |
| description | How to reach a CONNECTED MACHINE (a user's laptop/desktop, or any computer paired over the Agent Computer Tunnel) from a Kortix session — read/write files, run shell commands, and drive the desktop (click/type/screenshot) on that machine. It works through the `computer` connector and the same list/discover/show/call path as every other connector, so there is no separate tunnel client and no token. Load this when the task is about acting ON a specific physical/remote computer the user has connected ("on my laptop…", "read ~/Downloads on my machine", "run this on my desktop", "click the button on my screen"), or when the user asks how the agent reaches their computer. For files INSIDE this sandbox, just use normal shell/fs — not this. |
A user can connect their own machine to Kortix over the **Agent Computer Tunnel**
(a permissioned reverse tunnel). Once connected, you reach that machine through
the **connector gateway** — it shows up as a single **`computer`** connector that fronts
**all** of the account's connected machines. You use the normal
`kortix-connectors` MCP tools (`connectors` → `discover` → `describe` → `call`);
there is **no token and no separate tunnel CLI** — the live tunnel is the
credential, resolved server-side.
The computer connector's tools relay an RPC to the machine:
- filesystem —
computer.fs.read / fs.write / fs.list / fs.stat / fs.delete
- shell —
computer.shell.exec (stdout / stderr / exitCode)
- desktop —
computer.desktop.cua.click / type_text / press_key / hotkey /
scroll / launch_app / list_apps / list_windows / get_screen_size /
, plus (a passthrough to
ANY computer-use tool by name).
**1. See which machines are connected.** Call the connector `call` tool:
The machine's owner grants access **per capability** (filesystem / shell /
desktop), scoped (allowed paths, allowed commands, allowed desktop features), in
**Customize → Computers**. The tunnel layer enforces this on every call — the
The connector gateway does not bypass it.
- **Use the `computer` connector** — never hand-roll a tunnel client
or look for a tunnel token. There isn't one in the sandbox by design.
- **Pick the machine deliberately.** When more than one is online, always pass
`computer`; a call without it errors and lists the options. Use
`list_computers` to choose.
- **Be careful with write/destructive ops.** `fs.write`, `fs.delete`,
`shell.exec`, and desktop control act on someone's real machine — confirm
intent for anything irreversible, exactly as you would locally.
- **`pending_approval` is not a failure** — it means "ask the human to grant it
in Computers", then retry. Surface the request plainly.
- This is for an **external connected machine**. For this sandbox's own files,
use normal shell/fs, not `computer.*`.
