> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Linear

> Connect Linear to Tess to manage issues, projects, and team workflows from chat and agents.

The **Linear** connector integrates Tess with Linear issue tracking and project planning. Once connected, the AI can create and update issues, check project status, and support engineering routines inside chats and agents.

Linear is part of the Tess [Connectors](/en/connectors) ecosystem and uses **OAuth** authentication for Apps connectors.

## Prerequisites

<Info>
  * A Linear account with access to the workspace you want to use.
  * Permission to authorize third-party apps in that Linear workspace.
</Info>

## How to connect

<Tip>
  On some Apps connectors, the OAuth consent screen may show a third-party connection bridge name rather than Tess. That is normal—review the requested permissions and continue if they match what you expect.
</Tip>

<Steps>
  <Step title="Open the Connectors panel">
    In chat, click the **+** next to the message box and select **Connectors**.
    You can also manage connectors while editing an agent in Agent Studio.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/linear/01-connect-panel.png" alt="PRINT: (Connectors panel with Linear highlighted and the Connect button visible)" />
    </Frame>
  </Step>

  <Step title="Find Linear and click Connect">
    Under **Apps**, locate **Linear** and click **Connect** to start authentication.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/linear/02-oauth-consent.png" alt="PRINT: (Provider authorization / consent screen for Linear)" />
    </Frame>
  </Step>

  <Step title="Authorize access">
    Sign in with the account you want to use and review the requested permissions before confirming.
  </Step>

  <Step title="Confirm it is active">
    Back in Tess, **Linear** should appear under **Connected**, ready for chats and agents.

    <Frame>
      <img src="https://mintlify.s3.us-west-1.amazonaws.com/tess-dfe1edf0/images/connectors/linear/03-connected.png" alt="PRINT: (Tess callback or Connectors list showing Linear as Connected with a success state)" />
    </Frame>
  </Step>
</Steps>

## What you can do

* **Create and update issues** with title, description, priority, and assignees
* **Search and list issues** by team, project, status, or labels
* **Track projects and cycles** to summarize progress and blockers
* **Comment on issues** without leaving Tess
* **Organize work** for engineering, product, and support routines

## Example prompts

> 1. List open issues assigned to me in the ENG team and group them by priority.
> 2. Create a bug in Linear titled 'Login timeout on Safari' and assign it to me.
> 3. Summarize what changed this week in the Connectors project and highlight blockers.
> 4. Find issues labeled 'customer' that are still In Progress and suggest next steps.

## Best practices

* Name the team/project when you have more than one context.
* Ask for a draft issue first when the request is ambiguous.
* In agents, define whether Linear is for intake, triage, or status reporting.

## Troubleshooting

<AccordionGroup>
  <Accordion icon="circle-question" title="Authorization fails or is denied">
    Confirm you are in the correct Linear workspace and that third-party apps are allowed.
  </Accordion>

  <Accordion icon="circle-question" title="401 / connection dropped">
    Reconnect Linear in Connectors. Tokens can expire after password or permission changes.
  </Accordion>

  <Accordion icon="circle-question" title="Cannot see a team or project">
    The connected account may lack access. Connect with an account that can view that team.
  </Accordion>
</AccordionGroup>

<Note>
  Tess uses the permissions of the connected account. It does not expand access beyond what that account can already do.

  Connectors involve access to external systems. Only connect accounts that fit the usage context, and review permissions carefully.
</Note>