Talking to Wisper

Wisper is the one agent you talk to in WispOS. You don’t pick a model, a project or a team before you ask: you say what you want, and she works out where it goes.

Where to talk to her

• Her page (Wisper, in the sidebar): the full conversation. Use it for real work and back-and-forth.
• The popup (⌥ Space on a Mac, Alt Space on Windows): a quick ask from any app, without opening the window. See Quick asks, the popup and your voice.
• Your phone: see Wisper on your phone.

It’s one conversation wherever you start it.

What happens when you send a message

Every message gets one of three kinds of answer, and her page shows which while she works:

1. A reflex. Plain things like “set a timer for 10 minutes” are answered at once, without waiting on the AI at all.
2. A conversation. A question, an explanation, a quick change in a file: she does it herself, in the same turn, and tells you what she did.
3. A delegation. Bigger work becomes a request in your Queue. She either does it or hands it to the team that owns that kind of work, and tells you who has it. You can keep talking to her while it runs.

A short reply, a question or a nudge on something already running doesn’t create a new request; it goes to the work it’s about.

Her replies

• Her replies come in word by word, and her portrait follows along: listening while you type, thinking while she works it out, talking as the words arrive.
• When a reply mentions a file, page or project, it’s a link: click it to open it in the drawer beside the conversation.
• She says when something isn’t built yet, and she won’t do anything that can’t be undone, like publishing or sending, without asking you first.
• When she needs to work outside your HQ folder (in a project somewhere else on your computer, say), the app asks you first: Allow once or Allow always.

When a report lands

When a team finishes, Wisper reads the report, does any small follow-up herself, and then tells you what happened. If you’re in another app, her popup slides in with a chime. Press Esc to put her away; it waits on her page.

Getting good results

• Say the outcome, not the steps. “The checkout page should remember the last card used” beats a list of edits.
• Name the project if you have several that could fit: “in the cookbook, …”.
• One request per message for real work. Each becomes its own row in the Queue and is tracked on its own.
• Your request is the go-ahead. She doesn’t come back with a plan for you to approve; she does it and reports. If she truly can’t decide something, it comes back to you as a Decision.
• Follow up in plain words. “Make it blue instead” refines the request it’s about rather than starting a new one.