Complete Your First Task with xAgent
Basic Usage
Use this structure when you need a clear task description:
Goal:
Input materials:
Required constraints:
Output format:
Result location:
You do not need to fill every field mechanically. The more complex the task is, the more useful it is to define the material scope, constraints, and deliverable format.
Start with something small and easy to verify:
Please turn this requirement into a to-do list. Group items by Must / Should / Optional, and end with a Markdown table.
If the task uses files, upload the file first, then say which file should be processed:
Please read the meeting notes I just uploaded. Extract decisions, action items, owners, due dates, and save the result as Markdown.
After submitting the task, watch for three things:
- Whether xAgent asks for more information.
- Whether a tool call or approval request needs your confirmation.
- Whether the result is returned in the message, saved as a workspace file, or both.
If the result does not meet expectations, continue in the same page with requirements such as "keep the original wording," "add a risk column," or "save the result as CSV."
Complete Example: Organize Meeting Notes
Input
Upload a meeting record named meeting-notes.md. It contains discussion notes, decisions, owners, and timing requirements.
Task
Read meeting-notes.md and extract decisions, action items, owners, due dates, and risks.
Create a readable Markdown summary and also save the action items as CSV.
Mark unclear information as "Needs confirmation" instead of filling it in yourself.
What to Check During Execution
- xAgent reads the correct source file.
- Confirmed owners and dates remain faithful to the source.
- Missing information is labeled instead of guessed.
- Both Markdown and CSV outputs are generated.
Output
The workspace can contain:
meeting-summary.md
meeting-actions.csv
meeting-summary.md may include:
## Decisions
- Release the new version to test users first, then expand based on feedback.
## Action Items
| Action | Owner | Due date | Risk |
| --- | --- | --- | --- |
| Organize the test issue list | Alex | July 18 | Some issues do not have reproduction steps |
| Confirm the release scope | Needs confirmation | Needs confirmation | An owner must provide more information |
The acceptance criteria are clear: the correct source was used, key information is traceable, missing details were not invented, and both output files were saved.