Glossary
Blop lets people and their coding agents observe, investigate and verify the software they change, locally first and optionally with a shared cloud workspace.
Language
Section titled “Language”Local plane
Section titled “Local plane”Local plane
Section titled “Local plane”Everything that runs on a developer’s machine and works without an account: the collector, the Inspector, local telemetry and local memory.
collector
Section titled “collector”The local process that receives OpenTelemetry traces and logs from your app and coding agents and stores them on your machine. Avoid: monitor, monitoring server, daemon
Inspector
Section titled “Inspector”The local web interface for browsing the collector’s traces, logs, services and findings. Avoid: dashboard, local web UI
The record of one request or operation as it moves through your software, made up of spans.
One timed step within a trace, such as a database call or an HTTP request.
A timestamped message emitted by a service, kept alongside the traces it belongs to.
service
Section titled “service”A named application or process that sends telemetry to the collector.
One command execution recorded by blop run, with the issues it saw. A run is not a trace.
A failure the collector groups across runs and telemetry, with a state: open, muted or fixed.
A deterministic pass over local telemetry that produces findings.
finding
Section titled “finding”An audit result with trace and span evidence attached. Avoid: insight (when the result is local)
local memory
Section titled “local memory”Notes and findings saved on your machine that your agent can recall later, without an account. Avoid: local brain, local graph
Verification
Section titled “Verification”browser check
Section titled “browser check”A .blop.ts file, run with blop test, that drives a real browser to confirm a behaviour works.
Avoid: active check, authored check, flow verification, E2E test, intent-based test
check run
Section titled “check run”One execution of browser checks or another test suite (Vitest, JUnit), recorded in Blop Cloud. Avoid: run, test run
Browser Harness
Section titled “Browser Harness”The controlled browser tooling that browser checks and other agents use to operate real browsers. Avoid: harness (when it stands alone)
provider
Section titled “provider”The model provider that powers a browser check.
Blop Cloud
Section titled “Blop Cloud”Blop Cloud
Section titled “Blop Cloud”The hosted web app where teams keep projects, runs and shared memory, and manage Blop from the browser, CLI or hosted MCP. Avoid: web app, control plane, hosted app
workspace
Section titled “workspace”A team’s space in Blop Cloud. It holds projects, members and enabled apps.
project
Section titled “project”One software product within a workspace, which groups its runs, findings and knowledge.
organization memory
Section titled “organization memory”Knowledge, rules and procedures a team has chosen to share, with sources and revision history, that agents can recall. Avoid: organizational brain, knowledge graph, team memory
A feature of Blop Cloud that a workspace owner can turn on or off for the workspace.
Agents
Section titled “Agents”coding agent
Section titled “coding agent”An AI tool that edits code on your behalf, such as Claude Code or Codex, and which Blop observes and supports without taking control.
An integration point that lets Blop capture a coding agent’s activity as telemetry.
A packaged set of instructions, as a SKILL.md file, that a coding agent can load for a specific task.