A mission is useful when work needs attention beyond a single conversation. Give it a specific objective and a reason to return, so each run produces something you can act on.
Choose a bounded objective
Start with work you already understand: prepare a recurring briefing, check a defined set of sources, or organize incoming information. Name the sources, the expected output, and what counts as a meaningful change. Avoid an open-ended instruction that leaves success unclear.
Choose when the mission should wake
Describe the timing in your request, including the time zone if it matters. Missions can wake on a schedule or a supported event, such as mail arriving in the agent’s inbox. Match the cadence to the decisions you need to make instead of requesting constant updates.
Each Monday morning, review the sources in this project and prepare a short weekly briefing. Highlight changes since the last briefing, link the evidence, and flag decisions that need my attention.
Define the action boundaries
Separate gathering and preparing from sending or publishing. A mission can prepare a message or a deliverable for review, while consequential steps need approval. Include the intended recipients and destination when you want an action prepared.
Follow the work and adjust it
Use the visible mission state to review progress and findings. Failed steps can retry with backoff; repeated failures can pause the work for attention. Pause a mission when the objective no longer applies, and revise the instructions when its output stops being useful. Missions run through cloud chat; voice and the on-device model have narrower capabilities.
Put it to work.
Copy a request from this guide, add your details, and start a conversation with Praxa.
Open Praxa