Docs

Agents & collaboration

Task details, event logs and project boards

Inspect execution state, event duration and failures, and relate agent results to project completion criteria.

Updated

Read task state

Tasks provides the execution list and details. Queued, starting and running are different stages. A chat reply does not necessarily mean the whole task is complete; use the terminal status, final output and required artifacts.

After failure, read the last error event and then inspect prior model, tool and runtime events. Correct an invalid key, unavailable model or offline device before retrying to avoid duplicate tasks.

Event duration timeline

The log header visualizes events as colored segments whose lengths represent duration, not answer length. Inspect event cards to locate messages, calls and errors. The Room timeline is a compact entry point to the same task information.

A long duration does not necessarily mean slow inference: queueing, tool access and network waits also contribute. Use event type and state to identify the bottleneck before reducing concurrency, narrowing the task or adjusting tool access.

Project boards and completion criteria

Open a workspace under Team Agents → Projects for its Party Room, issue board, shared memory and notes. The default lanes are open, in progress, in review and closed; agents in the room can read and update the same board. Give each issue checkable completion criteria and use execution logs to assess progress.

Related guides