Skip to main content
A Host is the Traycer process that connects Desktop to workspace folders, files, terminals, git state, and coding agents. A Host can run on the same machine as Desktop or on another reachable machine. Most of the time, you do not manage Hosts directly. You notice them when Traycer is starting, offline, updating, or when a tab is tied to a different machine.

​
What The Host Owns

The Host owns live work that depends on where it is running:
  • workspace-folder access
  • file previews
  • git diffs
  • terminal sessions
  • agents on the Terminal interface
  • provider and coding-agent setup that depends on tools available to that Host
Cloud sync can move durable Task data across machines, but live surfaces still depend on the Host that opened them.

​
Multiple Hosts

A user can have more than one Host. For example, your laptop and a workstation can each run a Host, and each Host owns the work it can reach on that machine. Cross-device Hosts are coming soon. The model is:
  • each device can run its own Host
  • Desktop can connect to a Host when that Host is reachable
  • live surfaces still depend on the Host that started them
  • cloud sync carries durable Task data across devices

​
Current Host And Tab Host

Traycer can use a Host in two ways: Some tabs keep using their original Host: If a Host becomes unavailable, affected tabs show an unavailable state. Terminal sessions cannot move to another Host; start a new session on the Current Host when needed.

​
Hosts And Agent-To-Agent Work

The Host boundary also gates what one agent can do to another. Referencing is unaffected — every agent in the Task can be referenced regardless of Host. The other two capabilities are not: A message to an agent on another Host is rejected rather than queued. The full matrix, including the runtime requirements that apply on top of these, is in Agent-to-Agent.

​
Where To Manage Hosts

Use Settings > Host to check Host status, install or update the Host, restart it, and run Doctor diagnostics. Use Troubleshooting for unavailable states, logs, and issue-reporting steps.