Devices

A device is a computer of yours that an agent can reach. Pairing one is what lets an agent work with files and tools that exist on your machine rather than in a service you connected.

Device versus workspace

Both give an agent somewhere to do work, and they are not interchangeable:

	Workspace	Device
Where it runs	Endue’s infrastructure	Your own machine
Who sets it up	Prepared automatically when work needs it	You pair it
Good for	Anything self-contained — checking out code, building a report	Files, tools, and networks only your machine can reach

Pairing

The Devices section in Agent Builder lists the machines paired to this agent and their state: available, pairing requested, paired, or inactive. Pairing is initiated from the machine — the agent side is the list you see here, and revoking a pairing here cuts the agent off immediately.

Setup docs in progress

Pairing a device needs the desktop app or the CLI, and neither is generally available yet. Install and pairing instructions ship with them — see Surfaces for what each one does today.

Limits

• A paired device is a door into your machine. Pair only machines you control, and revoke pairings you no longer use.
• Work on a device happens where the device is. If it is asleep or offline, the agent cannot reach it.
• Actions that write or execute are subject to the same approval gate as everywhere else.
• Devices are paired per agent, not per account.

Related

SurfacesThe desktop app and CLI that make a machine pairable.

WorkspaceThe cloud machine an agent gets without pairing anything.

Security and permissionsWhat an agent can and cannot reach.