Who worked on a task, stacked pull requests kept together, agent session details, inline review findings, and more

See who reported a task and who worked on it

A task's page now names the people behind it, not only the work. See how far each task has got.

A new People row shows who reported the task: whoever created it in Clocktopus. Linear and Jira tickets have no reporter.
Beside it, a stack of avatars shows everyone with commits, manual time entries, pull requests or reviews on the task, in the repositories and projects you can see. Hovering an avatar gives the person's name and what they did, and anything past six people collapses into a +N chip.
Git authors not matched to a member of your organisation are listed by their git name or login, with a dashed avatar. Commit authors nobody has answered for are counted in a link to To sort.
Agent sessions don't make someone a collaborator; they stay on the timeline.
The MCP tool get_task returns the reporter and collaborators too.

Stacked pull requests stay together on the Work page

The Work page's Pull requests tab now keeps the pull requests of a GitHub stack, made with gh stack, together within their status group. See the Work page.

The top of the stack comes first, and each pull request carries a badge with its place in the stack, such as 2/3.
It works for repositories connected by webhook as well as through the GitHub App. Bitbucket has no stacks.
When a stack changes, each pull request's place updates on its next event, so one with no event since keeps its old place.

Open an agent session to find it again

Each agent session on a task's timeline now opens a dialog, so you can find the session again on the machine that ran it. See one task.

It shows the agent's own session id and, for Claude Code and Codex CLI, a command to resume it, each with a copy button.
The directory the session ran in is shown only to the member who ran it. Everyone sees its branch, repository, agent version and terminal type.
It shows when the session started and ended, or that it is still running, and its agent time, with this task's share when the session spans several tasks.
Owners and admins also see its spend: this task's share and the session's total.

Review findings land on the line they're about

review-work no longer gathers what it leaves for you into one comment. It now posts a single pull request review. See the skills.

Each finding is an inline comment on the line where it should be fixed, saying what is wrong, the case where it goes wrong, why it wasn't fixed and a recommended fix, as a suggestion you can apply when the fix replaces only those lines.
The review's summary names up to three things the work does well, what the session fixed and in which commit, and how many findings were dropped.
A finding on a line outside the pull request's changes goes in the summary with its file and line.
When start-work runs through a goal, every task's pull request now joins the goal's gh stack with the right base, and a branch cut from another open pull request's branch joins that pull request's stack.
clocktopus agent doctor now reports a skill as outdated when any of its files changed, not only its main one.

This release ships CLI 0.11.0.

Fixes & improvements

Entries on the Time page now show the short SHA of the commit behind them. Clicking it opens the commit on GitHub or Bitbucket in a new tab, without opening the edit dialog.
In the Add clock-out and clock-in dialog, the next entry's description now sits on its own line, cut short with the full text on hover, and the checkbox to shorten that entry is checked by default.
Task summaries created or updated over the MCP server can now be up to 5000 characters, up from 2000.