Connect to Your Daemon

The first time you open Snippbot Desktop, setup walks you through four steps: Choose daemon → Sign in → This computer → Done. You can step back at any point before you finish, and re-run setup later from Settings → This desktop app → Run setup again.

Step 1: Choose daemon

1. Pick where your daemon runs:

   • This computer — the app probes http://127.0.0.1:18781 on its own and shows “Found” if something’s listening there.
   • On my network — click Search to look for a daemon advertised on your LAN (this is a separate, on-demand scan, not automatic, because it can trigger a firewall prompt on Windows).
   • Remote server — type an address, e.g. https://bot.example.com.

2. For a remote server, click Try connection. The app checks, in order: whether the address is reachable, whether Cloudflare Access is in front of it, whether a Snippbot daemon answers (and its version), and whether that daemon accepts the desktop app’s CORS origin.

   Expand

   Choosing a remote daemon and running Try connection.

3. If the daemon sits behind Cloudflare Access, the check reports “service token needed” (or “refused”). Enter the Client ID and Client Secret of a Cloudflare Access service token from the daemon’s owner, then click Save token and try again. The token is saved to this computer’s credential store and sent only to that daemon — it’s a service token, not your personal Cloudflare login.

Plain http:// only works for this computer and your local network; a public or remote address must use https://. See Troubleshooting if the app refuses an address you expect to work.

Step 2: Sign in

Pick one of three ways to sign in:

1. Username & password — the same account as the Snippbot web UI login. Check Keep me signed in on this computer for and choose a duration: 1, 7, 30, or 90 days (90 is the default). Unchecked, the sign-in lasts only for this launch of the app. A kept sign-in is stored as a device token in your OS credential store (Keychain on macOS, Credential Manager on Windows) and can be ended any time from Settings → This desktop app.

   Expand

   Signing in with a username and password.

2. Pairing link — open the Snippbot web UI, go to Devices → Pair Desktop App, and click Open in Snippbot Desktop. The app catches that link and asks you to confirm the daemon address before pairing — it never pairs from a link without that confirmation, since any web page could otherwise fire one.

3. 6-digit code — the same Devices → Pair Desktop App screen shows a 6-digit code as a fallback if the deep link doesn’t work. Type it in and click Verify code.

   Expand

   Pairing with the 6-digit code from the web UI.

Once you’re connected, a small card confirms the sign-in kind (paired device, kept on this computer, or this-launch-only) and, if it has one, the date it expires.

Step 3: This computer

This step is optional — chat, agents and jobs all work without it. It’s only for letting agents on the daemon read, write, or run commands on this computer (not the daemon’s own server). If you want that, follow the on-screen steps to set it up in the web UI; see Tools on This Computer for the full flow. Otherwise click Skip: chat only.

Step 4: Done

A summary confirms you’re connected, and that the daemon keeps running agents, routing, memory and jobs even when this app is closed. From here you can click Open Snippbot to go to the Full workspace, or Open Quick Chat to go straight to the Quick Chat popover.

Returning later: “Welcome back”

If your sign-in expired or you signed out, relaunching the app shows a “Welcome back. Sign in to continue.” screen instead of the full setup flow — it already knows which daemon you were using and just asks you to sign in again (password, or pair with a code). Click Change next to the server address if you need to switch daemons.

Signing out

Sign out of this computer from either:

• Settings → This desktop app → Sign out of this computer, or
• The account menu in the Full workspace’s left rail → Sign out of this computer.

Signing out revokes this computer’s device token on the daemon (not just locally) and returns you to the sign-in screen.