A desktop and a travel laptop can each run Canopy locally. Link them to see work across both, send instructions to the right computer and keep supported configuration together. Each installation still has its own services and data.
Give each task one execution home
Threads and bots belong to one home computer. Other linked computers show them and route actions back to that home. Starting a Thread on your desktop from a laptop keeps the Thread, worker and project directory on the desktop.
This arrangement suits computers belonging to the same person. Pairing gives a linked computer broad access to your Canopy work. It is not a team collaboration feature with separate member roles or a read-only guest invitation. Pair computers you control.
Share configuration with a defined scope
Configuration sharing covers account settings, providers, proxies, project identities, connected accounts and the agent environment library. Instructions, skills and plugins can follow the shared setup. Credentials travel through the pinned encrypted link and are encrypted separately by each receiving gateway.
Project files, native CLI logins, workspace directories and machine-specific paths stay local. Connector access for individual workers and bots remains tied to their homes. Configuration sharing can be disabled per link; doing so keeps existing copies rather than deleting previously shared values.
Keep history readable when a computer leaves
Linked computers keep mirrored bot and Thread history for reading. When a home computer becomes unavailable, its recorded work stays visible. You can inspect what had synchronized before the connection stopped, rather than losing the entire view of a project.
Offline reading does not allow offline remote edits. Messages, approvals and settings changes that need the unavailable home cannot be sent for later delivery. Reconnect to continue. The interface resumes history synchronization when the link becomes available again.
Prepare both local desktops
Run Canopy Desktop in Local mode on each computer, configure Network access and pair them through Linked computers. The link uses pinned mutual TLS. Your network must provide a working route; an encrypted link does not remove routing or availability requirements.
Standalone server and Docker gateways do not offer desktop linking. A server can instead centralize remote workers. If replacing a computer, use explicit move actions where supported. Moving a Thread's history does not copy its native CLI session or project files.