slew docs/reference/console
Web console
https://app.slew.cloud is the slew dashboard: your projects, their deployments with one-click rollback, traffic and audience analytics, and your AI usage — in the browser instead of the terminal.
Signing in
The console authenticates with a CLI token (an AI key won't work). Two ways in:
- The easy way: run
slew dashboard. The CLI validates your stored token and opens the console already signed in. The token is handed over in the URL fragment (#token=…), which browsers never send to any server, and it's stripped from the address bar immediately. - Paste a token: create one with
slew token cli "browser"and paste it into the login form. It's validated against the API before being stored.
Your session persists in the browser's local storage. If the token is later revoked, the console logs you out automatically on the next load.
What's there
| Page | Shows |
|---|---|
| Projects | Every project: name, live URL, active deployment, created date — plus your live Temporary shares, each with a "Delete" button to stop serving it before its TTL. The workspace switcher in the header flips between your personal projects and each organization's |
| Organization settings | Members and their roles, pending invites (send, revoke, copy the accept link), org-owned tokens (CI deploy tokens and AI keys that survive membership changes), GitHub installations shared with the org, the org's AI usage, display name, and leave/delete. Invite links accepted at /invites/<token> after GitHub sign-in |
| Project detail | The deployment history — id, status, file count, size, timestamp — with a "Roll back to this" button on any deployment that can go live again and a "Delete" button on inactive ones (confirmed before it runs; the live deployment can't be deleted) |
| Project traffic | The Traffic tab: cookieless analytics per project. Requests, bandwidth, and cache-hit charts over 6 h–72 h live windows or 30/90-day history, plus the audience view — pageviews, visitors per day, top pages, referrers, and countries over 7/30/90 days |
| AI usage | Requests, prompt tokens, and completion tokens per model, with totals |
Creating projects, deploying, and minting tokens stay in the CLI and the HTTP API.