Deep-Target Highlight
Deep-Target Highlight takes a deep link one step further: it opens the destination and circles the exact control you need there, with an optional title and message. It never clicks anything for you — it points, and you decide.
On this page
What it is
Deep-Target Highlight is the "navigate, then point" half of Omniscio's deep links. A plain deep link opens a destination — a settings page, a board, a note, an inbox row. A deep-target link carries one extra instruction: a data-ui-anchor name identifying one control on that destination, which the app spotlights once the view has mounted.
Two transports reach it:
POST /ui/deep-target— the CLI call an agent makes when it wants to show a person where to go. It takes a destination path, the anchor, and optional title, message, auto-dismiss and request-id fields.omniscio://<destination>?highlight=<anchor>&highlightTitle=&highlightMessage=— the same thing as a shareable link.
The feature is on by default (deepTargetHighlightEnabled) and listed in Settings → Lab so it can be switched off.
Where to find it
- On screen: a spotlight card appears over the named control when the destination finishes loading, with the title and message it was given and a close control.
- Settings → Lab → Deep-Target Highlight turns the whole surface on or off; with it off, the CLI route answers
403 forbidden. - Nothing to configure per link — a link either carries a highlight or it does not.
How it behaves
Navigate-only, by construction
The highlight attaches only to destinations the app classifies as navigate-only — open a page, switch to a board, open a note, open a setting, open an inbox row, start a tour, and their siblings. A link that would spawn a session or send a message is refused with 400 destination "<action>" is not navigate-only, so a highlight can never ride a billable action.
With ?highlight= in a URL this is enforced the same way: an unrecognised parameter is simply not attached, and a non-navigate action never gets one.
What the spotlight can do
| Field | Rule |
|---|---|
anchor |
The control's data-ui-anchor name; lowercase letters, digits, :, _ and -, 1–120 characters |
title |
Optional tooltip title, up to 80 characters |
message |
Optional tooltip body (markdown), up to 2,000 characters |
autoDismissMs |
500–60,000 ms, or null to wait for a manual dismiss |
requestId |
An optional echo id so a caller can correlate the highlight it asked for |
The anchor is interpolated into a [data-ui-anchor="<anchor>"] selector, so the character set is deliberately narrow: quotes, brackets and whitespace cannot appear, which makes selector injection impossible rather than merely unlikely.
Attribution and the navigation guard
When an agent asks for a highlight, the spotlight card can say who requested it. That name is resolved server-side from the requesting session and is not a request field, so an agent cannot claim a different identity for its nudge; a user- or script-initiated link simply has no attribution.
The request goes through the same navigation guard as any agent-initiated navigation: depending on where the person is, it navigates immediately, offers a click-to-go toast that replays the highlight verbatim, or lands as an inbox card when the person is away.
Related
Plain deep links without a spotlight are described in deep-links.md. The settings surface a highlight most often points at is documented in settings-reference.md, and the helper that reads a page for you is ask-about-this-page.md. Every other page in this library is listed in INDEX.md.
Last verified 2026-11-10