Agents and devices
Remote access and devices
Agents drive the same devices through device_* tools and the agent-device command line, which T3 Code installs only after Agents can use devices is on.
T3 Code docs: devices
What it’s for
Letting an agent test mobile work while you watch; an agent-opened device floats over the chat, and in the mobile app you tap the device button above the composer.
T3 Code docs: devices
When to use it
Turn off Agents can use devices in Settings → Devices to keep agents away from simulators; your own panel is unaffected.
T3 Code docs: devices
How to use it
Let agents control devices by turning on Agents can use devices in Settings → Devices.
T3 Code docs: devices
Restart any existing agent session so it receives the device CLI environment.
T3 Code docs: devices
To watch an agent's device in the mobile app, open its thread and tap the device button above the composer.
T3 Code docs: devices
Theo’s tips
Theo lets an agent on one machine, such as his Linux box, request access to another machine in his fleet (a Mac mini or Windows PC) to test changes. He approves it from a pop-up in the app.
So, if I have a Linux machine that I'm using for a lot of work and it wants to test the changes or have another agent go run the changes out on one of my Mac minis or maybe on my Windows PC, it can request access and a little pop-up comes up in the app saying, ‘Hey, this thread on this computer wants to have access to this environment. Do you want to allow that?’
What’s changed
- Agent devices can be viewed and controlled.Added Sep 19
Related settings
Unofficial notes. Not affiliated with Theo or t3.gg.