Saved prompts
Most research asks the same few questions in the same few shapes. Save one, give it a shortcut, and it is two keystrokes away for good.
Type / at the start of an empty composer. The library opens above it; keep typing to narrow, ↑/↓ to move, Enter or Tab to insert.
What lands in the composer is text. Edit it, add the CVE id or the hostname, then send. A saved prompt is a starting point, never a macro that fires on its own.
If you meant the slash literally, press Esc. The menu closes and your slash stays where you typed it.
Deliberately, most of the time. / is an ordinary character — it starts a path, ends up in and/or, and sits inside a regex — so the menu only appears where a slash cannot plausibly be prose: at the very start of an otherwise empty composer, and only while what follows still looks like a shortcut.
Typing /etc/passwd is readable writes that sentence. It does not open a menu, and it does not swallow your words.
Settings → Saved prompts is where you add, edit and delete them. A prompt needs a title and a body; a shortcut is optional.
A shortcut is what you type after the slash — lowercase letters, numbers and dashes, so /triage-cve works and /Triage CVE does not. It is yours alone: someone else on the platform using /triage has no bearing on yours.
The menu lists your most-used prompts first, counting only prompts you actually insert — opening the menu to look does not move anything up.
A profile is a composition: which model, what thinking depth, what system prompt. Applying one changes how the next answer is produced.
A saved prompt is words you were going to type anyway. Inserting one changes nothing about the model, the depth or the instructions — which is the point. Choosing a phrasing should never quietly switch the machine answering you.