Linear and Claude Code workflow for a team

Updated

CRUX connects the tasks a small product team keeps in Linear to the coding agents the team already uses, such as Claude Code, Codex and Cursor. Every Linear status gets an owner role and a ready step, and the agent reads the task with its history before it writes code.

The problem on a Linear team

On Monday the team agreed in a comment on the parent task that export stays CSV only. On Thursday a developer opens a child task, pastes its text into Claude Code and asks for an Excel export. The agent sees only the pasted text, so it agrees and builds it. The reviewer finds the contradiction in the open pull request.

What CRUX adds on top of Linear

A task in CRUX is a Linear issue. CRUX adds a workflow that, for each status, names the owner role and the agent steps. Each step posts an artifact to the task. How CRUX works walks through one task.

Set up the Linear integration and start the first step

  1. Create a project. Create an organization and a project, choose Linear as the tracker and pick the Linear team. An admin of your CRUX organization connects Linear once. A CRUX project is tied to one Linear team.
  2. Link your Linear account. Each team member links their own Linear account on the Connected accounts page. Linear opens its OAuth page and asks for read and write access. If your workspace requires admin approval for third-party apps, CRUX gives you a ready message to send your admin. Nobody acts under a bot account, so comments appear under the name of the person who started the step.
  3. Connect your coding agent. Open "Connect your coding agent" and create a personal token. Keep it in the CRUX_MCP_TOKEN environment variable. The dialog gives the setup for your agent, which connects to https://crux.team/mcp/p/<projectId>.
  4. Map statuses to roles. A project admin installs the crux plugin and runs /crux:crux-config in Claude Code, which needs the connection from step 3. The agent reads your team's Linear statuses, asks who owns each status and where the checkpoints go, and opens a pull request with the workflow. A project without a code repository gets the workflow imported directly. Without Claude Code, choose "Start from the template" or "Build from my board" in the dashboard.
  5. Start a step. In Claude Code run /crux:crux-run ENG-123 planner, with the Linear issue ID as it is. In another agent, open the task in the CRUX dashboard, press "Copy prompt & wait" and paste the prompt into your agent.

How Linear statuses map to workflow steps

The template a new project starts from looks like this. While you set it up, you match its statuses to your team's Linear statuses and change the roles and agents.

StatusOwner roleAgentStep artifact
To DoPMrefineracceptance criteria
In ProgressDeveloperplannerimplementation plan
In ReviewDeveloperreviewerreview report
DonePMnonenone

What the agent reads and what it may change

The agent reads the task, its parent and child tasks, comments, attachments and links. It lists the team's statuses and searches tasks, also by label. Approved decisions are in the comments, because every earlier step posted its artifact there as a structured comment. When the Linear team has cycles switched on, they appear as sprints, so the agent sees what the team planned next.

The agent does not read the project wiki over MCP. An agent on your machine reads the wiki from the repository checkout, like any other file.

The agent can create and update tasks, add comments and relations, and upload attachments. It is told to change a status or an estimate only when a person asks. Deleting a task takes a preview and then a second call that confirms it. At a checkpoint the agent shows its draft artifact in the chat and posts it after the person says ok. Text an agent wrote starts with a robot emoji, 🤖.

How is CRUX different from Linear's own coding sessions?

Linear agents include Linear's own cloud coding agent: a person delegates an issue to Linear, a coding session runs in Linear's cloud and returns a draft pull request. Other agent runners also take an assigned issue and return a pull request, and Jira has its own agents that work the same way. In CRUX a person starts each step. Roles include PM, QA and the lead as well as developers. The agent runs in each person's own coding agent, on that person's subscription. Task-to-PR agents compares these products. Checked on 13 November 2026.

Limits

  • A CRUX project is tied to one Linear team, not to the workspace.
  • CRUX is a hosted service only. There is no self-hosted CRUX.
  • /crux:crux-config runs in Claude Code only. With another agent, set the workflow up from the template or from your board in the dashboard.
  • An agent that runs on CRUX in the browser reads the repository and cannot change it.
  • CRUX is in beta and one founder builds it.

Next step

Start free. The setup for each agent is in Connect your coding agent.

FAQ

Can the agent move a task to another status?

Only when the person who started the step asks for that change. CRUX does not change your Linear settings.

Which coding agents work with Linear through CRUX?

Any MCP client. The "Connect your coding agent" dialog has the setup for Claude Code, Codex, Gemini CLI, OpenCode, Cursor and Zed.

What does it cost?

One person uses CRUX free. A team of 2 to 10 people pays $49 per active project per month, and a team of 11 or more pays $120. The first month of every project is free. During the beta billing is not switched on, so nothing is charged. See the pricing page.

Other trackers

CRUX also works with Jira Cloud, Plane and GitHub Issues.