The Console
What the engine's one built-in page shows, how to open it with an API token, how to protect it or switch it off, and what it does not do compared with the Sypnia Cloud app.
Engine This page is for whoever uses or protects a self-hosted engine. The Console exists only in the open-source engine. Sypnia Cloud has the full app instead, at app.sypnia.com, and no Console.
The Console has no data of its own. It reads through the same API as everything else, with the token you give it, so it can show exactly what that token may read and nothing more.
Open it
At the end you will have: the problems of one project on your screen.
Create a token for yourself
The Console signs in with an API token.
readshows problems, sessions and their timelines; addreplayto watch recordings.Terminal sypnia token create --project shop --name "Console, Ana" --scopes read,replay --expires 90dYou should seeA line that starts withsps_. It is shown once.
What happens to the token:
- It stays in that browser tab and is forgotten when you close it. The Console sets no cookie and keeps nothing on the server.
- It is sent only to your engine, as the
Authorizationheader of API calls. - A token belongs to one project, so the Console shows one project at a time. For another project, paste that project’s token.
- The root token is refused. It can delete projects, and it does not belong in a browser.
What it shows
Problems
The list shows the project’s problems, latest activity first: the sentence in plain words, or the technical title when the agent is off; the marks «new», «growing» and «came back»; how many people it hit; since when; and the release. You can filter by status and environment, and search the text.
Opening a problem shows:
- The analysis, when an AI provider is connected: who it hit, since when, the likely cause with its evidence, what to do, and how sure the agent is.
- The failure itself: the stack, in your own files and lines when the release has source maps; what the person did before; and the trace, as a list of steps with their times.
- The sessions it affected, each with a link to its replay.
- Copy prompt: the ready prompt for your coding agent, the same text
sypnia problem --promptprints. - Resolve and Reopen. Ignore and Analyse again appear only when the token has the
adminscope.
Alerts
Alerts that nobody has acknowledged sit in a strip above the list, newest first, each with an Acknowledge button. An alert about a problem opens that problem. Alerts about uptime, a slower page, a failing API route or usage show their title and their numbers, and that is all: the Console has no screen for those. The data is in the API.
Sessions and the replay viewer
The second tab lists recent sessions: who, when, how many pages, and whether something went wrong. You can keep only sessions with trouble or with a recording, and find one by person id or session id.
Opening a session shows its timeline, in order: pages, clicks, rage clicks, dead clicks, errors, failed requests. If the session has a recording and your token has the replay scope, the viewer plays it beside the timeline: play, pause, change speed, and jump to any event of the timeline.
- A replay is watchable once its session has been idle for 2 minutes or has ended.
- What a person typed is asterisks, and masked areas are blank. The Console cannot show what the browser never sent. See Masking.
- The viewer fetches the recording straight from your bucket, through signed links that work for 15 minutes (
SYPNIA_STORAGE_PRESIGN_TTL_SECONDS). The bucket stays private. - The Console does not load the SDK, so it never records itself.
What it does not do
The Console is one page on purpose. This is what the Sypnia Cloud app has and the Console does not:
| The Console Engine | The Sypnia Cloud app Cloud | |
|---|---|---|
| Problems with their analysis and prompt | Yes | Yes |
| Session replay | A viewer: play, pause, speed, jump to an event | The full player, with the moment it broke marked on the timeline |
| Performance: slow pages, slow and failing API calls, the element behind a vital | No. API and MCP | Screens |
| Click maps, rage and dead clicks per page | No. API | Screens |
| Traces | The trace of a problem, as a list | A waterfall for any request |
| Uptime | No. API | Screens |
| Search across everything | Text search in problems; sessions by id | One search box |
| People and accounts activity | No. API | Screens |
| The daily summary and weekly suggestions | No. GET /v1/summary and GET /v1/suggestions | In the app and by e-mail |
| Project settings, keys, tokens, alert rules, webhooks | No. The CLI and the API | Screens |
| Signing in | An API token, one project at a time | Accounts, organizations and roles |
| A link you can send to a colleague | It opens for anyone who has their own token for that project | It opens for members of the organization |
| Pull requests | No | A button on the problem |
Nothing in the left column is hidden from you: it is all in the API, the CLI and the MCP server. The Console only chooses not to draw it.
Protect it
Without a token the Console shows nothing: the page is an empty shell, and the data is behind the API. Protecting the Console is therefore mostly protecting tokens. Do these in order.
Give each person their own token
One token per person, with the fewest scopes and an end date.
replaylets its holder see what your users saw on their screens: give it only to people who should.Terminal sypnia token create --project shop --name "Console, Ana" --scopes read,replay --expires 90d sypnia token list --project shopYou should seeThe list shows who holds what, and when each token was last used. Revoke one withsypnia token revoke; it stops working within one minute.Decide who can load the page at all
The Console is at a public address by default. To close it to everyone outside your team, add a rule in the proxy in front of the engine, for the path
/consoleonly. SDKs and API clients must keep reaching/v1.With the Caddy of Deploy with Docker, make a password hash and add four lines:
Terminal docker compose exec caddy caddy hash-passwordCaddyfile {$SYPNIA_DOMAIN} { @console path /console /console/* basic_auth @console { team <the hash> } reverse_proxy sypnia:8080 }You should seeAfterdocker compose restart caddy, the browser asks for the nameteamand the password before it shows the Console, and then the Console asks for the token as before.On AWS, the address is a CloudFront distribution: attach an AWS WAF rule that allows
/console*only from your office or VPN addresses. AWS bills a WAF by the month.Or switch it off
If your team reads through a coding agent and the CLI, you may not need the page.
Terminal SYPNIA_CONSOLE_ENABLED=falseYou should seeAfter a restart,<your base URL>/consoleanswers404. The API, the MCP server and the CLI are unchanged. Links in alerts still point at the Console, and stop working.
Also set SYPNIA_API_CORS_ORIGINS only if a web app of your own must call the read API from a browser. The Console needs nothing there: it is on the engine’s own address.
When something does not show
| What you see | Why | What to do |
|---|---|---|
404 at /console | The Console is switched off, or this process runs without the api role. | SYPNIA_CONSOLE_ENABLED, and the role of sypnia serve. |
| «This token cannot sign in» | The token was revoked, expired, mistyped, or it is the root token or an ingest key. | Create an API token. |
| An empty problems list, and you expected one | The environment. A test from localhost usually lands in development. | Change the environment at the top. |
| A problem with only a technical title | No AI provider is connected, or the analysis limit of the day was reached. | Models and what is sent. |
| A session without a «Watch replay» link | It was not recorded: by default 10 % of sessions are, plus every session with an error, a rage click or a dead click. | Sessions and replay. |
| «You need the replay scope» | The token has read only. | Create a token with read,replay. |
| «Not ready yet» on a replay | The session is still going on. | Wait until it has been idle for 2 minutes. |
| «Expired» on a session or a replay | It is older than your retention. | Retention. |
| The viewer stays empty and the browser’s console shows a CORS or network error | The browser cannot read from the bucket. | Check SYPNIA_STORAGE_PUBLIC_ENDPOINT, and the bucket rule for a hosted bucket. Try without browser extensions that block requests. |
Related
- What each scope lets a token do.
- The Console is one line of it.
- The whole comparison.