blop
Blop provides a local-first OpenTelemetry observability layer that coding agents can invoke as a standard command-line tool, giving developers trace-level runtime evidence without leaving their terminal. The tool captures traces, logs, and memory reads from agents like Claude Code and Codex, with deterministic audits that cite specific trace and span IDs. It binds to loopback by default and is read-only, keeping the coding agent in control.
- Developer Tools
- Software Only
Funding
Founders
Founder details are not available yet.
Product
Problem
Teams shipping software with coding agents lack a direct view of runtime behavior. A failing test provides an assertion and log stream but not the correlated request path, slow span, or trace-level context, forcing developers to leave the coding loop and manually translate context from separate observability tools.
Solution
Blop provides a local-first OpenTelemetry observability layer that coding agents can invoke as a standard command-line tool. A single command starts a local OTLP receiver backed by SQLite; any existing OpenTelemetry exporter can point to it without SDK changes. Agents query services, traces, logs, and audit findings through bounded CLI commands with stable JSON output and documented exit codes. Audits are deterministic and cite trace IDs, span IDs, timestamps, and attributes behind every finding, distinguishing observed facts from derived conclusions. The tool is read-only, binds to loopback by default, and includes no model loop or autonomous action, keeping the coding agent in control.
Target Audience
Primary users are software development teams and individual developers who use coding agents and need runtime evidence to verify changes, investigate failures, and audit agent work without leaving their terminal workflow.
Features
- OTLP-native collector accepting traces and logs over HTTP in JSON or protobuf from any language
- Local SQLite store with configurable retention, no account, and no external dependencies
- Stable `--json` output contract (schema `blop.cli/v1`) with bounded result sizes, deterministic ordering, and documented exit codes
- Read-only queries including `status`, `services`, `traces`, `trace`, `logs`, and `audit` with progressive disclosure from summary to individual spans
- Deterministic audits that cite trace IDs, span IDs, timestamps, durations, and status codes for every finding
- Optional authored browser checks via `.blop.ts` files for active verification of user flows against local, preview, staging, or deliberately selected production targets