Main job
Direct attentionMission Orb is the fastest way to know what matters now.
Guidance
Mission Orb
Mission Orb is the persistent action layer across authenticated product screens. It is designed to reduce navigation overhead and keep the next important move visible.
Guide summary
Use this page to understand the surface before you act inside it.
Use the persistent action layer for next-best actions, approvals, warnings, quick actions, and contextual help.
Guide type
GuidanceThis guide reflects the current product workflow and surface ownership.
Sections
8Summary first, then steps, mistakes, and recovery notes.
Related guides
4Written against the current product structure and core execution workflow.
States
Idle / Recommended / Attention / Approval Required / Warning / ProcessingThose states change the recommended action path.
Related action
Use Orb before browsing manuallyIf Orb already knows the blocker, follow it first.
Guide section
What it is
Mission Orb is the always-available mission-control action layer.
When to use it
Use it whenever it carries attention, warning, or approval states, or when you need a shortcut into help or Copilot.
Where to find it
Find it on authenticated product screens.
What happens next
You use this surface as part of the broader mission -> task -> run -> artifact workflow.
Common mistake
Ignoring warnings
Related action
Use the Help Center or Contact Support action inside Orb when you are blocked in context.
Guide section
Why it matters
It surfaces the next-best action, warnings, approvals, support, and quick actions without making you hunt through multiple screens.
Guide section
How it fits into the workflow
Orb overlays the workflow rather than replacing it. It helps you move through the system faster.
Guide section
Step-by-step usage
- Open Mission Orb.
- Check whether the current state is recommended, attention, approval required, warning, or processing.
- Review the suggested action or active warning.
- Use quick actions or command actions if they match the current need.
- Return to the core surface once the blocker is addressed.
Guide section
Inputs and outputs
Inputs needed
Current product context
Active run or account posture
Approval or warning state
Outputs produced
Next best action
Warnings
Quick actions
Support and Help shortcuts
Guide section
Common mistakes
- Ignoring warnings
- Using navigation when Orb is already offering the direct path
- Treating Orb as cosmetic chrome instead of an action layer
Guide section
Troubleshooting
If Orb seems generic, check whether the current screen exposes a contextual object like a run, mission, task, or artifact.
Guide section
State guide
Idle
Nothing urgent is currently asking for intervention.
Recommended
A useful next move is available and should save time.
Attention
Something needs review or action soon.
Approval required
A human decision is needed before execution should continue.
Warning
A risk, failure, or blocking posture needs intervention.
Processing
The system is actively moving work and the best action may be to monitor rather than interrupt.