Issue status and the lifecycle rail now agree. The handoff action is Copy agent prompt and copies a short loopops_issue pointer, not a duplicated brief or a raw MCP client name.
Dated, in plain words, only things you can see or rely on. Agents read the raw twin at /changelog.md.
Issue status and the lifecycle rail now agree. The handoff action is Copy agent prompt and copies a short loopops_issue pointer, not a duplicated brief or a raw MCP client name.
Real documentation at /docs: a sectioned sidebar (Start · Instrument · Run the loop · Data & trust · Reference), and every page doubles as raw markdown for agents — append .md to any docs page URL.
Default-on data scrubbing (Sentry's model): sensitive field names filter to [Filtered]; credential patterns and Luhn-valid card numbers mask inside every string value and message, on both OTLP lanes and feedback. Per-project rules via /v1/redaction or the loopops_redaction tool. Details →
The same navigation on every public page — Docs · Pricing · Blog · Dashboard — with the theme toggle moved to the footer.
The console overview now derives the product picture from telemetry wiring — observed services, trace relationships, and explicitly virtual dependencies. Agents read the same map with loopops_map; six product surfaces remain health coverage and a fix category, not a hardcoded topology.
Every diagnosed issue has a schema-backed handoff packet — identity, diagnosis, cited evidence, repository, loop history, success criteria, approval constraints. Copy it as a complete agent prompt from the console, or read it fresh with loopops_issue. Details →
GET /v1/ingest/health and the console's first-event panel now say WHY a project looks empty: the last accepted batch, or the last rejected request with its exact reason. No more silent zero.
OTel's canonical recordException path now normalizes on both OTLP lanes — errored spans cluster on the real exception message instead of the span name, with type and stacktrace preserved.
A request-rate ceiling per project bounds a runaway or leaked key without touching legitimate batched producers. Throttled producers see why on the ingest-health surface.
/proof now shows real aggregate numbers from LoopOps' own improvement loop — the loop, run on the tool that runs it. Counts only; not a mockup.
The local stdio server is retired; https://mcp.loopops.dev tracks the current MCP specification release. Headless and CI setups drive the same operations over the plain /v1 HTTP API with project keys.
Link a GitHub repository to a project — from the console or loopops_link_repository — and issue handoffs carry the repo, so a picked-up agent starts in the right codebase.
Overview rebuilt around the four questions a human actually asks: Am I OK? What needs me? What is the product? What did the agents do? Analytics stay one click away behind a single disclosure.
The Connections view shows which coding agents drove which improvement runs — verified work, shipped fixes, honest recency labels. Attribution is self-reported by the harness on loopops_improve.
POST /v1/feedback/audio — users talk, the edge transcribes, and the transcript lands in the same feedback lane that clusters into bug and idea candidates. Raw audio is not retained.