AutoMerge is generally available

Last updated:

Agent0 Doesn't Call Expected Tools

Why Agent0 skips or can't access certain tools and how to fix it.

When Agent0 doesn't call the tools you expect, the issue is usually with tool access permissions, prompt clarity, or integration setup.

Agent0 Doesn't Post to Slack

Symptom: Automation runs but doesn't post to Slack channels.

Common causes:

Slack Tool Not Allowed (Most Common)

Check:

  • Open Tools & Skills → Configure tools.
  • Select slackSendMessage and check whether Allowed is on.

Fix for default policy:

  • Default policy only allows Slack posting when trigger is from Slack
  • For schedule or check triggers, explicitly turn Allowed on for slackSendMessage.

Fix for custom allowed tools:

  • Turn Allowed on for each Slack tool the automation needs.
  • If every run must send a message, also turn Required on for slackSendMessage. Required tools are force-included even if an API-configured allowlist would otherwise exclude them, but still need integration access and valid parameters.

Note: Slack connector tools work under any Network Access setting (No Network or Full Network). They do not require Full Network access.

Prompt Doesn't Say Where to Post

Check your prompt:

  • Does it say "Post to #incidents" or similar?
  • Or does it just say "analyze the data"?

Fix:

Query error rate for service {{label.service}}.

Post your findings to #incidents with recommended actions.

Be explicit about the output destination.

Slack Integration Not Connected

Check:

Fix:

  • Connect the Slack integration
  • Follow the OAuth flow
  • Verify bot has access to target channels

Agent0 Doesn't Query Metrics

Symptom: Agent0 responds from knowledge without querying actual data.

Common causes:

Prompt Too Vague

Problem:

Tell me about service health.

Fix:

Query the error rate and p99 latency for service {{label.service}} over the last hour. Show the actual numbers from Dash0.

Query Tool Not Required

Agent0 might skip queries if not explicitly required.

Fix:

  • Open Tools & Skills → Configure tools.
  • Select getMetricQuery or the relevant query tool and turn Allowed and Required on.
  • Agent0 will retry if it skips the query

Default Tool Policy Blocking Queries

This is rare (Dash0 query tools are almost always allowed), but check:

Fix:

  • Open Tools & Skills → Configure tools.
  • Find the query tool and turn Allowed on. Query tools are allowed by default unless you restrict them.

Agent0 Skips GitHub/Linear Actions

Symptom: Doesn't comment on PRs or create Linear tickets.

Check the available tools and access:

  • GitHub connector: Provides only githubListRepos tool
  • Linear connector: Issue and comment writes are available only when enabled for your organization
  • PR comments: Use gh CLI via bash with Trusted hosts only or Full Network and repository write access, not a connector tool
  • Linear tickets: When available, linearSaveIssue creates or updates issues and linearSaveComment adds or updates comments. These tools still need integration access and permission under the automation's guardrails.

To Comment on GitHub PRs

Requirements:

  1. Set Network Access to Trusted hosts only or Full Network in guardrails and grant the GitHub integration write access to the repository
  2. Use gh CLI commands via bash tool, not GitHub connector tools
  3. Ensure prompt explicitly instructs to use bash commands

Example prompt:

Analyze the PR for potential issues.

If you find concerns, use bash to run:
gh pr comment <pr-number> --body "Your analysis here"

GitHub Connector Tools

What it provides:

  • githubListRepos tool to list accessible repositories
  • No connector write tools. Sandbox CLI access is separate and does not require a GitHub trigger.

Check:

  • Go to Settings > Integrations
  • Is GitHub connected?

Fix:

  • Connect the integration for read access
  • For write operations such as PR comments, use gh CLI with Trusted hosts only or Full Network and repository write access

Linear Integration

What it provides:

  • Read access to Linear issues
  • Issue and comment write tools when enabled for your organization

Check:

  • Verify that the write tool is available in Tools & Skills → Configure tools
  • Allow or require the tool explicitly for non-Linear triggers
  • Check integration access and any tool errors in the run history
  • If write tools are unavailable, post findings to Slack instead

Tool Denied in Manage Tools Dialog

If you previously denied a tool, it won't be accessible through a namespace allow rule. Required tools are an exception: remove the requirement as well if you want to block a tool.

Check:

  1. Open Tools & Skills.
  2. Click Configure tools.
  3. Search for and select the tool.
  4. Check whether Allowed is off.

Fix:

  • Turn Allowed on to restore access.
  • Close the dialog and save the automation.

Debugging Tool Access Issues

Systematic approach:

1. Check Run History

  • Open the run that didn't call the tool
  • Look at which tools were actually called
  • Check for tool call errors or failures

2. Verify Tool Is Available

Test if tool is accessible:

  • Create a minimal test automation
  • Simple prompt: "Call [tool name] to check if it works"
  • If this fails, the issue is permissions/integration
  • If this works, the issue is in your complex prompt

3. Review Guardrails

Checklist:

  • ✓ Network access appropriate for the tool
  • ✓ Allowed is on in Tools & Skills → Configure tools
  • ✓ Required is on if every run must call the tool
  • ✓ Integration connected (for Slack/GitHub/Linear)

4. Make Prompt More Explicit

Before:

Check the service.

After:

1. Query error rate for service {{label.service}} using getMetricQuery
2. Post your findings to #incidents using slackSendMessage

Both steps are required.

Common Scenarios

Schedule Wants to Post to Slack

Problem: Default policy blocks Slack posting from schedule triggers.

Fix:

  • Open Tools & Skills → Configure tools, select slackSendMessage, and turn Allowed on.
  • Turn Required on too if every run must post a message.

Slack Message Wants to Query and Post

Default behavior: Works automatically (default policy allows both).

If it doesn't work:

  • Ensure prompt explicitly says to query and post
  • Check Slack integration is connected

Failed Check Wants to Comment on GitHub

Problem: GitHub connector is read-only; PR comments require gh CLI.

Fix:

  • Set Network Access to Trusted hosts only or Full Network and verify repository write access
  • Use bash tool with gh CLI commands
  • Make prompt explicit: "Use bash to run gh pr comment..."

Further Reading