Observagent
Agent integration · macOS · Windows · Linux

Connect Grok Bot to Observagent.

Grok Bot is xAI's persistent AI-teammate product, with desktop and mobile apps in front of Bots that run on a cloud computer with a browser, filesystem, and terminal. Its Enterprise controls, including OpenTelemetry export, live in the Cursor dashboard.

Select OS Review data sent
Grok Botcursor.surface=grok_bot events
OTLP/HTTP protobufCursor collector endpoint
ObservagentLogs + metrics
How it works

Grok Bot rides Cursor's Enterprise OpenTelemetry export

Grok Bot ships as desktop apps (macOS, Windows, Linux) and mobile apps, but each Bot itself runs on a shared, persistent cloud computer, not on your device. See Required tier below for current subscriptions that include Grok Bot. Its Enterprise-tier admin controls, including audit logs, network policy, action recording, and OpenTelemetry export, are configured from the Grok Bot page of the Cursor dashboard.

There is no separate xAI-hosted telemetry endpoint for Grok Bot. When a Cursor Enterprise workspace enables OpenTelemetry Export, that stream already carries Grok Bot activity, tagged cursor.surface=grok_bot, alongside regular Cursor IDE usage. If you already completed the Cursor integration guide for the same workspace, also enable Action Recording to receive Grok Bot action events in that project.

  • Grok Bot access and export access are separate; Action Recording and OpenTelemetry Export require Enterprise.
  • Cursor pushes over OTLP/HTTP binary protobuf only; gRPC and JSON encodings are not supported.
  • Export is a team-level setting configured once by an admin, not a per-Bot or per-device toggle. Action Recording must also be enabled for Grok Bot action events and is off by default.
  • Unlike most other integrations in this documentation, this export can optionally include the raw text of user prompts and assistant responses; that is a separate opt-in, not the default.
Before you begin

Minimum required plan

Cursor Enterprise with Grok Bot access.

  • A team admin must enable both Action Recording and OpenTelemetry Export. Bot access on an individual or self-serve team subscription does not include these Enterprise controls.
  • Grok Bot itself is included on The X Subscription Premium, Super, and Ultra. Enterprise availability and controls must be enabled for your organization.
Observagent accessPrepare an Observagent project with monitoring and the required signals enabled, plus a valid project key with telemetry:write permission.

Requirements reviewed on .

Select OS

Integration steps

Select a platform to see commands and paths for your computer. Project setup and delivery verification are shared across platforms.

WindowsPowerShell
  1. Step 1

    Confirm Grok Bot and OpenTelemetry Export are both enabled

    Grok Bot access depends on the subscriptions listed above. Action Recording and OpenTelemetry Export are Enterprise only. In the Grok Bot dashboard, enable Action Recording for Bot action events, then confirm OpenTelemetry Export is available before continuing.

    • Grok Bot control-plane audit logs (Bot creation, access changes, routines) are a separate Enterprise feature that streams to a SIEM, not to this OTLP path.
    • Action Recording is off by default and is required for Grok Bot action events to flow through OpenTelemetry Export.
  2. Step 2

    Create a project and project key

    In Observagent, enable Logs and Metrics on a project, turn monitoring on, and generate a project key with telemetry:write permission.

    • Use a separate key for this connection so Observagent can attribute the stream reliably.
    • This export does not include traces; leave that project signal as-is for this connection.
  3. Step 3

    Point Cursor's OpenTelemetry export at Observagent

    This is the same Team Settings -> OpenTelemetry Export toggle used for regular Cursor IDE telemetry; there is no separate Grok Bot endpoint. Enter the collector endpoint, OTLP/HTTP binary protobuf protocol, and bearer header, and confirm the endpoint responds before saving.

    • A 200 or 204 response confirms the endpoint is reachable before you save the configuration in Cursor.
    • Cursor pushes OTLP/HTTP binary protobuf only; gRPC and JSON encodings are not supported.
    • OpenTelemetry Export can optionally include the text of user prompts and assistant responses; leave that off unless you specifically need it.
    PowerShell
    (Invoke-WebRequest https://dashboard.observagent.cloud/v1/metrics -Method Head).StatusCode
  4. Step 4

    Allowlist your endpoint and verify delivery

    Add Cursor's published egress IPs to your allowlist if needed, run a Grok Bot task to completion, then check Observagent for events tagged cursor.surface=grok_bot alongside your regular Cursor traffic.

    • Cursor egresses from a fixed set of source IPs published in its enterprise documentation.
    • Filter or search for cursor.surface=grok_bot to isolate Grok Bot activity from regular IDE usage in the same stream.
Troubleshooting

Diagnose export failures

  • Nothing arrives: confirm the workspace is on the Enterprise plan and that both Action Recording and OpenTelemetry Export are enabled, not just configured. Grok Bot access alone (Pro/Teams) does not include these controls.
  • Cursor IDE events arrive but no Grok Bot events: confirm a Bot actually completed a run; opening the desktop or mobile app alone does not generate activity.
  • Connection or timeout errors: the endpoint is not publicly reachable, or Cursor's published egress IPs are not allowlisted on your side.
  • 401/403 from Observagent: the bearer key is missing, malformed, revoked, or lacks telemetry:write.
  • Wrong content type rejected: Cursor sends OTLP/HTTP binary protobuf only. Confirm your collector path accepts protobuf, not JSON, on /v1/metrics and /v1/logs.
  • Traces never appear: this export path does not include traces; that is expected.
  • Need Bot-level audit detail: Bot creation, access changes, and routines are covered by Grok Bot's separate Enterprise Audit Logs, which stream to a SIEM, not this OTLP path.
Privacy

Review what the stream includes

By default, treat this export as operational metrics and logs, including requests, errors, and Bot lifecycle events, not a transcript feed. Cursor's OpenTelemetry Export has a separate opt-in that can additionally include the text of user prompts and assistant responses; leave it off unless you specifically need that content, and be aware that Bots read and write files and act across connected apps, so a full transcript can carry more than a chat message would. Field-level detail can change between Cursor and Grok Bot releases, so review Cursor's and xAI's current documentation before connecting a workspace with sensitive repositories or credentials. Observagent applies its own server-side content controls as an additional boundary.