All changes
v1.15.0

Tasks, goals, and the agents that work them, and more

Tasks from Linear, Jira and Clocktopus

Clocktopus used to see your tickets only as keys in branch names and commit messages, so a ticket's cost was something you pieced together from reports. A task is now a thing in its own right, with every commit, pull request, time entry and agent session tied to it.

  • Linear and Jira send each ticket's key, title, description, kind and dates over a signed webhook. Connect them on the Integrations settings page.
  • Create tasks in Clocktopus from the web app, the CLI or an agent over MCP. A task belongs to the organisation, and takes a project when the first branch, commit or entry names its key.
  • A task has a kind, bug, feature, improvement or tech, and can be marked refined once it's ready to work on.
  • The app says "task" everywhere it used to say "ticket".

We wrote about why in Scrum is dead?.

Every task has a stage

You never set a task's stage. Clocktopus records when each commit reaches each branch, through merged pull requests, and a task is done when its work reaches one of the project's delivery branches. You can see how long a task took to reach each branch.

  • A pull request's task comes from its title when the branch names none.
  • A draft pull request leaves its task in progress, not in review.
  • A task whose pull requests all close without merging is cancelled. You can also cancel any task from its menu until work on it resumes.

The Work page and the task page

  • Work → Tasks lists tasks grouped by stage, with quiet in-progress tasks in a Stale group and a badge on tasks an agent is working. Work → Pull requests lists pull requests. Both update live.
  • A task's page shows a timeline of its commits, pull requests, time entries and agent sessions, its description, its branch and its cost.
  • Cost follows one rule everywhere. An agent session's spend is shared across the tasks it worked on, and clocked time no commit accounts for goes to the task the agents were working on. Hours come first, money is shown only to owners and admins, and members see a task's total hours, not just their own.
  • Task keys in time entry descriptions link to the task.
  • Press Ctrl+K on any page to search tasks. The best match comes first, and a typo still finds it.

Goals

A goal is an ordered list of tasks with a short number, such as G-3, that agents and skills accept. A goal's card shows each task's stage as a dot, reads Ready to ship once every task has merged, and closes once every task reaches a delivery branch. You can also close one by hand.

Agents pick up the work

  • MCP tools let an agent create, search and read tasks, plan goals, take the next task and tie its session to a task.
  • Skills: start-work carries a task, or a whole goal as stacked pull requests, through to an open pull request. create-task and create-goal write work an agent can pick up, and refine checks tasks and marks them ready.
  • clocktopus agent setup installs the Clocktopus plugin for Claude Code, and the skills and MCP server for Codex, OpenCode and Cursor. You choose which agents and extras to set up. Cursor's runtime is recorded too.

Agent skills and MCP server cover both.

clocktopus init

One command sets up a checkout: it signs you in, picks the organisation and project, links the repository, installs the GitHub App or a webhook, waits for GitHub's first ping, and runs agent setup. The Git connection page shows that ping and flags any webhook events that are missing. See Set up a checkout.

A delivery board that follows tasks

The dashboard's delivery board follows the period's tasks from created to shipped. It shows where they stand, flags the bottleneck, and says whether each figure is ahead of, on or behind your usual pace. It charts tasks shipped beside pull requests merged per day, stacked by complexity. Deployment frequency, change lead time and cycle time by stage come from when work reaches your delivery branches.

Fixes & improvements

  • An organisation sees only the git data its own webhooks and App installations received.
  • A force push opens the day's session and is priced from the clock-in.
  • The delivery strip and rail count the project's merges, and projects and members with no hours in the period are still listed.
  • Other members' Work pages update on agent sessions and manual entries, and the task page shows the whole team's timeline.
  • A repository outside the GitHub App's account is pointed to a webhook instead.
  • Agent setup supports OpenCode 2, and setup and doctor find the repository from any remote.
  • The welcome screen's project step waits for your organisation instead of failing with "That project could not be created".
  • A new organisation no longer gets a default job role.
  • Images in blog posts open full size when clicked.
  • The summary report's Pull requests tab and ticket flow table are replaced by the Work page.