agent-team-message-list

To list run messages and audit communication history, use the agent-team message list command with the required --run parameter. You can apply optional filters like --task, --from, --to, --kind, and --unread to scope the returned data.messages.

Yes, you can filter unread messages for a specific task by combining the --run, --task, and --unread parameters. This scopes the message history to only show unread communications within that defined task boundary.

Debugging workflow communication history is best done by listing run messages with sender and recipient constraints. Applying the --from, --to, and --kind filters isolates specific message exchanges, returning structured data.messages for targeted auditing.

To check message history changes after a specific version update, use the --after-version parameter. This filters the run messages to return only the communications that occurred following the specified version, enabling precise version-based auditing.

Yes, the message list command supports limiting returned records through the optional --limit parameter. This restricts the volume of data.messages retrieved from the run-scoped messaging context during a single query.

The only required parameter to inspect run-scoped message history is --run, which targets the specific workflow run ID. All other parameters like --task, --kind, and --limit are optional filters for refining the returned data.messages.