Probes
Reusable how-to-check notes that surface at the moment a prompt asks.
What a probe is
If objectives say what to check, probes answer how. A probe is a short, reusable note attached to a component: the query to send, the UI path to follow, the thing that took you an hour to figure out the first time.
Probes live on the component, in its Probes tab:
- Open the component and switch to Probes.
- Click Add Probe.
- Fill in the title and an optional description.
They support drag-reordering, editing, and deletion — the same conventions as objectives.
Where probes surface
At the moment of need. When a proactive prompt asks you to confirm a component on an asset, the prompt carries a probe-count badge — and its context menu offers View probes, opening that component's probes as a numbered list, right there in the asset view.
If the component has no probes yet, the panel says so: "This component has no probes defined in its notespace yet."
Why probes matter
- They close the distance between noticing and checking. A checklist only accelerates you if the how is one click away.
- They capture hard-won knowledge. The bypass that worked, the header that mattered — written once, surfaced forever.
- They compound like everything else. A good probe serves every asset the component ever appears on, and every teammate who ever works it.
What's next
- Proactive Checklist — where probes surface.
- Work a Prompt — the practice of resolving prompts with evidence.