Observagent
Editor integration · Windows · macOS · Linux

Connect Cursor to Observagent.

Use Cursor's Enterprise OpenTelemetry export to stream team-wide usage metrics and logs directly to Observagent.

Select OS Review data sent
CursorTeam usage events
OTLP/HTTP protobufCollector endpoint
ObservagentLogs + metrics
How it works

Use Cursor's Enterprise OpenTelemetry export

Cursor for Enterprise can push team-wide usage data to one collector you run, rather than only the built-in dashboard. Observagent accepts this stream directly, so no local proxy is required.

  • Metrics include tokens, tool calls, and best-effort cost, aggregated for the team.
  • Logs include API requests, errors, corrections, skills, hooks, plugins, and cloud agent lifecycle events.
  • 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-developer toggle.
Before you begin

Minimum required plan

Cursor Enterprise.

  • A workspace admin must configure and enable OpenTelemetry Export in Team Settings. Individual plans and self-serve team plans do not provide this Enterprise export feature.
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 your plan and admin access

    OpenTelemetry Export is available on the Cursor Enterprise plan and is configured under Team Settings by a workspace admin.

    • If your workspace is on a lower plan, use the dashboard CSV export or the Admin/Analytics API instead of this OpenTelemetry path.
  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

    Configure OpenTelemetry export in Cursor

    In Cursor, open Team Settings -> OpenTelemetry Export and enter the collector endpoint, OTLP/HTTP binary protobuf protocol, and bearer header. 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.
    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 the collector sits behind a firewall, generate normal team activity, then check Logs and Metrics for the project in Observagent.

    • Cursor egresses from a fixed set of source IPs published in its enterprise documentation.
    • Check Logs and Metrics independently; one signal arriving does not prove the other did.
Troubleshooting

Diagnose export failures

  • Nothing arrives: confirm the workspace is on the Enterprise plan and that OpenTelemetry Export is enabled, not just configured.
  • 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 per-developer detail: combine this stream with the dashboard CSV export or the Admin/Analytics API, which can cover data this stream does not.
Privacy

Review what the stream includes

The documented export covers usage metrics and operational logs such as requests, errors, corrections, and lifecycle events, not a general-purpose transcript feed. Field-level detail can change between Cursor releases, so review Cursor's current enterprise OpenTelemetry documentation before connecting a workspace with sensitive repositories. Observagent applies its own server-side content controls as an additional boundary.