Skip to Content
Baseera Docs

Immersive mode

Put the assistant beside the record your users are working on. It flags what is wrong in the field, drafts fixes they approve, guards the Finish button and keeps a trail.

Chat waits for a question. Immersive mode does not. The assistant sits beside the record or form a person is working on in your app, for example an invoice, and works on it with them.

You declare the record's fields and your own checks. Baseera adds AI checks that read your knowledge. When something is wrong, the field itself gets a flag. The model can draft a fix, and the person approves it in the field. A serious problem holds the Finish button until it is fixed or overridden with a written reason.

What it looks like

A person opens invoice 1042 and the tax ID is empty.

  1. The Tax ID input gets a red ring and a badge: "The tax ID is missing."
  2. The Finish button is disabled. A line under it says "1 issue blocks Send invoice."
  3. After a short pause, a small card speaks up with Apply fix. The fix is the tax ID from the customer record.
  4. The fix appears under the input as a Baseera draft with Approve and Reject. Nothing is written yet.
  5. The person approves. The value goes into your form through your own onChange, the flag clears and Finish turns on.

Why it exists

A chat window is a second place to look. People working through forty invoices a day do not stop to ask. The problems they care about are specific to the record in front of them, and the cost of a wrong finish is paid later, by someone else.

Immersive mode moves the assistant to where the work is, makes your business rules visible on the field that breaks them, and leaves a record of what happened.

Immersive or chat

You wantUse
Answers to questions, search over documents, actions by requestChat
A person to be told when a record is wrong, before they send itImmersive mode
A hard stop on a finish, with an audit trailImmersive mode
Both a question box and record checksBoth. The agent can have both modes on.

The two share one agent, one knowledge base and one session. The model sees the record's fields and check results on every chat turn while a record is open.

The loop in five steps

Declare

Your screen calls useBaseeraImmersive with the record's fields, your checks and a finish action. See Quickstart.

Check

Your checks run in the browser, and Baseera's AI checks run on the runtime. Each result is blocking, warning or info. See Fields and checks and AI checks.

Fix

A flag shows on the field. The model, or a check's fix, drafts a value. The person approves or rejects it in the field. See Drafts and fixes.

Finish

Blocking issues hold the Finish button. The person can finish anyway with a written reason. Baseera records the finish and returns a single-use receipt. See Finish and overrides.

Verify and keep

Your server confirms the receipt with verifyFinish. Every flag, fix, approval, override and finish is kept as a per-record trail, shown in the dashboard and sent to you as a signed webhook. See Trail and webhook.

What it proves, and what it does not

Your checks run in the browser. Baseera cannot see whether they are true, and a determined user can change what the browser reports.

What Baseera does guarantee is narrower and explicit:

  • The finish was recorded by Baseera first, for this record and this agent, once, in the last 10 minutes.
  • The record says who finished, when, which blocking checks the browser said were open, and the override reason the person wrote.
  • If your server passes its own blocking check ids to verifyFinish, the override must cover those too. That part does not depend on the browser.

The trail is the browser's account of what happened. It records. It does not prove. For a hard guarantee, compute your blocking checks on your server and pass them to verifyFinish. A route that never calls verifyFinish enforces nothing.

Everything in the record's fields goes to your model provider with each turn. Do not declare fields that hold secrets.

The packages are not on npm yet. See Installation for how to add them from the Baseera workspace until the first release.

Next steps

On this page