Dashboard
A project’s dashboard is a live web app that reads the latest solution and renders it. It runs in the project’s own sandbox, so it is a real application — charts, tables, whatever the problem needs — not a static export.
| Command | Does |
|---|---|
aura dashboard |
Print the dashboard’s URL and open it in your browser |
aura dashboard --no-open |
Print the URL only |
aura dashboard --project <id> |
Do either for a project other than the selected one |
aura dashboardRun dashboard URL https://aura-api-eu.strangeworks.com/api/v1/projects/proj_01J8Z…/run/dashboard/d/eyJhbGci…/ Expires in 12hInside a chat session, /dashboard does the same thing for the project you are already talking to:
> /dashboardhttps://aura-api-eu.strangeworks.com/api/v1/projects/proj_01J8Z…/run/dashboard/d/eyJhbGci…/The URL carries its own credential
Section titled “The URL carries its own credential”The link contains a view ticket, not your API key. The ticket is read-only, reaches nothing but this
one project’s dashboard, and expires — so it is safe to paste into a browser, a chat message, or an
<iframe src>, none of which are safe places for a key.
It is a bearer credential all the same: anyone holding the link can see the dashboard until it expires.
Send another when it does — aura dashboard mints a fresh one every time.
Over SSH, and in CI
Section titled “Over SSH, and in CI”The URL is always printed. A browser is only launched when one would plausibly appear in front of you —
so on a remote box over SSH, under CI, or with output redirected, the command prints and stops rather
than opening a window on the wrong machine. --no-open forces that behaviour anywhere.
That makes it pipeable:
aura dashboard --project "$PROJECT" --no-open | grep URLWhich project
Section titled “Which project”The dashboard belongs to the selected project unless you say otherwise —
--project → AURA_PROJECT → the config file, like every other command.
The project has to be in run mode
Section titled “The project has to be in run mode”A dashboard exists once a project has been modeled and its run workspace set up. Before that the command
fails with 409 — check MODE in aura project list.
From the SDKs
Section titled “From the SDKs”Both SDKs mint the same ticket, for embedding a dashboard in your own product:
const url = await aura.dashboardUrl(projectId);url = await aura.dashboard_url(project_id)Use createDashboardTicket / create_dashboard_ticket instead when you need the expiry — to refresh a
long-lived embed before the ticket runs out.