Skip to main content

​
What it gives you

  • A faster prompt-to-result loop. No cognitive cost of guessing the right card — type and go.
  • A library that grows without cluttering the widget. New specialized scenarios (a status check, a PR fixer, a publisher, …) become reachable through the same Task input, without a new button to hunt for. The old temporary AWS Pulse card is gone for this reason — that flow is still there, just ask for it.
  • One click when Amos isn’t sure. When the routing isn’t confident enough, the top candidates appear as a button panel in the task modal, and one click picks the right flow. The panel is the same one every Amos question uses.
  • A useful answer even on a miss. If the routing can’t decide at all, the prompt falls through to a straightforward question-and-answer flow rather than failing.

​
Follow-ups are routed on their own

Every prompt is classified on its own content, not on the first prompt of the conversation. A single workflow can therefore mix kinds freely — build a project → ask a question about it → request a security review → keep coding — and a coding follow-up still targets the same repo, because the project binding survives routing. One boundary worth knowing: this routes follow-ups, not project origination. Starting a repo-backed project remains the job of the dedicated project command, which collects the structured fields (repo, branch, deploy target) that a mid-workflow prompt doesn’t. A “start coding” follow-up on a plain conversation routes to the coding flow, but without a repo attached.

​
You can say it instead of typing it

The Task input is also the voice path. Hold the orb (or Space) and speak — anything that isn’t a navigation command becomes a task and is routed exactly like typed text. When Amos needs to disambiguate, it reads the question aloud and your spoken answer snaps to the nearest offered option. See Voice Control.

​
Under the hood

How prompts are classified, how confident routing chains into the chosen scenario, and where the confidence threshold lives are described in Scenarios runtime.