> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/dino-ai/tools-and-features/linear-tool.md).

# Linear Tool

The Linear Tool allows DinoAI to access information from your Linear issues, bringing task requirements and issue details directly into your development workflow.

This tool connects development work to Linear, enabling DinoAI to understand requirements, resolve tickets, and implement features based on information stored in Linear.

{% hint style="info" icon="plug-circle-plus" %}
**Requires Linear integration.** Before using this tool, make sure you've connected your Linear account in Paradime. See [Connecting Linear](/app-help/integrations/linear.md) to Paradime for setup instructions.
{% endhint %}

#### Available tools

DinoAI exposes two Linear-specific tool calls. Both ask for permission before they run.

| Tool                   | What it does                                                                                                                                                                |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Fetch Linear issue** | Fetches the full details of a single Linear issue by ID (e.g. `ENG-456`) — title, description, state, assignee, team, labels, branch name, child issues, and comments.      |
| **List Linear issues** | Lists Linear issues with optional filters: **team**, **assignee email**, **workflow state**, **label**, and **priority**. Use this to discover, triage, or batch-plan work. |

#### Capabilities

| Capability                    | What it does                                                                           |
| ----------------------------- | -------------------------------------------------------------------------------------- |
| **Fetch a specific issue**    | Pull details from a Linear issue using its key or URL                                  |
| **Discover issues by filter** | Find issues by team, assignee, state, label or priority — without knowing the exact ID |
| **Extract Requirements**      | Understand task requirements and acceptance criteria                                   |
| **Fix Reported Issues**       | Help resolve bugs and errors documented in issues                                      |
| **Track Work Implementation** | Associate code changes with specific Linear issues                                     |

#### Using the Linear Tool

Depending on whether you already know the issue ID, DinoAI will pick one of the two tools:

**When you reference a specific issue**

1. Open DinoAI in the right panel of the Code IDE
2. Mention the Linear issue ID or URL in your prompt (e.g. `ENG-456` or a full Linear issue URL)
3. Grant permission when DinoAI asks to access the Linear issue — this runs **Fetch Linear issue**
4. Review and implement DinoAI's suggested actions

**When you want DinoAI to find issues for you**

1. Open DinoAI in the right panel of the Code IDE
2. Describe the issues you're after in natural language — e.g. "in-progress bugs assigned to me in the ENG team", "all P1 issues with the `data-quality` label", "issues in the `Triage` state for team DATA"
3. Grant permission when DinoAI asks to list issues — this runs **List Linear issues** with the filters DinoAI inferred from your prompt
4. From the returned list, DinoAI can then drill into a specific issue using **Fetch Linear issue**

{% hint style="info" %}
**Supported filters for List Linear issues** — team key (e.g. `ENG`), assignee email, workflow state name (e.g. `In Progress`), label name, and Linear priority (`0` = None, `1` = Urgent, `2` = High, `3` = Medium, `4` = Low). Up to 100 issues are returned per call.
{% endhint %}

#### Example Use Cases

**Implementing a Feature from an Issue**

**Prompt**

{% code overflow="wrap" %}

```
I need to implement the feature described in A-456. Can you help me get started?
```

{% endcode %}

**Result:** DinoAI calls **Fetch Linear issue** for `A-456`, extracts the requirements, suggests an implementation approach, and helps create the necessary models or code changes to satisfy them.

**Resolving a Production Issue**

**Prompt**

{% code overflow="wrap" %}

```
I have a production branch that failed this morning. Details are in Linear issue A-123. Can you help me resolve it?
```

{% endcode %}

**Result:** DinoAI fetches the issue details, analyses the error information, and walks you through creating a fix branch, updating the relevant files, and testing the solution.

**Triaging issues across the team**

**Prompt**

{% code overflow="wrap" %}

```
List all Urgent issues currently In Progress for team ENG, and tell me which ones look most likely to block this week's release.
```

{% endcode %}

**Result:** DinoAI calls **List Linear issues** with `team_key="ENG"`, `state_name="In Progress"`, `priority=1`, summarises the returned list, and highlights the issues most likely to block the release. From there, ask DinoAI to drill into a specific one to plan or implement the fix.

**Finding my open work**

**Prompt**

{% code overflow="wrap" %}

```
Show me all my open Linear issues with the "dbt" label, then pick the highest-priority one and start implementing.
```

{% endcode %}

**Result:** DinoAI lists issues filtered by `assignee_email` (you) and `label_name="dbt"`, picks the highest-priority one, fetches its full details, and starts the implementation plan.

#### Working with Other Tools

The Linear Tool works well alongside DinoAI's other capabilities to support your full development workflow:

* Combine with the **Terminal Tool** to create branches using Linear-based naming conventions (e.g., `feature/linear-123`) and reference issue IDs in commit messages
* Combine with the **Confluence Tool** to cross-reference issue requirements against linked specification pages
* Use alongside **Git Lite** to commit implementation work that traces back to a specific Linear issue

You'll need appropriate Linear permissions to access issues. DinoAI will request permission each time it needs to access Linear information.

#### Best Practices

* **Use exact issue references** — Include the precise Linear issue key or URL in your prompt to ensure DinoAI accesses the correct issue
* **Ensure issue quality** — DinoAI works best with well-documented Linear issues that include clear descriptions and acceptance criteria
* **Verify suggestions** — Always review DinoAI's interpretation of requirements before implementing, especially for complex or ambiguous issues
* **Combine with the Terminal Tool** — Let DinoAI help with the full workflow from implementation to testing, using the issue as the source of truth throughout


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/products/dino-ai/tools-and-features/linear-tool.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.