Start from the issue. Finish on the board.

Connect Linear or Jira on any machine and start a Claude Code session straight from an issue. Claude gets the description, comments and images, works in its own git worktree, and the issue moves to In Progress. When the work is done, you say so, and one click opens the pull request and moves the issue to In Review.

Commission's Issues page with an issue open: its description, where it runs, its own git worktree and Start session

How it works.

Start a session from an issue

The Issues page lists your issues from every connection. Open one and choose Start session: Claude gets the title, description, comments and images, and the issue moves to In Progress if you've turned that on. Already working on it? Link the issue to the session you have.

  • Linear with a personal API key, several connections per machine
  • Jira Cloud with your Atlassian email and an API token
  • Jira Server and Data Center 8.14 or later, with a personal access token
An issue open in Commission, with Start session
A session started from an issue, on iPhone

One worktree per issue

A session started from an issue gets its own git worktree and branch, so two issues on one repository never trample each other. Archive the session and the worktree goes; the branch stays. Anything with uncommitted changes is left alone.

You say when it's done

After a finished turn, Wrap up asks Claude to commit what's left and write its summary. Then one click moves the issue to In Review with that summary. With GitHub connected on that machine, the same click pushes the branch and opens the pull request.

  • Claude is asked not to move the ticket or open the PR itself
  • Nothing changes on your board without your click
  • Turn both switches off and a connection stays read-only
How Wrap up works →
A Commission session: the conversation with Claude and a diff of each file it changed
A Commission session on iPhone, with the conversation and its diffs

CI and review come back to the session

Once the pull request is open, its checks show on the session. A failing run lands in Needs you with Send the failure to Claude, and review comments arrive in the session's review strip, ready to go out with your next message.

  • GitHub connects per machine with a fine-grained token, which stays there
  • The push uses that machine's own git

File it, schedule it, hand over the whole list

File a new Linear or Jira issue without leaving Commission. Let a machine start a session for each new issue, or at set times. Or give a coordinator a list of tickets: it runs them as sessions side by side and keeps a record of what shipped.

Coordinate a list of tickets →

Good to know.

  • Keys stay on the machine. Each connection lives on the machine that uses it, so work and personal accounts never mix. Tie a connection to spaces to see its issues there first.
  • Self-hosted Jira needs https. The machine must reach your Jira and trust its certificate. Server and Data Center need 8.14 or later.
  • GitHub for pull requests. Pull requests, CI and merges use GitHub. Without it, the issue still moves to In Review.

Questions.

Does Claude change my tickets on its own?

No. Claude is asked to wait for you. The issue moves to In Progress when the session starts, if that switch is on, and to In Review when you click. Turn both off and Commission only reads.

Which Jira versions work?

Jira Cloud, with an Atlassian email and an API token, and Jira Server or Data Center 8.14 or later, with a personal access token over https.

Where are my API keys stored?

On the machine you connected them on, used only by that machine's sessions, so work and personal accounts never mix.

What does Claude get from the issue?

The title, description, comments and images, plus any note you add before it.

Does it work with GitLab or Bitbucket?

Not today. Pull requests, CI and review comments work with GitHub.

Set up your hub in about ten minutes.

Free while Commission is in beta. No account to create.