01Bring your computers into one workspace#
Connect a laptop, desktop or other host to Halofy, then open its projects and sessions from your current client. You can send messages, follow progress and respond to agent requests on the computer that owns the session.
A session running on your desktop can keep working while you manage it from your laptop. You do not need to move the project or restart the conversation to continue directing that work.
02Connect a host, then open its sessions#
Use Settings → Linked devices to connect your computers. Halofy account connections discover your signed-in computers; a pairing link connects a specific environment. Keep Halofy running and the host awake.
Choose the device and project from the sidebar to open its sessions. In web and desktop, sessions from different connected hosts can sit in the same split-view workspace.
03Keep work moving across machines#
Use each host’s local files, tools and provider accounts while managing the sessions together. A long-running task can stay on one computer while another handles a separate project.
Commands and files remain on the host that runs the session; connected access does not copy the filesystem. For cross-device session context, keep one web or desktop client connected to both computers. The sessions do not need open panes or a split-view group. See session context without open panes.
Work on an authorized teammate’s device#
- Keep Halofy running on the host computer and sign in to the correct team workspace.
- Have a manager choose the team’s Collaboration mode.
- On web or desktop, look for an authorized teammate’s computer in the sidebar, labelled Name · Device. Open a session to read it or use the controls your access permits.
- Use the composer’s Run on menu to choose an available computer for a new session.
A device with control access can expose files and projects beyond the team’s project folders. Personal chat contents remain hidden, but this is not a limit on which host files a teammate can reach. Your Halofy account connection, other device connections and plugin-share management are not shared by the team grant.
Membership and mode changes are rechecked. Losing access ends the team pairing; it does not undo actions the host already accepted. The host must stay online, and both sides need compatible Halofy versions.
Distinguish live access from a recorded chat#
Chats in the Console at app.halofy.ai are captured records and remain read-only. Live messaging, approvals and turn controls belong to the Workstation connection.
Offline means the host has no active connection. Keep it awake with Halofy running. Loading chat history means the connection is open but its chats are still loading; use Retry history if offered. A failed connection to one computer does not prevent the others from connecting.
