Manage Machines
Manage remote runtimes, agents and development settings
Open Settings → Machines and select a machine. Each machine has its own development tools and configuration.
System
Check the connection, resource usage and system dependencies. Under Workspace Runtime, install, start, restart or shut down the Workspace Server. Check for updates and install a compatible update when available.
A working SSH connection doesn't always mean the runtime is ready. If projects won't open, check the runtime status and error first.
Workspaces and conversations
Use Workspaces to inspect the machine's registered working directories and Conversations to find agent sessions on that machine.
Agents, MCP and skills
- Agents: install agent CLIs and configure the agents available on this machine.
- MCP: add tool servers and sync their configuration to selected agents on this machine.
- Skills: install or create skills for the machine's supported agents.
Authenticate agents on the remote machine. For stdio MCP servers, commands and dependencies must also be available there. Paths such as ~/.codex refer to the remote user's home directory.
See Providers, MCP Servers and Skills for details. Subscription readings are available in Settings → Usage; shared accounts appear once across machines.
Machine defaults
Set the worktree root, shell setup, tmux preference and file-watcher exclusions for the host. Project settings can override applicable defaults. See Project Settings.
Automations
Remote automations are scheduled on the machine. Keep the machine and Workspace Server running, with the agent authenticated and its dependencies available. Closing the desktop doesn't shut down the remote machine.