Currently, there's no way to see who triggered a Chunk task directly from the Chunk UI. To find this information, users must navigate to the Pipelines page, locate the chunk-task workflow for the relevant branch, drill into the corresponding job, and find the triggering step in the job output — a multi-step process that requires knowing where to look.

Request: Surface the invoking user's identity (the person who clicked "Fix workflow" / triggered the Chunk task) directly on the Chunk chat or task page.

Use case: A team noticed an unexpected PR created by the circleci-app GitHub user and had no way to determine who triggered it from the Chunk UI alone. Attribution visibility would help teams audit unexpected Chunk activity and maintain accountability, especially in organizations where Chunk access isn't tightly restricted.