> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-ade-im-seeing-error-messag-eright-58df792e.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Guide: CTO + Linear workflow
> Connect the CTO agent to Linear for automated issue triage, task delegation, and status syncing.
The CTO agent can sync with your Linear workspace to read incoming issues, triage them, delegate work to AI agents, and update issue statuses as work progresses. This guide walks you through connecting Linear and configuring the CTO for automated workflows.
***
## 1. Connect Linear
Navigate to **Settings > Linear** in ADE.
Click **Connect Linear** and authorize ADE with your Linear workspace. ADE requests read/write access to issues, projects, and labels.
Choose the Linear team whose issues the CTO should monitor. You can change this later or add multiple teams.
Once connected, ADE shows a sync status indicator in the Linear settings panel.
***
## 2. Configure the CTO Agent
Navigate to **CTO** in the sidebar to access the CTO agent's settings and chat interface.
In **CTO Settings**, select which AI model the CTO uses. A capable model (Claude Sonnet or Opus) is recommended for triage and planning tasks.
* **Sync interval** — how often the CTO checks for new issues (default: 5 minutes)
* **Issue filters** — which issue states, labels, or priorities to include
* **Auto-triage** — whether the CTO should automatically triage new issues or wait for your instruction
Control how aggressively the CTO delegates work:
* **Ask first** — the CTO proposes a plan and waits for your approval
* **Auto-delegate** — the CTO assigns work to agents without asking (within budget)
### Workflow targets
The CTO can route incoming Linear issues to different execution surfaces:
| Target | When to use |
| ------------------ | ----------------------------------------------------------- |
| `employee_session` | Simple tasks a single worker can handle in one session |
| `worker_run` | Tasks that need a dedicated lane, durable status, and audit |
| `pr_resolution` | PR review comments or failing checks that need fixing |
| `review_gate` | Work that should be reviewed by the CTO before proceeding |
The CTO chooses the target based on issue complexity, your delegation policy, and available budget.
***
## 3. Triage Incoming Issues
When new issues arrive in Linear, the CTO can triage them:
* **Read the issue** — the CTO reads the title, description, and any comments
* **Assess complexity** — estimates effort and identifies which parts of the codebase are involved
* **Propose a plan** — suggests whether the issue should be a worker run, PR fix, review gate, or deferred
* **Assign priority** — updates the Linear issue with a recommended priority if auto-triage is enabled
In Supervised mode, you review the CTO's triage in its chat interface before any work begins. In Auto-delegate mode, the CTO proceeds directly to delegation.
***
## 4. Delegate to Worker Agents
When the CTO decides to act on an issue, it:
The CTO spawns a new lane for the issue, named after the Linear issue ID (e.g., `linear/ENG-142`).
A worker agent is launched in the new lane with context from the issue, the project pack, and any relevant code references.
The CTO tracks the worker's progress and reports status back to the Linear issue. Comments are added to the issue as work progresses.
For larger issues, the CTO splits the work into dedicated lanes and worker runs.
***
## 5. Status Syncing
As work progresses, ADE keeps Linear updated:
| ADE event | Linear update |
| ------------------- | --------------------------------------------------- |
| Worker starts | Issue moves to **In Progress** |
| PR opened | Issue linked to the PR, comment added |
| Worker completed | Issue moves to **Done**, summary comment added |
| Worker failed | Issue flagged with a comment describing the failure |
| Intervention needed | Issue comment requesting human input |
### Custom status mapping
Configure status mappings in **Settings → Integrations → Linear**:
| ADE state | Default Linear status | Configurable |
| ------------------- | --------------------- | ------------ |
| Worker started | In Progress | Yes |
| PR opened | In Review | Yes |
| Worker completed | Done | Yes |
| Worker failed | Blocked | Yes |
| Intervention needed | Blocked | Yes |
You can also configure `activeStateTypes` (which Linear states trigger CTO attention) and `terminalStateTypes` (which states mean the issue is done) to match your team's Linear workflow.
***
## 6. Review and Close
When a worker completes:
* The CTO posts a summary comment on the Linear issue with links to the PR and any artifacts
* The issue status is updated based on the outcome
* You can review the work in ADE's History view or PR panel, then close the issue in Linear
***
## Tips
* Start with **Ask first** mode until you trust the CTO's triage judgment. Switch to **Auto-delegate** once routing behavior matches your workflow.
* Use Linear labels to control routing — for example, label issues `ai-eligible` and filter the CTO to only triage those.
* Keep architecture and convention docs current so the CTO can inspect the repo and make better triage decisions.
***
## Next Steps
Understand the CTO's role and org chart model.
Learn how CTO workers pick up delegated tasks and report progress.