linear-connector

You can search Linear issues and retrieve project, team, comment, and attachment details by routing read requests through a policy gate that allows reads by default before executing any GraphQL call.

Create and update Linear issues by passing plain markdown strings for descriptions and comments without ADF conversion, routing write actions through a policy gate that escalates write operations by default for safety.

Yes, you can link externally hosted file attachment URLs to Linear issues using the write workflow, which applies policy enforcement to escalate the action before updating the issue.

Policy enforcement for Linear updates allows read actions by default, escalates write and delete actions like archiving issues or updating fields, and hard-denies privilege actions before any network call is made.

Limitations include the hard denial of privilege actions and the enforcement of policy escalation for all write and delete operations, meaning you cannot bypass the policy gate to add, update, or delete comments.

You must invoke the linear-connector binary with a specified action and JSON parameters, ensuring your environment supports executing this binary to enforce policy gates before making Linear GraphQL calls.