Connect Linear

Solutioneer uses the Composio linear toolkit for Linear writeback. Two skills — integration-fit-gap-analyzer and poc-handoff-orchestrator — write to Linear.

Prerequisites

• A Composio API key in .env.
• A Linear account with permission to create projects, milestones, and issues in the target workspace.

What gets connected

The linear toolkit exposes these tool slugs to Solutioneer:

• LINEAR_CREATE_LINEAR_ISSUE — create an issue.
• LINEAR_SEARCH_ISSUES — search existing issues (to avoid duplicates).
• LINEAR_CREATE_LINEAR_PROJECT — create a project.
• LINEAR_CREATE_PROJECT_MILESTONE — add a milestone to a project.
• LINEAR_CREATE_PROJECT_UPDATE — post a project update.

How to connect

The normal flow runs inside Codex:

1. Ask for a Linear write. For example: “Create a Linear project for this POC plan with one milestone per success criterion.”
2. Codex verifies that COMPOSIO_API_KEY is present.
3. Codex checks whether the linear toolkit is connected.
4. If it is not, Codex offers Connect now / Skip.
5. Connect now opens the Composio hosted login page in a browser tab.
6. You complete the Linear OAuth flow.
7. Codex polls the connected account until it becomes ACTIVE.
8. Once active, Codex executes the write.

Connect from the Composio dashboard

1. Open the Composio dashboard.
2. Go to Connections.
3. Find the linear toolkit.
4. Click Connect and pick the Linear workspace to grant access to.
5. Confirm the connection shows as Active.

Which skills write to Linear

• Integration Fit Gap Analyzer — creates Linear issues, but only for gap and unknown rows. supported rows never become issues.
• POC Handoff Orchestrator — can create a full project scaffolding: a Linear project, a set of milestones, an issue per POC risk, and a project update.

Confirmation rules

Codex confirms before writing. The target team, project, and issue labels (when provided) are all part of the confirmation. If you did not ask for a Linear write, it will not push to Linear.

Troubleshooting

• Wrong team. Linear projects are team-scoped. Make sure the team you named matches the Composio connection you authed with.
• Fit-gap created too many issues. By design the fit-gap only creates issues for gap and unknown rows. If you want fewer issues, tighten the fit-gap first — do not pressure the skill to mark rows supported without evidence.
• Milestone dates missing. Codex does not invent dates. If you did not provide notes.milestones or notes.targetDates, milestones will be created without due dates.

See Troubleshooting for more.