A task assigns a clear work goal to an Agent team and continuously records execution progress, collaboration, and the final result. For work that requires multiple steps, multiple collaborators, or acceptance of results, create a task and let the team organize the execution.
How tasks work and terms
After a task is created, the team enters the corresponding task room to execute it. Open the task from the task board and enter the task room to track progress, add information, view subtasks and result files, and accept the submitted results. When you create a task through conversation, the initial conversation with the Leader is used to state the requirements and confirm the creation result. Subsequent execution then moves to the task room of that task.
Select the recommended approach based on the characteristics of the work:
| Work characteristics | Recommended approach |
| Q&A and instant communication | Regular chat |
| Multiple steps, multiple collaborators, or acceptance of results is required | Create a task and let the team organize the execution. Track the work through the task board and accept the deliverables through result cards |
Terms
| Concept | Description |
| Team | A collaboration unit made up of people and Agents, responsible for taking on and executing tasks |
| Leader | The Agent in a team that organizes task execution. It makes plans based on requirements, assigns work, and consolidates results. It can also complete simple tasks directly or split tasks into subtasks as needed |
| Worker | The Agent in a team that carries out specific work |
| Task | A complete piece of work organized around one goal, including the task content, executing team, state, collaboration records, and results |
| Subtask | A work unit split out during execution. Subtasks can be taken on by different Workers and have their own states and dependencies |
| Task room and task chat | A task room is the collaboration space where the team executes the current task. The task chat is the conversation area within it, used to view execution messages, add information, and discuss issues |
| Reviewer | The person or Agent responsible for accepting task results and providing revision feedback |
QuickStart
This example creates a meeting preparation task and asks the team to provide a meeting agenda and a preparation checklist.
Preparations
You can log on to AgentCore App and access the target team.
The team has a Leader configured, and the required Workers are added when collaboration is needed.
The executing Agents have the models, tools, and access permissions required to complete the task. For how to configure an Agent, see Use a managed Harness.
Acceptance requires the reviewer identity. This example uses manual creation, which by default sets the currently logged-on user as the reviewer and therefore meets the acceptance identity requirement. For the operation permissions of each identity, see Permissions.
To deliver results to a specific session, the Channel, Room, and Object identifiers are provided by an administrator. For how to configure them, see Configure a reply path.
Step 1: Create a task
Open the task board and click New Task, and then select Manual Creation. For other creation entry points, see Create a task.
Select the executing team and enter the task title and content:
Title: a short phrase, such as "Project kickoff meeting plan".
Content: includes the goal and the delivery requirements. For example, create a 60-minute project kickoff meeting plan for the product, development, and testing teams, and submit an agenda in Markdown format along with a pre-meeting preparation checklist for each role.
Click Create Task. After creation, a task card appears in the Created group on the board, and you enter the task room to track execution.
Step 2: Track execution
On the board, find the task in the Created or In Progress group and open its details.
Open Task Chat to view the execution messages from the Leader. When you need to add information, send a message to the current task and @ the corresponding Agent.
If the task has been split, use the Task Information Panel to view the subtasks and their dependencies. For a description of each area on the details page, see View task details.
Check Events to see the key changes in the task.
Step 3: View results and accept
After the task enters Pending acceptance, go to the Task Chat and open the Result Card.
Read the result description, and preview or download the submitted files.
Check whether the total agenda duration, the completeness of the content, and the preparation checklist meet the requirements.
If the requirements are met, perform the acceptance operation on the card. If revisions are needed, enter specific revision feedback and send it. For details, see Accept or request revisions.
After acceptance passes, the task changes to Completed. After you submit revision feedback, the team continues processing and resubmits the results for review.
Create a task
Task creation provides three entry points. Choose one based on your scenario:
| Entry point | Location | Scenarios | Who organizes the task information |
| Create through conversation | A private chat with the Leader, or @ the Leader in the team chat | You want to clarify the goal and add information through conversation before the Leader organizes the execution | The Leader organizes it based on the requirements |
| Manual Creation | In the task board, choose New Task > Manual Creation | The task content and the executing team are already defined, and you want to create the task directly on the page | You enter the information |
| AI Creation | The AI Creation entry in the New Task window | After you select a Leader and describe the requirements, you move into a conversation with that Leader, who continues to complete the task creation | The Leader organizes it based on the requirements |
Whichever method you use, state the work goal, the required materials, the expected results, the acceptance requirements, and the operational limits so that the team can understand and execute the work accurately.
Create through conversation
Describe the requirements to the Leader and explicitly ask the Leader to create a task. You can chat with the Leader privately or @ the Leader in the team chat, and state the work to be completed, the expected results, and the acceptance requirements. The Leader creates the task based on the requirements. If information is missing, you can continue to add it through the conversation.
For example: "Create a task to develop a 60-minute project kickoff meeting plan, including the meeting agenda and a pre-meeting preparation checklist for each role, and submit the Markdown file."
After the task is created, subsequent execution moves to the corresponding task room. Open the task from the task information in the Leader's reply or from the task board, and enter the task room to track progress, add information, and view results. Whether the task was created is determined by the task record. You can confirm a newly created task that has not started execution in the Created group on the board.
Create manually
Open the task board, click New Task, and select Manual Creation.
Enter the task title and content, select the executing team, and set the priority as needed.
Click Create Task. After creation, the Leader of the selected team enters the corresponding task room to organize the execution.
Manual creation sets the currently logged-on user as the reviewer by default. To receive results in a specific session, configure a reply path.
The New Task window also provides the AI Creation entry, which is essentially an entry inside the manual creation window that switches to conversational creation: after you select a Leader and describe the requirements, the App enters a conversation with that Leader, who continues to complete the task creation. You can enter the task information yourself, or use this entry to let the Leader organize it.
Configure a reply path
Only when you need to deliver results to a specific session, expand Add Reply Path in the manual creation window. If you are unsure how to fill in the fields, contact an administrator for help.
| Field | Description |
| Channel | The identifier of the channel that receives the results. For example, in-App sessions use matrix |
| Room | The identifier of the target session, not the session display name |
| Object | The identifier of the target user to notify, not the user nickname |
Matrix is the communication service used for in-App chat in AgentCore App. Room and Object require the full identifiers assigned by the system, not the session name or the user nickname. An administrator can provide these configuration values, and regular use does not require understanding the identifier format. For the delivery channels and receiving methods for results, see Receive result callbacks.
Find and view tasks
Use the task board
The task board organizes tasks by work state.
| Board group | Tasks included |
| To Confirm | Tasks that are blocked, paused, failed, or pending acceptance. Open a specific task to view the reason |
| Created | Tasks that have been created but have not started execution |
| In Progress | Tasks that are being executed |
| Completed | Tasks that are completed |
| Cancelled | Tasks that are cancelled |
To Confirm is a board group name, not a single task state. Check the status label on the card to determine whether the task is waiting for acceptance or needs attention for a blockage or failure.
Search and filter
Use Search Tasks to find tasks by keyword.
Narrow the view through the team drop-down list.
Select Only My Tasks to view the tasks created by the current account.
Switch between Active Tasks and Archived Tasks to find tasks in different archive states.
To fetch the list again, click Refresh.
View task details
After you open a task, the page contains two areas: Task Chat and Task Information Panel. The Task Chat shows execution messages, collaboration discussions, result cards, and your exchanges with Agents. The Task Information Panel contains the following sub-areas:
| Sub-area | What you can view |
| Subtask Dependency Graph | The subtasks that have been split out, their states, and their predecessor-successor dependencies |
| Events | Key changes in creation, execution, and result processing. Some events link to the corresponding chat messages |
| Files | The files related to the current task. You can search for and open files |
| Members | The members participating in the current task. You can view member information |
| Details | The task content, Task ID, Assignee, reviewer, team, source, delivery target, and creation time |
Details includes Assignee, which is the Agent assigned to execute the task. The Task ID can be used to report issues to an administrator.
Track tasks and collaborate
Communicate in a task
To add background, explain limits, or ask about progress, send a message to the current Task Chat. To have a specific Agent handle something, @ that Agent. For the overall plan and delivery issues, communicate with the Leader first.
Keep the additional information for the same task in the Task Chat as far as possible, so that the team works around the same set of requirements. When you change a delivery requirement, state the specific change and whether the original requirement still applies.
For example:
@Leader 请将会议方案中的风险讨论增加到 15 分钟，总时长仍保持 60 分钟。
请相应调整其他环节，并在最终说明中列出调整内容。View subtasks and dependencies
After the Leader splits the work, use the Subtask Dependency Graph to view the state and the execution order of each item. A subtask shown as not started is not necessarily abnormal. When a predecessor dependency exists, the subtask starts only after the preceding work meets its conditions.
Splitting, assignment, and progress are organized by the team. You can make requests through the chat and learn about progress through the dependency graph and the event records.
Understand task states
| State | Meaning and recommended actions |
| Created | The task has been established and is waiting for execution. Check the chat for the reception and preparation status |
| In Progress | The team is processing the task. Check messages, events, and subtask progress |
| Blocked | The work has encountered a condition that temporarily prevents continuation. View the reason first, then add materials or resolve the issue before resuming |
| Paused | The task is paused. To continue, click Resume |
| Pending acceptance | The results have been submitted and are waiting for the reviewer to check |
| Completed | The task is complete. Tasks that require acceptance have passed acceptance, and tasks that do not require acceptance are complete after the results are submitted |
| Failed | This execution failed. Confirm the reason first, and retry after the conditions for continuing are met |
| Cancelled | The task has been cancelled and will no longer continue under the original flow |
A chat reply, a new file, or a completed subtask does not mean that the overall task is complete. Overall progress is determined by the task state and the formally submitted results.
View results and accept
View results and files
Formally submitted results are presented in the Result Card, which includes the result description and the associated files. You can preview supported files in the card or download them locally for inspection. You can also find related files in the Task Information Panel under Files.
The file list may contain both process files and result files. When you accept results, check the files associated with the current Result Card first to avoid mistaking earlier versions for the final results.
Accept or request revisions
After you check the results, you can accept them or request revisions. For operation permissions, see Permissions.
To request revisions, enter specific feedback in the Result Card. For example:
议程总时长符合要求，但会前准备清单缺少测试角色的材料要求。
请补充测试范围、环境和风险清单，并重新提交完整文件。After you send the revision feedback, the task returns to the execution flow. After the team makes the revisions and resubmits, check the new results.
For tasks that require acceptance, expressing approval through the chat cannot replace the formal acceptance operation on the card. For how acceptance is handled on behalf of a reviewer on an external channel, see Permissions.
Receive result callbacks
Messages about task completion and state changes are delivered back to the originating session of the task, including in-App chat (Matrix) and instant messaging (IM) tools such as DingTalk and Lark. You can receive the notifications in the original session, track task progress, and view results. Without a configured reply path, view and accept results directly in the Task Chat. To deliver results to a specific session, see Configure a reply path.
Manage tasks
Task operations
The task card or the details page shows the available operations based on the current state. Read the confirmation prompt before you perform an operation.
Pausing, cancelling, and retrying do not undo the external operations that the Agent has already completed. When external system changes are involved, confirm the actual impact against the execution records.
| Operation | Applicable situations | Description |
| Pause | In Progress tasks | Pauses the current task, which can be resumed later. Does not undo completed external operations |
| Resume | Paused or blocked tasks | Continues the task. For blocked tasks, resolve the blocking reason first |
| Retry | Failed tasks | Advances the task again. Confirm the failure reason and the required conditions first. Does not undo completed external operations |
| Cancel Task | Unfinished tasks | Cancels the current task. Does not undo completed external operations. Cancelled tasks have no direct resume entry |
| Archive | Tasks in the Created, Paused, Blocked, Completed, Failed, or Cancelled state | Moves the task to the archived view. In Progress and Pending acceptance tasks cannot be archived directly |
| Unarchive | Archived tasks | Moves the task back to the active view. Unarchiving does not equal resuming execution or reopening a completed task |
| Delete | Archived tasks | Permanently deletes the task record. Deleted records cannot be recovered |
Each operation must satisfy both the identity permission and the task state conditions. For details, see Permissions. When subtasks pending acceptance have not been handled, handle the related results first.
Permissions
The permissions to view, manage, and accept a task are evaluated separately. The following table applies to App users. A single user can hold multiple identities at the same time, and an operation must also satisfy the task state conditions in the preceding table.
| Identity in the current task | View tasks and files | Pause, resume, retry, cancel | Archive, unarchive, delete | Accept results or request revisions |
| The task creator, and still within the visibility scope of the task | Yes | Yes | Yes | Must also be the reviewer of the task |
| A human participant in the task | Yes | Yes | Yes | Must also be the reviewer of the task |
| A designated reviewer | Determined by the visibility scope of the task | Determined by whether the user also holds the creator or human participant identity | Determined by whether the user also holds the creator or human participant identity | Yes |
| Other users who have not joined the task | No | No | No | No. For designated reviewers on external channels, see the notes below |
Acceptance identity is independent: Having view or management permissions does not mean that you can accept results. A reviewer designated through an external IM can give explicit feedback in the corresponding session, and the executing Agent handles the acceptance on that reviewer's behalf and confirms that the task state has been updated. This does not automatically grant task access or management permissions in the App.
Team membership and task membership are different: Belonging to a team does not mean that you can access all of the tasks of that team. The visibility scope of the current task applies.
Parent and child tasks are authorized separately: Participating in a parent task does not automatically grant access to or operation permissions on a child task. You must join each task separately.
Visible buttons are not authorization: Whether an operation is allowed depends on the validation result of the current account's permissions and the task state. Guests cannot perform write operations.
Multi-team task collaboration
Scenarios
When a piece of work requires several specialized teams to cooperate, a parent team can coordinate multiple child teams. For example, product release preparation requires the product team to organize the release content, the development team to provide change notes, and the testing team to submit verification conclusions, after which the parent team consolidates the release materials.
Collaboration model
The parent team takes on the overall goal and splits out the work that each specialized team must complete. An Agent with coordination responsibilities can act as a Worker in the parent team and, at the same time, as the Leader of a child team, organizing that team to complete the work.
| Level | Responsibilities |
| Leader of the parent team | Understands the overall goal, organizes the division of work, tracks each item, and consolidates the final results |
| Coordinating Agent in the parent team | Takes on the corresponding subtask, organizes the child team it leads to execute the work, and reports the results back to the parent team |
| Child team | Creates and executes its own tasks around the assigned work, and splits them into subtasks as needed |
The same Agent can take on different roles in different teams. Multi-team collaboration requires the teams and the member relationships to be configured in advance.
Initiate and track
Select the parent team responsible for overall coordination and create a task.
State the overall goal, the delivery requirements, and the content that each specialized area must cover.
The parent team organizes the division of work. Specific work can be completed directly or through collaboration with child teams.
Track the overall progress, add requirements, and view the final results from the parent task.
When you need details from a specific child team, view the corresponding task if you have the access permissions.
Example requirement:
请统筹本次产品发布准备，组织完成发布内容、技术变更说明和测试结论，
最终提交一份统一的发布检查清单。
请注明每项工作的结论、相关文件和仍未解决的问题。Results and operational boundaries
The Agent with coordination responsibilities reports the results of a child team back to the parent team, which then organizes and submits the final results according to the overall requirements. The completion of one child task does not mean that the overall task is complete. Check the results submitted in the parent task.
Parent and child tasks have their own execution states. When you pause, cancel, or resume a parent task, do not assume that the child team tasks automatically perform the same operation. The parent team must confirm the actual state of each item. For cross-team access rules, see Permissions.
When child work is blocked or fails, ask the Leader in the parent task to explain the impact and the next steps. The subtask dependency graph on the page shows the split relationships within the current task and is not a complete overview of all child team tasks.