Dash0 acquires Polar Signals

Last updated: August 18, 2026

AI

Configure how Agent0 responds, including verbosity level, automatic context inference, approval for write actions, and whether Agent0 can be invoked over the Dash0 MCP Server.

Configure how Agent0 responds in your Dash0 organization. Access these settings at Settings → Agent0.

Agent0 Settings

Verbosity

Controls how detailed Agent0's responses are. Choose from:

  • Compact: Brief, concise responses
  • Default: Balanced level of detail (recommended)

The current verbosity setting affects how much explanation and context Agent0 provides when analyzing your telemetry data and investigating issues.

Verbosity dropdown showing Compact and Default options

Infer Context

When enabled, Agent0 automatically infers context from the specific page you're looking at when opening the Agent0 search, and passes it to Agent0 to provide you with contextualized results. (Recommended)

This setting allows Agent0 to automatically gather relevant traces, metrics, and logs based on your current view, making its analysis more accurate and relevant to your investigation.

Infer context toggle with help text explaining automatic context inference

Write Action Approval

Controls whether Agent0 asks for your approval in Chat before it runs an action that creates, changes, or deletes something.

  • Off (default): Agent0 runs write actions as part of answering your request.
  • On: Agent0 stops at each write action, shows what it wants to do, and waits for someone to approve or deny it in the conversation.

The setting is admin-only, and it is disabled while Agent0 itself is off. GitHub actions are not covered by it.

Write action approval toggle with help text explaining when Agent0 asks for approval

For the approval card and what approving or denying does, see Approve Write Actions.

Agent0 via MCP

Controls whether Agent0 can be invoked through the Dash0 MCP Server, so an AI assistant such as Claude Code or Cursor can hand it a whole investigation instead of querying telemetry itself.

  • On (default): assistants connected to the Dash0 MCP Server can delegate to Agent0. Each delegation consumes Agent0 credits.
  • Off: the delegation tools (runTask, waitForTask, and the thread inspection tools) are removed from the MCP Server for everyone in the organization. The read-only telemetry tools stay available and remain free.

This is the organization-wide way to guarantee that MCP usage does not consume Agent0 credits, and it applies no matter which client each person connects with. The setting is admin-only, and it is disabled while Agent0 itself is off.

For what delegation does, what it costs, and how an individual can disable it in just their own client, see Delegate to Agent0 via MCP.

Note

This setting is about the Dash0 MCP Server, which exposes Dash0 to your AI assistant. It is unrelated to Settings → Integrations → MCP, which connects external MCP servers into Agent0 as connectors.

Further Reading