My Tasks¶

Tasks are the primary entry point for your collaboration with the Agent. Compared to casual questions, tasks are better suited for carrying work that has goals, context, a process, and results.

Create a Task¶

Click Create in the Agent workspace, and fill in the task title and description. The title is used for quick task identification, and the description is used to explain the goals you want the Agent to handle and the necessary context.

After creating a task, the system will enter a collaboration session.

Advance the Session¶

After entering the task session, you can tell the Agent what to do next, just like chatting.

Using @ in the session input allows you to reference system entities within the current workspace, enabling the Agent to analyze around specified objects. Currently supported entities include services, applications, dashboards, hosts, and containers. More entity types will be supported in the future.

After referencing an entity, the Agent can narrow the analysis scope by combining the entity's context, for example:

Referencing a service to analyze abnormal requests, error rates, latency changes, and upstream/downstream impacts of the service.
Referencing an application to analyze access, performance, errors, and user experience issues related to the application.
Referencing a dashboard to interpret metric trends, anomaly points, and correlated data within the dashboard.
Referencing a host to check host resources, load, logs, and related alert clues.
Referencing a container to analyze container status, resource usage, restarts, logs, and the cluster environment.

In the session, you can also:

Use Skills to have the Agent process in a specific way.
View the Agent's thought process and execution results.
Stop the Agent during execution.
Initiate new requests when needed.

If the task is complex, it is recommended to let the Agent formulate a plan first, then decide whether to execute it.

Plan Mode¶

Plan mode is suitable for complex tasks, such as problem troubleshooting, solution design, release checks, refactoring assessments, etc.

When using plan mode, the Agent will first help you clarify goals, scope, steps, and risks before proceeding to execution. This reduces misunderstandings and prevents the Agent from taking direct action with insufficient information.

It is recommended to use plan mode in the following scenarios:

The task affects multiple people or systems.
It involves production environments, releases, permissions, or external services.
Multi-step execution is required.
Scope and success criteria need to be confirmed first.
You want the Agent to propose a solution before deciding whether to implement it.

Task Insights¶

Task Insights organizes key information from the session to help you quickly understand what has happened in the current task.

Viewable information includes:

Evidence.
Hypotheses.
Analysis.
Anomalies.
Impact scope.
Conclusions.
Action recommendations.

Task Insights supports timeline and list views. The timeline is suitable for reviewing the task progression process, while the list is suitable for viewing key information by type. If there are many task messages, you can first check Task Insights to grasp the key points.

Task Attachments¶

Task Attachments are used to centrally display files generated during the execution of the current task. The Agent may produce attachments of types such as PDFs, Excel files, reports, export files, etc., during analysis, organization, or result generation.

In the Task Attachments page, you can:

View attachments generated for the current task.
Download corresponding files as needed.

Approval¶

When the Agent needs to perform high-risk actions, approval requests may appear. You can view pending approval items in the session and decide whether to allow them.

Before approving, it is recommended to confirm:

What action the Agent intends to perform.
Which systems or data this action affects.
Whether there are rollback or recovery methods.
Whether this step is truly necessary for the current task.
Whether the operation complies with team processes.

Do not skip approval judgment because the task is urgent.

Stop Execution¶

If you find the Agent is heading in the wrong direction, the task scope needs adjustment, or the current execution is no longer needed, you can click Stop Execution. After stopping, you can add new instructions and then re-initiate the request.

Stopping execution only interrupts the currently in-progress response or operation; it does not mean the task is completed. The task can still continue to advance, or you can let the Agent execute again after adding instructions.

Complete a Task¶

Completing a task is used to formally close out a task. When the task objectives have been achieved, or the current task no longer needs to be advanced, you can update the task status to Completed.

After a task is completed, the team can review key conclusions, main evidence, Task Insights, and output attachments around this task, facilitating review, handover, or subsequent tracking.

Before completing, it is recommended to confirm:

Whether the goals have been achieved.
Whether the key conclusions are clear.
Whether the attachments that need to be retained have been generated and are downloadable.
Whether the main evidence and conclusions are visible in Task Insights.
Whether subsequent action items have been clarified.