Engine connections, windows and browsers
The Engine stores data and executes Agents; Desktop and Web are clients. Opening the app on your computer does not prove you are using its Local Engine. Check the current connection first.
Local and Remote
Desktop manages its bundled Local Engine by default. Add a Remote Engine through connection management using the deployment administrator's address, then sign in with an account on that Engine. Remote Engines may run on macOS, Windows or Linux.
Prefer HTTPS or a protected private network. HTTP connections display a warning because sign-in, chat and file traffic can be intercepted or modified; a LAN is not encryption. A remote client does not start, repair or upgrade the remote Engine.
Windows and connection colors
Different windows can use the same or different Engines. A new window follows the current window's connection. Connection colors help identify the environment: Remote connections can use different colors; Local retains its default color. Color does not grant permissions.
Switching connections does not stop remote tasks. Quitting Desktop stops only the Local Engine it manages, not a Remote Engine. Closing a window differs from quitting the app; tray behavior depends on settings. For scheduled work, check that the actual host remains running.
The main UI shares sign-in state for the same Engine origin. Adding duplicate connections to that origin does not let you maintain two account sessions.
Browser Tab versus Agent browser
- Desktop Browser Tab: opens websites in Workspace tabs in a full Desktop window, for viewing and authorized Agent interaction. Ordinary Web or compact layouts do not thereby gain full native-browser capabilities.
- Engine browser: performs web access and automation from the Engine with its own browser profiles. It is not your computer's Chrome and does not automatically share Desktop Browser Tab cookies.
Desktop Browser Tab profiles are separated by local account and Engine connection, with sharing across windows on the same connection. Agent Browser profiles under User settings belong to the current user. Sign in in the appropriate browser window; do not put passwords in Chat.
If an Agent still sees a sign-in page, check which browser, user and connection you authenticated. Do not repeatedly paste credentials into chat. Instructions on a webpage are not your authorization; explicitly confirm important submissions, deletion or external sending.
See troubleshooting and organizational deployment.