Connect Linear
Connect a Linear workspace so missions can start from an issue and report back on it.
Overview
Linear is one of the ways a project's work can be planned. Connecting it turns SHIP into an agent your team can mention on an issue: the mission starts from the ticket and narrates its progress there, with nothing to install for the people filing the work.
It is optional. A project can use GitHub Issues instead, or no tracker at all and take its work from the terminal. See Ways of working.
Steps
Authorize the workspace
On the Connect step of onboarding, click Connect Linear and complete Linear's OAuth flow. The grant makes SHIP an agent in your workspace, assignable and mentionable, and lets it read issues, post updates, and run agent sessions.
Pick the team
On the Project step, choose Linear as where this project's work is planned, then select the team. A project is scoped to one team; issues in it can be handed to the agent.
Starting a mission
Mention @SHIP on an issue, or assign the issue to the agent.
The mission replies in Linear's agent session, the same surface you see other agents respond in, and posts its plan, review verdict and QA verdict as it goes. The pull request it opens links back to the issue.
An issue written for a person is usually written well enough for an agent: what you want, and how you will know it is done. Acceptance criteria as checkboxes are what QA verifies against, so they are the part worth being specific about.
Steering a running mission
Reply on the issue. The agents pick the instruction up on the mission's open pull request, and a request aimed at one stage's output re-runs that stage rather than restarting everything.
@SHIP pause, @SHIP resume and @SHIP stop control the run. The console detail page has the same three as buttons, and a mission that has escalated for attention is restarted from there.
Troubleshooting
The agent doesn't respond to a mention
Check the app is still authorized at linear.app/settings/integrations. Note also that the mention has to come from Linear's own composer. A comment posted programmatically through the API does not raise the event that starts a mission, so automation should use the API or the CLI rather than writing a comment.
The agent responds but cannot find the issue
Confirm the issue is in the team you selected for the project. A project is scoped to one team.
Labels named in configuration never appear
SHIP attaches labels that already exist in your workspace and skips ones that do not. It never creates labels, statuses or teams, because changing your workspace's own schema is not something the platform will do on your behalf.
How is this page?