Linear
for LuumenAI

Fast follow-ups filed with the run linked.

Keep Linear in sync with operational work. LuumenAI finds related issues, files follow-ups with the run linked, and updates status — every write previewed and approved first.

The Linear toolbox

47 tools: 22 read, 25 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadDownload issue filesDownloads a Linear Attachment record or a private upload embedded in issue/comment Markdown; `file_name` must include the correct extension.
  • ReadGet a commentRetrieves a single Linear comment by its unique ID.
  • ReadGet current userGets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may be a bot or service account rather than a human user.
  • ReadGet cycles by team IDRetrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints).
  • ReadGet create issue default paramsFetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.
  • ReadGet Linear issueRetrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use…
  • ReadGet Linear projectRetrieves a single Linear project by its unique identifier.
  • ReadGet Project UpdateRetrieves a specific project update by its unique identifier.
  • ReadList commentsLists comments from Linear workspace accessible to the authenticated user.
  • ReadList issue draftsList issue drafts.
  • ReadList issues by team IDList all issues for a specific Linear team, scoped by team ID.
  • ReadGet all cyclesRetrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied.
  • ReadList Linear issuesLists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned.
  • ReadGet labelsRetrieves labels from Linear.
  • ReadList linear projectsRetrieves all projects from the Linear account.
  • ReadList Linear statesRetrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow.
  • ReadGet teamsRetrieves all teams with their members and projects.
  • ReadList Linear usersLists all workspace users (not team-scoped) with their IDs, names, emails, and active status.
  • ReadList project updatesRetrieves all project updates from the Linear workspace.
  • ReadSearch Linear issuesSearch Linear issues using full-text search across identifier, title, and description.
  • ReadValidate credentialValidates the Linear API credentials by checking if the authentication token can successfully query the current user.
  • ReadWho Am IReturn the identity (name, email) of the connected Linear account.
  • WriteArchive issueArchives an existing Linear issue by its ID, removing it from active views while preserving its data for future reference. Approval by default
  • WriteArchive ProjectArchives an existing Linear project by its UUID, removing it from active views. Approval by default
  • WriteArchive Project UpdateArchives a project update in Linear, hiding it from the default view while preserving its data. Approval by default
  • WriteCreate attachmentCreates a new attachment and associates it with a specific, existing Linear issue. Approval by default
  • WriteAdd reaction to commentAdd a reaction to an existing Linear comment. Approval by default
  • WriteCreate a commentCreates a new comment on a specified Linear issue. Approval by default
  • WriteCreate linear issueCreates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date. Approval by default
  • WriteCreate issue relationCreate a relationship between two Linear issues using the issueRelationCreate mutation. Approval by default
  • WriteCreate a labelCreates a new label in Linear for a specified team, used to categorize and organize issues. Approval by default
  • WriteCreate ProjectCreates a new Linear project with specified name and team associations. Approval by default
  • WriteCreate Project MilestoneCreate a project milestone in Linear with a name and optional target date and sort order. Approval by default
  • WriteCreate Project UpdateCreate a project status update post for a Linear project. Approval by default
  • WriteCreate TeamCreates a new team in Linear with the specified name and key. Approval by default
  • WriteDelete issueArchives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent. Approval by default
  • WriteRemove label from Linear issueRemoves a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue. Approval by default
  • WriteRemove reaction from commentRemove a reaction on a comment. Approval by default
  • WriteResolve commentMarks a Linear comment as resolved. Approval by default
  • WriteRun Query or MutationExecute any GraphQL query or mutation against Linear's API. Approval by default
  • WriteUnarchive Project UpdateUnarchive a previously archived project update in Linear. Approval by default
  • WriteUnresolve a commentUnresolves a previously resolved Linear comment, marking it as requiring attention again. Approval by default
  • WriteUpdate issueUpdates an existing Linear issue using its `issue_id`; requires at least one other attribute for modification, and all provided entity IDs (for state, assignee, labels, etc.) must be valid UUIDs —… Approval by default
  • WriteUpdate a commentUpdate an existing Linear comment's body text. Approval by default
  • WriteUpdate ProjectUpdate an existing Linear project. Approval by default
  • WriteUpdate Project UpdateUpdate an existing Linear project update post. Approval by default
  • WriteUpdate TeamUpdates an existing Linear team's settings and configuration. Approval by default

One prompt, start to finish

What a governed Linear run looks like inside Luumen.

Questions

How does LuumenAI connect to Linear?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Linear on its own?

Read actions answer immediately. Anything that writes — archive issue, archive project, archive project update, create attachment, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Linear — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Linear to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.