AutoMerge is generally available

Last updated:

Use the Dash0 Linear AgentRelease historyThis feature was introduced by Linear integration on March 6, 2026.

Mention @Dash0 in any Linear issue or comment and Agent0 investigates using your telemetry, posting results back into the thread with a deep link to the full session in Dash0.

The Dash0 Linear Agent brings AI-powered observability directly into your Linear workflow. Mention @Dash0 in any issue or comment and Agent0 investigates using your telemetry data, posting results back into the same thread with a deep link to the full session in Dash0.

Note

The Linear Agent must be configured before you can use @Dash0 mentions. See Set Up Linear Integration for configuration steps.

How to Trigger Agent0 from Linear

Mention @Dash0 anywhere in a Linear issue or comment to start an investigation:

  1. Type @Dash0 in any Linear issue description or comment
  2. Add your question or context (e.g., "Why is the checkout service slow?")
  3. Agent0 investigates by reading the issue context and querying your Dash0 telemetry data
  4. Results posted back as a comment in the same Linear thread

What Agent0 Reads

When you mention @Dash0, Agent0 automatically reads:

  • Issue title and description — understands what service, feature, or problem you're investigating
  • Issue metadata — service labels, priority, team ownership
  • Thread context — previous comments and discussion
  • Linked resources — related issues, projects, or external links in the issue

What Agent0 Posts Back

Each investigation response includes:

  • Investigation summary — what Agent0 found in your telemetry data
  • Relevant metrics and logs — key evidence from traces, metrics, and logs
  • Root cause analysis — likely causes based on the data
  • Deep link to full session — click to reopen the complete investigation in Dash0 with organization, dataset, and time range preserved

Example Use Cases

ScenarioYou type in LinearWhat Agent0 does
Service is slow"@Dash0 Why is checkout-service taking 5+ seconds?"Queries latency metrics, finds slow database queries, posts P99 latency charts
Error spike"@Dash0 We're seeing 500 errors on the API"Searches error logs, identifies failing endpoints, posts error rate trends
Incident investigation"@Dash0 What happened during the outage at 3pm?"Analyzes traces and logs from that time window, posts timeline of events
Feature impact"@Dash0 Did the new payment flow increase errors?"Compares error rates before/after deployment, posts comparison metrics

Response Format

Agent0 posts investigation results as Linear comments with the following structure:

🔍 Investigation Results

[Summary of what was found]

Key Findings:
- [Finding 1 with supporting data]
- [Finding 2 with supporting data]

[Charts, metrics, or log excerpts as needed]

🔗 View full investigation in Dash0: [deep link]

The deep link preserves:

  • Organization and dataset — correct data scope
  • Time range — relevant time window for the investigation
  • Service context — filters applied to the query

Access and Permissions

Agent0 reads issue context and posts investigation results using the connected Linear integration.

Note

The integration's OAuth grant includes write access beyond comments. Available tools depend on what is enabled for your organization. See OAuth Permissions before treating the connection as read-only.

Who Can Trigger Agent0

For a conversational @Dash0 request, your Linear email must match a Dash0 account that belongs to the Dash0 organization connected to the workspace. Agent0 authenticates as the person sending the prompt, or the session creator when there is no prompt sender.

If a mention matches an enabled Linear Mention trigger, that automation runs instead of the conversational agent. Matching and executing an automation is a separate path; the conversational email check does not determine whether it matches.

The Dash0 organization admin controls which Linear workspace is connected in Settings → Integrations.

Troubleshooting

@Dash0 Mention Not Responding

  • Check integration status — verify the Linear integration shows "Connected" in Settings → Integrations
  • Verify workspace — ensure you're mentioning @Dash0 in the correct Linear workspace
  • Check bot permissions — confirm the Dash0 bot has permission to read and comment on issues
  • OAuth token revoked — reconnect the integration if the OAuth token was revoked (e.g., app removed or permissions changed)
  • Check your identity: Your Linear email must match your Dash0 account, and that account must belong to the connected Dash0 organization for conversational requests.

Agent0 Posted "No Data Found"

  • Time range — Agent0 queries recent data by default; older incidents may require explicit time context
  • Service names — ensure service names in the Linear issue match those in Dash0 telemetry
  • Dataset access — verify the connected dataset contains the relevant service data
  • Multiple organizations — ensure you're signed into the correct Dash0 organization
  • Connection mismatch — verify the Linear workspace is connected to the intended Dash0 organization

Further Reading