Documentation Index
Fetch the complete documentation index at: https://docs.codeant.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Once your Linear workspace is connected to CodeAnt AI, you can file Linear issues straight from any finding the platform surfaces — security vulnerabilities, code‑quality insights, anti‑patterns, or pentest findings. The ticket lands in the team and project you configured during setup, gets the CodeAnt label automatically, and is prioritized based on the finding’s severity.Prerequisite Complete the Setup guide first so CodeAnt AI is authorized against your Linear workspace and a default team is selected.
When Can I Create a Linear Issue?
CodeAnt AI surfaces a Create Linear Issue action anywhere it detects something worth tracking, including:| Category | Examples |
|---|---|
| Security issues | Hard‑coded secrets · vulnerable dependencies · misconfigured IAM roles |
| Application security | SQL injection · XXE · SSRF |
| Code health | Long/complex functions · missing docstrings · duplicate code |
| Anti‑patterns | God objects · large switch statements · tight coupling |
| Pentest findings | Still‑open findings on the Pentesting dashboard |
Step‑by‑Step: Creating an Issue
- Open the finding details panel. From the dashboard, click any flagged item to bring up its detailed context (file location, severity, remediation guidance, etc.).
- Click Create Linear Issue. The action sits next to the other ticketing actions (Jira, Azure DevOps) on the finding details panel. CodeAnt AI files the issue against your configured team and project, attaches the CodeAnt label, and maps the severity to a Linear priority.
- Open it in Linear. Once the ticket is created, the button turns into View in Linear — click it to jump straight to the new issue in your workspace. The button stays in the created state on subsequent visits, so you won’t accidentally file duplicates for the same finding.
What’s in the Ticket?
Each Linear issue created by CodeAnt AI includes:- Title — the rule name or vulnerability summary, prefixed with the file/line for code findings.
- Description — a markdown body with the finding details, severity, affected file/line, code snippet, and remediation guidance. Linear renders the markdown natively, so links, code blocks, and headings show up cleanly.
- Priority — mapped from the CodeAnt severity (
Critical → Urgent,High → High,Medium → Medium,Low → Low). - Label — the workspace‑level CodeAnt label, so your team can filter every CodeAnt‑filed ticket in one view.
- Team / Project — whatever you configured on the Linear Integration settings page.
Tips
Filter all CodeAnt issues in Linear
Filter all CodeAnt issues in Linear
Use the CodeAnt label as a saved view filter in Linear. You’ll get a single feed of every ticket CodeAnt AI has filed, across all teams and projects.
Re‑route to a different team
Re‑route to a different team
Tickets always land in the team selected on the Linear Integration page. To send a batch of findings to a different team, change the team selection, file the tickets, then switch back. Tickets already filed are not moved.
What happens if my Linear access expires?
What happens if my Linear access expires?
CodeAnt AI refreshes Linear access tokens automatically before they expire. If a refresh fails (for example, because the OAuth grant was revoked from Linear’s side), you’ll see an error toast when creating a ticket and can reconnect from Settings > Integrations > Linear.