> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Linear > Read Linear teams, projects, cycles, issues and comments in Hebno, and create issues, update them and comment after you confirm. The Linear integration makes delivery status available in your client work. Ask what is still open in the current cycle, which issues in a client project are blocked, or what the team said on an issue since Monday, and Hebno answers from Linear with each issue cited. When a request implies a change, such as raising an issue or moving one to **Done**, Hebno shows a confirmation card and writes to Linear only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Linear account. | | **Default access** | Read and write | | **Attach** | Projects, cycles, issues | | **Search** | Hebno searches Linear when a request mentions an issue identifier, team, project, cycle, assignee, label, status or comment | | **Link** | A project links to one or more Linear projects | | **Write** | Create an issue, update an issue, add a comment. Every write needs a person to confirm. | ## Before you start You need: * A Linear account in the workspace you want to use. * An allowed integration. An owner or admin sets **Linear** to **Allow** under **Admin → Connectors → Catalogue**. * Approval from a Linear workspace admin if your workspace requires admin approval before members authorise applications. Hebno requests these OAuth scopes: | Scope | Why Hebno needs it | | - | - | | `read` | Read teams, projects, cycles, issues, comments, labels, workflow states and users | | `issues:create` | Create issues after you confirm | | `comments:create` | Add comments to issues after you confirm | | `write` | Update issue fields such as status, assignee, priority, estimate, cycle and labels after you confirm | Hebno does not request the `admin` scope, so it cannot change workspace, team or integration settings. ## Connect Linear **1. Start the connection** Open **Settings → Connections**, find **Linear** and select **Connect**. You can also select **Connect** from the prompt in a chat. **2. Sign in to Linear** Sign in, choose the workspace if you belong to more than one, check the access Hebno requests, and select **Authorize**. **3. Return to Hebno** The card shows **Connected** with your workspace name. Hebno reads and writes with your own permissions, so you see only the teams you can open in Linear, including private teams you are a member of. Tokens are encrypted at rest. Select **Disconnect** at any time, or ask an admin to revoke the connection under **Admin → Connectors → Connections**. ## What Hebno reads | Linear object | Fields Hebno uses | Typical questions | | - | - | - | | **Team** | Name, key, members, workflow states, cycle settings | "Which teams work on Contoso?" | | **Project** | Name, lead, status, health, start and target dates, milestones, project updates | "How is the Contoso pricing review project tracking?" | | **Cycle** | Number, name, start and end dates, scope, completed issues | "What is left in this cycle?" | | **Issue** | Identifier, title, description, status, assignee, priority, estimate, labels, cycle, project, parent issue, due date | "What is blocked on the Contoso pricing review?" | | **Comment** | Author, date, body, thread | "What did Priya say on CPR-42?" | Hebno queries Linear through its GraphQL API and filters by team, project, cycle, status and assignee for you, so you can ask in plain words rather than build a filter. Reads are live. Hebno queries Linear when a request needs it. Only what a reply used is stored with the conversation as its sources. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including issue descriptions and comments from Linear. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Linear object | Fields on the card | | - | - | - | | **Create an issue** | Issue | Team, title, description, status, assignee, priority, estimate, labels, project, cycle, parent issue, due date | | **Update an issue** | Issue | Status, assignee, priority, estimate, labels, project, cycle, due date | | **Add a comment** | Comment | Issue, comment text | ![Confirmation card for Linear with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-linear.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=b722512521bec81cec01045c0f89c2ba) A Linear change pending confirmation. Nothing is written until you confirm. Hebno never deletes or archives issues, projects or cycles, changes team membership or workflow states, or edits workspace settings. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Linear You->>Hebno: Raise an issue to rerun the price elasticity model Hebno->>Linear: Find the Contoso pricing review project and its team Linear-->>Hebno: Team Analytics, project Contoso pricing review, cycle 14 Hebno-->>You: Confirmation card with team, title, assignee, priority, cycle You->>Hebno: Confirm Hebno->>Linear: Create the issue as you Linear-->>Hebno: Issue ANA-218 created Hebno-->>You: Done, with a link to the issue ``` Writes are made as your Linear user, so Linear shows you as the creator or author. ## Link a project to a Linear project Linking marks which Linear projects belong to an engagement, so you can ask "what is blocked?" without naming the project. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Linear**. 3. Search by project name and select it. Repeat for each Linear project in the engagement. In chats tagged to the project, Hebno starts with the linked Linear projects for any delivery question, and cards for new issues default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Linear in chat * **Attach**: open the **+** menu, choose **Sources → Linear**, and pick a project, a cycle or an issue. Or type `/` and choose **Linear**. * **Ask**: name the issue identifier, project, cycle or person in your request. For example: > List every open issue in the Contoso pricing review project with priority Urgent or High, grouped by assignee. > Summarise what the Analytics team completed in the last cycle and what rolled over. > Move ANA-218 to In Review, assign it to Sarah Chen and add a comment that the rerun used the November store data. * **Research runs** show a **Checking Linear** step, with a chip for each project, cycle and issue it read. * **Agents** can read Linear on a schedule, for example a Friday summary of the cycle with issues at risk of rolling over. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | Linear shows that the application needs admin approval | Ask a Linear workspace admin to approve Hebno, then select **Connect** again. | | Hebno cannot find a team or issue you expect | The team is private and you are not a member, or you connected a different workspace. Hebno reads only what you can read. | | An update fails with an invalid status | Each team has its own workflow states. Choose a status from the issue's team on the card and select **Confirm** again. | | A write fails with a Linear message | Fix the field the message names on the card, for example a label from another team, and select **Confirm** again. | | **Reconnect Linear** appears | The authorisation was revoked or the token expired. Select **Connect** to authorise again. | | Requests fail with a **RATELIMITED** error | Linear limits requests and query complexity each hour. Wait and retry, or narrow the request to one team or project. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Jira](https://hebno.com/docs/integrations/jira.md) * [GitHub](https://hebno.com/docs/integrations/github.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.