Skip to Content
Baseera Docs

The dashboard page

The agent's Immersive mode page: the AI checks editor, records and timelines, server signals, the finish webhook with its deliveries, and the overview tile.

Open an agent in the dashboard and choose Immersive mode in the agent's navigation. The page has five parts, top to bottom. Everything configurable here belongs to the agent, so changes to AI checks follow the usual draft and publish flow.

A problem banner

If the latest finish webhook delivery failed, a banner at the top says Finish webhook problem and Last delivery failed, with a count such as "2 deliveries failed this week", the last reason, and a link, Open the webhook settings. It also reminds you that finishing records still works: Baseera tries each delivery twice, then shows it as failed.

AI checks

The first section is the editor for AI checks. It shows "N of 25" and a table with the columns Check, Severity and Finish.

  • Finish says Can block finish or Never blocks.
  • Add check opens New AI check: Id, Severity, Instruction and Can block finish, then Save check.
  • Each row has edit and remove actions. Editing opens Edit AI check.
  • The editor reminds you where each kind of check lives: "Checks that need your app's code stay in your app, declared with the SDK. AI checks live here, in the agent's configuration, so every change is a new version."
  • After saving: "Saved to the draft. It goes live when you publish it on Deploy."
  • At the limit: "You have reached the limit of 25 checks."
  • With no checks: "No AI checks yet. Add one to describe a rule the agent should verify."

Each field reports its own error, for example "Another check already uses this id." or "A check that can block the finish must have the blocking severity."

Records

Records lists the records people worked on in immersive mode, newest first, with the columns Record, Last event, Events and Finish.

The Finish column says Finished or Not finished, and for a finished record either "No blocking checks open" or "N blocking checks were open". Open a row to see its timeline.

The Record timeline shows everything that happened to the record in order, with who or what caused each event, and Export JSON downloads it. See Trail and webhook. With no records yet: "No records yet. They appear here once someone opens a record in immersive mode."

Server signals

Server signals lists events your backend sent with the secret key while nobody had the record open: Signal, Record, Received and Data. Values are not shown, only how many fields the signal carried. The lead explains: "The record's AI checks run again the next time it is opened."

Empty state: "No signals yet. Send one from your server with baseera.signal(entity, name, data)." See Signals.

Finish webhook

The last section sets where Baseera sends immersive.record.finished. Only owners and admins can change it, and an organization that requires two-factor needs your code entered in this session first.

Enter the Address (https). It must be public: not a private, local or internal address.

Press Save webhook. Baseera checks the address before it saves. If it cannot check right now, nothing is saved.

Copy the Signing secret. It is shown once and starts with whsec_. Press I've stored it when it is in your secret manager.

To change the address or get a new secret, press Change address or secret and save again. Saving again rotates the secret and destroys the old one. Remove webhook stops sending, and deliveries still waiting are dropped.

Recent deliveries lists each send with Status (Waiting, Delivered or Failed), Tries and When. A failed one shows a reason:

Reason shownWhat it means
Address not allowedThe address is not public https, or uses a blocked port.
Address not foundThe host name does not resolve.
Timed out after 5 secondsYour server did not answer in time.
Couldn't connectThe connection failed.
Redirected (not followed)Your address answered with a redirect. Use the final address.
Answer 500Your server answered with that status.
Gave upBoth tries failed.

The same address also receives eval.run.finished. See Webhooks for the full guide and Trail and webhook for the payload.

The overview tile

The agent's Overview has a tile, Immersive mode this week, with a link, Open immersive mode:

LineWhat it counts
Blocking issues raisedBlocking checks that fired in the last 7 days.
Fixed with a Baseera draftDrafts a person approved.
Finished anyway with a reasonRecords finished with a blocking check still open.
Average idle before a noticeNot recorded yet.
Most raised checksThe checks raised most, with their share of all checks raised.

The Overview's headline numbers include Changes approved (drafts approved in immersive mode) and Finishes blocked (records a blocking check held).

Needs attention also lists AI checks that have never run: "The AI check ... has never run". Try it on a record in immersive mode before you rely on it.

The Integrate page shows an Immersive records line, "N records started in immersive mode", or "No record has started yet." until the first one does.

Next steps

On this page