Skip to main content
Link Linear issues to Niteshift tasks for automated progress updates, PR attachment, and status transitions on the issue.

​
Setup

1

Connect Linear

Open Settings → Integrations → Linear and click Connect. The OAuth flow links your Linear workspace to Niteshift.
2

Choose teams

Pick which Linear teams should have Niteshift available. Issues in other teams are ignored.
3

Set a default repository

Each user sets a default repository for Linear-triggered tasks under the same settings panel. Without it, assignment-triggered tasks fail with a prompt to configure one.

​
How to use

Two paths trigger a Niteshift task from Linear: Assign a Linear issue to Niteshift. Niteshift creates a task in your default repository. The issue title, description, recent comments, and up to 5 images are passed in the agent prompt. If the agent needs more context (sub-issues, parent issues, additional comments or images, related tickets, etc.), configure the Linear MCP server. Tag @Niteshift in a Linear comment. Use this when you want to add a specific instruction beyond what’s already in the ticket. The comment body becomes the prompt; the rest of the issue context loads the same way as an assignment.
Follow-up prompts in Linear work until a prompt arrives from another source (web UI, GitHub) — after that, send follow-ups from the web UI.

​
What you receive

When a task is linked to an issue, Niteshift:
  • Moves the issue to In Progress when the task starts
  • Moves it to In Review when the task completes
  • Posts agent thoughts, summaries, and PR links as Linear comments
  • Attaches the pull request to the issue
Image attachments in the issue description and recent comments (anything hosted at uploads.linear.app) are downloaded into the task so the agent can see them.
This is the issue-tracker integration. Separately, the Linear MCP server lets agents read and write Linear data directly during a task, useful for “go check related tickets” or “update the parent issue when done” workflows.