xAgent Tasks: Goals, Materials, and Acceptance Criteria
Who This Is For
This page is for ordinary users who want xAgent to complete work more reliably.
What It Is
A task is a piece of work you want xAgent to complete. It can be one simple request or a complex job that needs files, Tools, confirmation, and multiple rounds of communication.
You do not need to learn models, Tools, or internal concepts before using xAgent. Clearly state what to do, where the materials are, and what the result should look like.
When to Use It
Submit a task whenever you want xAgent to complete something with a clear outcome, for example:
- Read and summarize a file.
- Organize meeting notes.
- Generate a report, table, or checklist.
- Check materials for problems.
- Draft a reply based on an external message.
- Run a recurring piece of work on a schedule.
Check Before Submitting
Confirm these four things before you submit:
| Check | Meaning |
|---|---|
| Goal | What you expect xAgent to deliver at the end |
| Materials | Whether files, links, background, and data have been provided |
| Scope | What should and should not be processed |
| Result | Whether to reply directly, save a file, produce a table, or generate a report |
When a task involves sending, deleting, or accessing an external system, add: “Ask me for confirmation first. Do not execute it directly.”
Basic Format
Use this structure:
Based on [materials], complete [goal].
Requirements:
1. The processing scope is [scope].
2. The output format is [format].
3. Ask me for confirmation before sending, deleting, or calling an external system.
Example:
Please read the customer interview records I just uploaded and organize the main problems and opportunities customers mentioned.
Requirements:
1. Output a table with “problem / evidence / impact / suggested action”.
2. Keep key evidence from the original text.
3. Save the final result as a Markdown file.
Common Task Templates
Organize Meeting Notes
Please read the meeting notes I uploaded. Organize conclusions, action items, owners, due dates, and risks in a Markdown table.
Analyze a Spreadsheet
Please analyze sales.csv in the workspace. Find the 10 metrics that changed the most this week, explain possible causes, and generate a short report.
Draft a Reply
Please draft a reply based on the latest customer message. Show me a draft first and do not send it directly.
Generate a Report
Please create an HTML report from the materials I uploaded, including a summary, key findings, evidence, and recommended next steps.
Plan Before Execution
Please list the processing plan first, including which materials you need to read and what outputs you will generate. Wait for my confirmation before continuing.
Reading Task Progress
After submitting a task, focus on these states:
| What the page shows | Meaning | What to do |
|---|---|---|
| Direct reply | A result or staged result is ready | Check whether it meets the requirement |
| Request for more information | The goal or material is unclear | Add details in the same session |
| Tool call | xAgent is reading, generating, querying, or sending | Wait for completion or confirm when prompted |
| Waiting for approval | An action is risky and needs human confirmation | Check the impact before deciding |
| Execution failed | A step did not complete | Adjust the task based on the error message |
Do not submit the exact same task repeatedly. Add instructions in the original session instead, so xAgent does not generate duplicate results.
Accept the Result
When the result is ready, check:
- Whether the original goal was completed.
- Whether the specified materials were used.
- Whether scope constraints were followed.
- Whether the requested format was produced.
- Whether the result was saved to the workspace.
- Whether there are external actions that still need confirmation.
- Whether evidence, sources, or key fields are missing.
When the result is not satisfactory, give a concrete revision request. For example: “add an evidence column,” “remove speculative content,” “sort by priority,” or “save it as CSV.”
Do Not Treat an Execution Receipt as Acceptance
| Information | What it establishes | What it does not establish on its own |
|---|---|---|
| Session created or message submitted | The entry point accepted creation or delivery work | Child completion or a returned result |
| Successful Tool call | That operation completed as reported by the Tool | Every stage and external effect meets the goal |
| Work record or plan state | Saved progress and task organization | Verified evidence or a correct final file |
| Remote terminal task state | The state reported by the remote service | Local processing or acceptance of the business outcome |
For complex tasks, specify where the result is, what supports it, and what remains unfinished. For example:
List completed and unfinished parts, and provide the final file and key evidence.
If work was delegated to another Session or a remote Agent, distinguish receiving a reply from validating its artifacts. Do not treat successful submission as task completion.
Current main also supports Session work records and scheduled business-run state. They record different progress or lifecycle facts and are not interchangeable. Continue in the original task Session, checking blockers and the original action before sending anything again.
Common Mistakes
| Wording | Problem | Better wording |
|---|---|---|
| Handle this | The goal is unclear | Summarize this document's conclusions and action items |
| See if there are problems | The acceptance criteria are unclear | Identify payment, delivery, and breach risks in this contract |
| Send it to the customer | The risky action is unclear | Draft a customer reply first and send it only after I confirm |
| Use the previous approach | A new session may lack the context | Briefly restate the rules to retain |
| Analyze everything | The scope is too broad | Analyze the most recent 30 days and output the top 10 anomalies |