Skip to main content

Documentation Index

Fetch the complete documentation index at: https://ade-app.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

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

1

Open settings

Navigate to Settings > Linear in ADE.
2

Authenticate

Click Connect Linear and authorize ADE with your Linear workspace. ADE requests read/write access to issues, projects, and labels.
3

Select a team

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.
1

Set the CTO model

In CTO Settings, select which AI model the CTO uses. A capable model (Claude Sonnet or Opus) is recommended for triage and planning tasks.
2

Configure Linear sync behavior

  • 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
3

Set worker spawning policy

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:
TargetWhen to use
employee_sessionSimple tasks a single worker can handle in one session
worker_runTasks that need a dedicated lane but not full mission structure
missionComplex multi-step work requiring planning, validation, and audit
pr_resolutionPR review comments or failing checks that need fixing
review_gateWork 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 mission, a single-lane task, 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:
1

Creates a lane

The CTO spawns a new lane for the issue, named after the Linear issue ID (e.g., linear/ENG-142).
2

Spawns a worker

A worker agent is launched in the new lane with context from the issue, the project pack, and any relevant code references.
3

Monitors progress

The CTO tracks the worker’s progress and reports status back to the Linear issue. Comments are added to the issue as work progresses.
If the issue is complex enough to warrant a mission, the CTO creates one instead of a single worker session.

​
5. Status Syncing

As work progresses, ADE keeps Linear updated:
ADE eventLinear update
Worker startsIssue moves to In Progress
PR openedIssue linked to the PR, comment added
Mission completedIssue moves to Done, summary comment added
Worker failedIssue flagged with a comment describing the failure
Intervention neededIssue comment requesting human input

​
Custom status mapping

Configure status mappings in Settings → Integrations → Linear:
ADE stateDefault Linear statusConfigurable
Worker startedIn ProgressYes
PR openedIn ReviewYes
Mission completedDoneYes
Worker failedBlockedYes
Intervention neededBlockedYes
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 or mission 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 Mission or History views, 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 the CTO has enough project memory to make good decisions.
  • Use Linear labels to control routing — for example, label issues ai-eligible and filter the CTO to only triage those.
  • The CTO’s project memory improves over time. Brief it on your architecture and conventions early; it will produce better triage and delegation as it learns.

​
Next Steps

CTO Concepts

Understand the CTO’s role, memory system, and org chart model.

Your First Mission

Learn how missions work — the execution unit the CTO uses for complex issues.