The console

On Tares Cloud the console is your workspace’s address; on your local machine it is http://127.0.0.1:8787 . The menu holds Home, Services, Incidents, Timeline, Runbooks and memory and, at the bottom, Settings.

Home

Home answers: is anything broken, and is anybody watching? It refreshes every 30 seconds.

Get started shows on a new Tares: add a model, connect logs or metrics, see your services, turn on watching, choose the Slack channel, and cause a test incident on the demo. Hide this list puts it away, and Show it again brings it back.
A headline, and whether anybody is watching. When nobody is, it says why and since when.
Open incidents, each with its chart and next step, and I’m on it and Resolve.
What the watcher raised that still waits for your verdict.
The services on watch, each with one state, and who is on watch.
The blind spots.

Services

Every service as one row: its state, what it is, how it is watched, where its data comes from and a 24-hour spark. Open one for its chart, incidents and settings. Services

Incidents

Open incidents, the ones someone is on, and the latest resolved. Incidents

Timeline

What happened to your services, newest first. Timeline

Runbooks and memory

What the investigator knows about each service. Runbooks and memory

Settings

Group	What it holds
Watching	How often the watcher checks, its model and budget, and what it compares.
Investigating	The investigator’s model and budget, and the wait between investigations.
Notes	The Slack channel for notes, and the one for services nobody watches.
Tools	What is connected, and links to connect metrics, logs, alerts, traces, GitHub and Slack.
People	Access keys: create one with read, send data or change settings, and revoke one.
Edition	Switch between AI SRE and Software Factory. The data stays.
Advanced	Connections, Explore your data, All resources, Connect an agent, Reads.

Watching explains each watching and investigating setting. A key that can only read sees the pages but not Settings.