Phones & tablets

The dashboard works on phones and tablets as well as desktops, so you can check the calendar, move a post or publish one from the couch. To use it, your phone needs to reach the computer running staqly, and each new browser signs in once by scanning a QR code. No key or password to type.

On a small screen you get a bottom tab bar (Schedule, Posts, Channels, Activity and More, which opens the menu), the calendar as a list, posts as cards, and touch targets of at least 44 px.

Before you start: open the dashboard to your networkCopy Anchor Link

The phone must reach the computer running staqly over the same Wi-Fi. Usually there is nothing to set up:

• Docker publishes the dashboard on your network (-p 8080:8080). The container can't see your computer's Wi-Fi address, so the first time the dialog asks for it (for example 192.168.1.23) and remembers it in this browser.
• staqly serve answers only on the computer itself until you start it with staqly serve --expose. Then the QR code uses your computer's Wi-Fi address by itself.

To pin the address for every browser, set PUBLIC_DASHBOARD_URL (for example http://192.168.1.23:8080, or a name like http://staqly.home:8080): -e PUBLIC_DASHBOARD_URL=... on your docker run command, or PUBLIC_DASHBOARD_URL=... staqly serve --expose.

Connect your phoneCopy Anchor Link

You can also sign in a browser with a link instead of a QR code: run staqly serve connect-link (or docker exec staqly server connect-link with Docker) on the computer and open the printed link in that browser.

How sign-in links workCopy Anchor Link

• The token is in the URL fragment (/connect#<token>), so it never reaches server logs, proxies or Referer headers. It is stored hashed.
• It expires after 5 minutes and works once.
• The phone gets its own browser session (30 days). It appears under Settings → General → Devices, where you can revoke it.
• In cloud mode with accounts the phone is signed in as you, with your role in the workspace: if you are removed from it, the link (and the session it made) stops working. People can also just sign in on the phone with Google, an email code or a passkey.
• Only the dashboard can create links; API keys cannot, and the dashboard never signs in with an API key in cloud mode.

Who has to sign inCopy Anchor Link

On your computer, the first browser signs in with the access token: open the link staqly printed at start (http://localhost:8080/#token=...), or paste the token from staqly serve token (Docker: docker exec staqly server token). Phones don't need the token: a QR code from that browser signs them in.

Either way, the API stays on 127.0.0.1: agents, MCP and scripts on this computer use the access token, and nothing on the network can call the API directly.

TroubleshootingCopy Anchor Link

The browser asks for the access token: it isn't signed in yet. Paste the token (staqly serve token, Docker: docker exec staqly server token), use Connect a device in a browser that is already signed in and scan the QR code, or open a link from staqly serve connect-link / docker exec staqly server connect-link.

The phone can't open the link: check that PUBLIC_DASHBOARD_URL uses the computer's LAN IP (not localhost), that the dashboard is open to the network (--expose or Docker), that both devices are on the same network, and that no firewall blocks port 8080.

The link says it was already used or expired: each link signs in exactly one browser within 5 minutes. Create a new QR code.

Next stepsCopy Anchor Link