Web Client

Chat with your agents from any browser — no app to install.

DashSquad has a web client: a page you open in your browser to chat with your agents. There’s nothing to install. It works anywhere you have a browser and an internet connection, and it uses the same remote access your phone uses to reach your HQ.

The web client is a separate address from Desktop. Desktop still runs on the machine with your agents; the web client is a page hosted elsewhere that you can open on a laptop, a shared computer, or a phone browser.

​

Before you start

The web client needs your HQ to already be set up for remote access. If you haven’t done that yet, follow Remote Access first — sign in to DashSquad from Desktop, create your HQ, and confirm it shows HQ ready at followed by your address.

​

Sign in and chat

1. Open the web client

   Go to the web client’s address (your organization gives you this link — it looks something like https://app.<your relay domain>).

2. Sign in with a passkey

   Sign in using a passkey — the fingerprint, face, or device unlock your browser already offers. There’s no password to remember.

3. Pick your HQ

   If you have more than one HQ, choose the one you want to chat through. The web client remembers your choice on this browser next time.

4. Start chatting

   Open a conversation, or start a new one, and chat with your agent the same way you would in Desktop or the phone app.

Conversations you have here are the same ones you see in Desktop and on your phone. Anything you send from the web client shows up everywhere else too.

​

Guide work while it runs

Keep typing while your agent responds. Press Send and DashSquad routes your message as a Steer or a Follow Up, labeled Auto-steered or Auto-queued. When it is not sure, or when you press Ctrl+Enter (Cmd+Enter on a Mac), choose Steer, which guides the response in progress, or Follow Up, which queues another request. Closing the choice keeps your draft and images. Edit or remove queued items before they start.

Automatic routing is a Desktop setting: see Settings → Chat in Desktop for Route automatically versus Always ask, and what happens without an OpenRouter key.

Your queue is shared with the other apps. Stop ends the current response and lets the next Follow Up run. If a response fails, the queue shows Follow Ups paused. Review what happened, then choose Resume Follow Ups. These controls need a current HQ; older HQs keep the previous single-response composer.

​

Approve this device

If your account already has an iPhone or iPad signed in to DashSquad, a new browser needs that device’s approval before it can chat — this keeps someone who only has your passkey from reaching your agents without you noticing. Instead of chatting right away, you’ll land on a screen headed Approve this device, with the message:

Waiting for approval — scan this code with the DashSquad app on your phone.

Open DashSquad on your phone, go to Settings, tap Approve a device, and scan the QR code shown here. A confirmation screen on the phone names this browser and HQ — tap Approve, and this page continues automatically within a few seconds.

Accounts with no iPhone or iPad signed in yet skip this step entirely: sign-in goes straight to your HQ list, exactly as before. The moment your first DashSquad for iOS device signs in, every new browser session after that needs approval.

If the request times out or is turned down instead, you’ll see one of:

What you see	What it means
Approval declined. You can try again from the HQ list.	Someone tapped Deny on the phone. If that wasn’t you, check who else has access before trying again.
The code expired. Try again from the HQ list.	Nobody approved it in time. Go back to the HQ list to get a fresh code.

​

Manage your devices

Open Devices in the web client to see every browser that’s signed in and connected to this HQ. Click Revoke next to any browser you no longer recognize or use — for example, a shared or public computer. Revoking your own current browser signs it out immediately and sends you back to the HQ picker.

​

Manage AI provider keys

Open the AI Providers tab to see the providers your HQ supports and the names of their keys. Click Add key and paste a key to add one. Click Replace to swap a key for a new one, or Remove to delete it. Keys are stored encrypted on your HQ and shared with Desktop. A saved key is never shown again.

To use a Claude or ChatGPT subscription instead, click Sign in with Claude or Sign in with ChatGPT and follow the steps shown. See AI Providers.

If there’s no AI Providers tab, your HQ needs an update.

​

Live browser view

When an agent with the browser tool opens a browser, a View browser button appears in the top bar. Click it to watch the agent’s browser live in a column beside the chat — or full screen, on a window 768 px wide or narrower. Between turns the view reads You have control, and you can click, type, paste, and scroll in the page yourself, for example to solve a CAPTCHA. Only one live view can be open per browser, so opening it here ends one open in Desktop. See Browser → Live view.

​

Troubleshooting

What you see	What’s happening	What to do
”Your HQ is unreachable”	The machine running your HQ is off, asleep, or not connected to the internet	Turn on or wake the machine running DashSquad and check its internet connection. The web client reconnects automatically once it’s back.
”This HQ needs to be re-enrolled from Desktop before web access works”	This HQ was set up for remote access before web support existed, so it hasn’t shared what it needs with the web client yet	Nothing to redo by hand: open Desktop on that computer once — it updates the HQ’s app access automatically when it starts. Then come back and pick the HQ again.
”Your web session for this HQ was revoked. Pair again to continue.”	This browser’s access to the HQ was revoked — either by you from the Devices screen, or by someone else with access to the HQ	You’re back at the HQ list. Pick the HQ again to reconnect. If you didn’t revoke it yourself, check the Devices screen on your other clients for anything you don’t recognize.
”No HQs linked to your account yet”	Your DashSquad account isn’t linked to any HQ	In Desktop, open Settings → Devices → Remote access and enroll this machine.

Revoking a browser’s access stops it from reaching your agents immediately — if that browser has a chat open, it disconnects there and then rather than at its next request. It does not change any other device’s access, and your conversations stay exactly where they are.