Tracker key prefixes on every project, agents that work in your Linear or Jira, development time on the delivery board, a session panel that follows the task, and more

Each project says which keys are its tasks

A project now declares the prefixes of the Linear, Jira or other tracker tickets its work is tracked in, beside its own task key prefix, and only keys with one of those prefixes become its tasks. See task keys.

Every project gets its own task key prefix when it is created, taken from its name (Acme Portal → AP) unless an admin types one, and never one another project or a connected tracker already uses.
A commit, branch or time entry naming a key with the project's own prefix or one of its tracker key prefixes creates that task when it doesn't exist yet. A key with any other prefix names no task, though its time is still tracked.
A connected tracker's ticket with a declared prefix lands in the project, and declaring a prefix moves the organisation's tasks with it that have no project into the project.
When a connected tracker starts sending tickets with a project's own prefix, the project moves to the next free numbered one (CLK → CLK2) and its existing tasks keep their keys.
The project form groups task keys and delivery settings together, and suggests the prefixes the project's commits use that are free to declare, each with one-click Add.
clocktopus init declares the prefixes that at least two of the checkout's commits and branches use, asking only when another project has one.
An archived project gives up the prefixes it declared, so another project can take them over. A late merge in an archived project still links to the task it already has.

Agents work with your Linear and Jira tickets

Agents now use a project's tracker key prefixes to work in the tracker your team plans in. See what the MCP server can do and the skills.

When one of the project's prefixes belongs to a connected Linear or Jira, the agent creates the project's new tasks in that tracker, through its own MCP server, and registers them in Clocktopus at once, before the tracker's webhook arrives.
A new MCP tool, register_ticket, records a Linear or Jira ticket the agent read under its own key, with its title, summary, link, kind and creation date, whether or not the tracker is connected. Calling it again re-syncs the ticket, and follows its key when it moved.
A new register-ticket skill does the same, and your repository's own skills and workflows can call it in one line. It does nothing in a repository that isn't linked to a project, or for a prefix the project doesn't declare. See calling the skills from your own.
create-goal now takes a Linear or Jira ticket (/clocktopus:create-goal BLA-12): it reads the ticket, its sub-tasks and linked issues, and plans the goal as sub-tasks of the ticket, creating the missing ones in the tracker.

This release ships CLI 0.12.0.

Development time and hours per task on the delivery board

The delivery board now shows how long a shipped task took to develop, not only how long it took from creation to shipping. See development time.

Development time runs from a task's first commit or agent session to its pull request being ready for review, or to the merge or shipping when nobody else reviewed it. The board shows the median, with the 75th percentile beneath it.
Beside it, the median hours members logged per task and the median agent runtime per task.
Each hours figure counts only the tasks that have any of that kind, and with fewer than three shipped tasks the board shows how many there are instead of a median.

The session panel follows the task you work on

The Claude Code session panel now keeps up when a session moves from one task to another.

A session that moves to another task's branch, with git switch or into a worktree, is now tied to that task, so its spend lands on the right task. A task you linked the session to after the move still wins.
When the session works on a task in another worktree, as a goal run does, the panel shows that worktree's branch and folder, with a Started in row for the session's own.
The panel's spend no longer shows $0 for every session.

Fixes & improvements

The Work page's Tasks tab now shows who worked on each task as a stack of up to three avatars, like the one on the task's page.
A task's description now links every task key it mentions to that task's page, when you can open it. Keys inside code and words like SHA-256 stay text.
The Tasks tab now lists your tasks when no repository is connected, with a banner linking to where you connect one, instead of hiding them behind the placeholder.
Open task lists now refresh when a commit, branch, entry or session creates a task.
A task that a commit created from its key can now be cancelled.
The Tasks tab and the Time page now list and link only keys that are tasks, and a task key on the Time page links to the task in its own organisation.
A task's hours now count in a project with no linked repository.
Placeholders on the project form now read as hints rather than filled-in values.