A Codex team workflow with your Jira or Linear tasks

Updated

Your tracker already holds what Codex needs to know: the task, its parent and the decisions already on it. CRUX lets Codex read them over MCP and gives each status in your workflow its own instructions, so nobody writes a prompt. This page is for developers who work in the OpenAI Codex CLI and keep tasks in Jira Cloud, Linear, Plane or GitHub Issues.

What goes wrong with Codex alone

Ryan opens Codex on a Jira task about invoice rounding and pastes the task text. The session starts from zero, so he explains the project again. Codex sees the task but not last week's decision to keep the old rounding for existing customers, so it rewrites that code. Megan has three Codex tabs open, and nobody else on the team can see which tab belongs to which task or what state it is in.

Codex reads the project's rules from AGENTS.md, and every developer should keep one. Rules say how the team writes code. They do not hold the decisions made on earlier tasks or say who answers the agent's question.

Connect Codex to CRUX over MCP

You need a CRUX account and a project tied to your tracker project. Each person connects their own tracker account, so the agent acts as the person who started it. Open "Connect your coding agent" in the dashboard, pick the project and Codex, and press "Create my token". The token is shown once, works for one project and acts as you. You revoke it in the dashboard under MCP clients.

Export the token in your shell. Put it in your shell profile or a secrets manager rather than typing it, and never in a committed file:

export CRUX_MCP_TOKEN=YOUR_TOKEN

Then add the server with your project's id in place of PROJECT_ID:

codex mcp add crux --url https://crux.team/mcp/p/PROJECT_ID --bearer-token-env-var CRUX_MCP_TOKEN

The command writes this table to ~/.codex/config.toml, and you can also write it by hand. Codex reads a project's .codex/config.toml only in a trusted project, so the user file is the safer place.

[mcp_servers.crux]
url = "https://crux.team/mcp/p/PROJECT_ID"
bearer_token_env_var = "CRUX_MCP_TOKEN"

Run codex mcp list to see the server.

Connect Codex to Jira

Atlassian's own path is the Atlassian Rovo MCP server, which documents a codex mcp add command, and its guide for ChatGPT and Codex. That gives one developer Jira inside Codex.

With CRUX, Codex reaches Jira Cloud through the crux server above, so it needs no second MCP entry. You connect your own Jira account once in CRUX, and Codex reads and updates tasks as you. On top of the task, it gets the instructions for the task's status and the artifacts earlier steps left on it.

Codex and Linear

Linear's own path is its MCP server, with a codex mcp add linear command and a browser sign-in. CRUX takes the same crux entry as for Jira: the project in CRUX is tied to one Linear team, and you connect your own Linear account through OAuth. Cycles become sprints when the team has cycles switched on.

Install the plugin in Codex

The plugin needs a CRUX account, because every skill calls your project's CRUX MCP server. It is open source under the MIT license:

codex plugin marketplace add cruxteam/skills
codex plugin add crux@cruxteam

What works in Codex and what does not

We ran the commands on this page in Codex CLI 0.169.0 on 13 November 2026. The plugin installs with its skills, and Codex calls the crux tools with your token. Codex asks you to approve each crux tool call. To let them run without asking, add default_tools_approval_mode = "approve" to the [mcp_servers.crux] table.

The setup command /crux:crux-config runs in Claude Code only, and only a project admin can run it. Someone on the team sets the workflow up there, and Codex users then take steps. The project wiki is not served over MCP: Codex reads the wiki from the repository checkout, like any other file.

Through MCP, Codex reads a task with its child tasks, comments, attachments, links, statuses and sprints, and searches other tasks. It creates and updates tasks, adds comments and uploads artifacts. It changes a status or an estimate only with your consent. Nobody acts under a bot account, and text an agent writes starts with a robot emoji.

Start a step and approve at checkpoints

A person starts every step. The plugin's README gives the Codex form of the crux-run skill, $crux:crux-run CR-12 developer. It claims the step, creates the git worktree .claude/worktrees/CR-12 on the branch CR-12 and prints one command to run in a new terminal tab, where Codex fetches the step's instructions from CRUX.

We have not yet run a whole step from Codex or checked how the board shows it. You can also start a step from the dashboard: press "Copy prompt & wait" on the task's "Run on my machine" card and paste the prompt into Codex.

At an approval checkpoint the agent stops and shows you its understanding, its plan or its result. It posts the artifact to the task only after you approve. You move the task to the next status yourself, and CRUX never changes your tracker's settings.

Limits

  • CRUX is in beta, and one founder builds it.
  • A step you claim stays yours until you start its session or unassign it in the dashboard.
  • CRUX is a hosted service only. It does not support Jira Server or Data Center.
  • Codex runs on your own subscription. CRUX sells no usage credits and adds no token markup.
  • One person uses CRUX free. A team of 2 to 10 people pays $49 per active project a month, a team of 11 or more pays $120, and the first month of every project is free. During the beta nothing is charged. See the pricing page.

Start free. For the dialog and the other agents, read Connect your coding agent. The Claude Code page covers the setup command. The same project works with Cursor, and the dialog also has entries for Gemini CLI, OpenCode and Zed.

FAQ

Can Codex read Jira tasks?

Yes, through CRUX. You connect your own Jira Cloud account, and Codex reads and updates tasks over MCP as you.

Can Codex read Linear issues?

Linear's own MCP server gives one developer Linear inside Codex. Through CRUX, you connect your own Linear account, and Codex reads and updates the team's issues over MCP as you, with the instructions for each status.

Can Codex read GitHub issues?

Yes, when your CRUX project is tied to a GitHub repository. Codex reads and updates its issues as you, and statuses come from a GitHub Projects board or from labels. GitHub Issues has no attachments, no URL links and no task deletion.

Do I need Claude Code to use CRUX with Codex?

Only for the setup command. One project admin runs it in Claude Code, and everyone else can stay in Codex.

Do the skills work without a CRUX account?

No. Every skill calls the CRUX MCP server of your project.