Get started

Two minutes to your first diagnosis.

Start with the loop, not another dashboard. Create a scoped project, emit one real signal, and hand your coding agent bounded evidence it can act on.

Create a project →Read the quickstart

OTLP inMCP outApproval gate intactNo email wall

Fastest path · coding agent

Already working with Claude Code, Codex, or Cursor? Paste this one line into it — the agent provisions keys, wires your app, sends the first span, and hands you the console link. The steps below are the same runbook, by hand.

Read https://loopops.dev/onboard.md and follow it: connect this repo to LoopOps and send its first telemetry.

Fast sandbox

Click, send, inspect

Use the browser path below to mint keys and post one failing span without touching your app.

Production app

Install the emitter

After signup, copy the filled command for @getloopops/otel and send real traces from a Node agent.

Agent operator

Claim over MCP

Bind the sandbox to your account later so Claude Code, Codex, or Cursor can read bounded evidence.

Step 1 · Create your project

Name it. Get scoped keys.

This mints an isolated sandbox with a producer_key for telemetry writes and an agent_key for bounded reads and diagnosis. No account gate on the first signal.

Prefer the terminal (or you're an agent)?

$ curl -fsS https://loopops.dev/v1/signup -d '{"project_name":"my-app"}'

Same result as the form — the response carries the keys, a bookmarkable console link, and next steps. Agents: prefer the idempotent POST /v1/provision and execute the full runbook at GET /onboard.md; human flow in the quickstart.

Step 2 · Send your first trace

Emit evidence, not a demo metric.

A single failing tool-call span is enough for the first diagnosis. Use the button for a clean smoke test, or copy the filled SDK/OTLP command after project creation.

posts one failing span to your project

Terminal and SDK commands

Node agent

npm install @getloopops/otel
printf 'import { initLoopOps } from "@getloopops/otel";\ninitLoopOps();\n' > otel.js
LOOPOPS_URL=https://loopops.dev \
LOOPOPS_INGEST_KEY=<producer_key> \
node --import ./otel.js agent.js

Raw OTLP JSON

curl -sS -X POST /v1/traces …   (create a project first)

The SDK command reads the key from your environment and exports OTLP/JSON to this project. Workers or edge runtimes should use the raw POST path.

Step 3 · Watch the loop

Verify the signal landed.

Your signed console link is the audit surface for this sandbox: sessions, outcomes, candidate diagnosis, and the handoff to the agent loop. Bookmark it.

Open your console →bookmark it — it's your way back in

Run your first diagnosis from the terminal

curl -sS -X POST /v1/runs/diagnose …

Keep going

Keep this project

Sandbox projects are span-capped and expire. Sign in with your email (one-time PIN) and claim it with the project_id + recovery_code above — it then lives under your account.

Connect your coding agent

Let Claude Code, Codex, or Cursor read the loop natively over MCP, and install the loop skill:

claude mcp add --transport http loopops https://mcp.loopops.dev

curl -fsS https://loopops.dev/skill.md --create-dirs -o ~/.claude/skills/loopops/SKILL.md

All clients + the Codex plugin: see connect options.