How work gets done: requests, the Queue and dispatch
What happens between asking Wisper for something and it being done: the request in your Queue, handing it to a team, the report, and how to follow it all on the Overview and Queue screens.
When you ask Wisper for real work, it doesn’t vanish into a chat. It becomes a request you can follow from start to finish.
The life of a request
- You ask. In plain words, on her page, in the popup or from your phone.
- It goes in the Queue. Wisper writes it down as one row in your Queue, in your words, stamped with when you asked. One request, one row: follow-ups refine that row rather than adding another.
- Someone takes it. Wisper does it herself, or hands it to the team that owns that kind of work. Handing it off is called dispatch; the row shows which team has it.
- It runs in the background. The Overview’s Working on card shows one row per run while it works, and says plainly where each one stands: working, stalled (alive but nothing has moved for a while, in amber), waiting its turn on a project another run is using (with its place in line), or wrapping up after its report. You can keep talking to Wisper, ask for other things, or close the window.
- A report lands. When the team is done it writes a report. Wisper reads it, does any small follow-up herself, and tells you what happened, with links to what changed.
- It’s marked done, but only once the work is finished and checked. Then it moves down the list.
If the work hits something only you can decide, it comes back as a Decision instead of a guess.
The Queue screen
The full list of everything you’ve asked for, oldest first. Each row shows where it is:
| Status | Meaning |
|---|---|
| Queued | Written down, not started yet. |
| Dispatched | Handed to a team, which is working on it. |
| Needs you | Waiting on a decision or something only you can do. |
| Done | Finished and checked. |
The Overview shows the latest rows; the Queue screen has all of them.
Keeping the computer awake
While a piece of work is running, or Wisper is waiting on your OK, WispOS keeps the computer from going to sleep on its own; the screen still dims and sleeps as usual. When nothing is in flight, it sleeps normally. Turn this off in Settings → Wisper & voice.
Tips
- Ask for outcomes. “Add a dark mode to the recipe site” is a good request. Each request should be one thing you’d recognise as done.
- Check the Queue, not the chat, to see what’s outstanding. The chat is the conversation; the Queue is the record.
- Requests are the go-ahead. You won’t be asked to approve a plan before work starts. Things that can’t be undone (publishing, sending, spending) still come back to you first.