Notices and focus
How Baseera speaks up when a person pauses, how Later and Got it behave, how it moves them to a field, and what is not available yet.
Immersive mode speaks up without being asked, but only when it will not get in the way. This page describes exactly what is implemented today.
The proactive notice
When the person stops typing, BaseeraSurface opens a small card at the bottom of the screen for the most important open issue. It shows the check's message, its actions and a Later button.
<BaseeraSurface locale="en" idleMs={1500} proactive />Prop
Type
The rules:
- Only blocking and warning issues open a notice. Info never does.
- It picks the top issue: blocking first, then warnings. Your own checks come before AI checks of the same level.
- One card at a time. Typing again closes it.
- A card that went away because the person started typing again has had its turn. It does not return at every pause.
- Later snoozes that issue for this record. It still counts in the launcher badge and stays in the review panel. It only stops opening a notice.
- After Later or Got it, the next notice waits until the person does something and pauses again.
- Snoozes reset when a different record opens.
The card's primary action is Apply fix when the check has a field fix, and Ask Baseera otherwise. See Drafts and fixes.
Notices are client-side. They come from the check results your screen already has. They need no model call and cost nothing.
The Overview tile "Average idle before a notice" says "Not recorded yet." The idle time is not measured on the server today.
The model raising a check
The protocol reserves an event, immersive.notice with { checkId }, for the model to raise a check with the person on its own, for example when they have gone idle.
Not available yet. The runtime does not emit immersive.notice today. The card above is the only proactive behavior. The event type exists in the SDK's types so your code will not break when it ships.
Focus: moving the person to a field
The model can point at a field with the ui.focusField tool. The SDK provides it while a record is open and at least one field is on screen.
What it does:
- Scrolls the field to the middle of the screen. It is smooth, and instant under
prefers-reduced-motion. - Moves keyboard focus into the field.
- Highlights it for 2 seconds.
If the field is not on screen, for example it is in a collapsed section you did not bind, the tool returns an error "That field isn't on the screen" and the model can say so. It is a read tool: it runs at once and needs no approval.
The review panel uses the same mechanism. A check that names a field gets a Show button that focuses it.
To make a field reachable, wrap its input in BaseeraField and keep it mounted while the record is open. See Drafts and fixes.
In your own UI
useBaseeraImmersiveState() gives you boundFields (the names on screen) and focused (the field Baseera just pointed at, with a timestamp). The headless useBaseeraField returns focused and focusControl for the same purpose. Wrap parts of your UI that are not the input in data-baseera-ui so focus skips them.
Flags on the field
While a check that lists a field in fields is open, the field gets a ring in the severity color and a badge with the message. The worst severity wins when several checks name the same field. The badge is part of the input's aria-describedby.
Next steps
Drafts and fixes
How a value gets into a field: a fix on a check, applyCheckFix, the model's ui.prefillDraft tool, the draft shown in the field, approval and rejection.
Finish and overrides
When the Finish button is enabled, the single-use finish receipt, what verifyFinish proves and does not prove, and finishing anyway with a written reason.