Observal AI Agent Observability: Sessions and Traces
Resumen
Pixel’s announcement explores Observal, an open-source project for coding-agent observability that records sessions and traces while also serving as a self-hosted resource registry. It covers the project’s renamed identity, Apache 2.0 license, technology stack, and practical questions about what session data to retain and for whom.
DEV Community
Observal AI coding agent observability: sessions and traces
A developer tells you: « the agent ran for an hour, burned a pile of tokens and shipped nothing. » There is no error code and no stack trace, only a conversation. For that case, Observal AI coding agent observability means keeping the session itself, which is the ground Observal covers: an open source repository (Apache 2.0) showing about 4.3k stars on the GitHub page I read on 9 November 2026. This post approaches it through the operational decision it forces on you: what to keep from an agent session, where, and for whom. A note on method: span.observer did not deploy Observal. Everything below comes from the README, the repository documentation and the screenshots it publishes; anything I could not read is marked « unverified ». Observal AI coding agent observability: what is it? First trap: the name moved. The README now calls itself « Agentic Resource Registry » and states « Formerly Observal: same code, same maintainers, same Apache 2.0 license ». The command is still observal and old links redirect. Today the project describes itself as a self-hosted registry of resources for coding agents (skills, MCP servers, hooks, prompts, sandboxes) with a session-tracing layer on top. If you were looking for an LLM benchmark-style evaluation platform, that is not what the documentation describes (see limits below). Facts taken from the repository: Apache 2.0 licence, Python on the server and CLI (FastAPI, Typer), React for the UI, PostgreSQL 16 for the registry, ClickHouse for telemetry, Redis for the queue. The latest commit on the main branch is dated 7 November 2026 and pyproject.toml carries version 1.17.0-dev.0; I could not read a published release on the page, so I quote no stable number. The fork count (about 1.1k) comes from the same page. What it records from an agent session The mechanism is easy to state. A hook or extension in the harness (Claude Code, Codex, Cursor, Copilot, Kiro, OpenCode, Pi, Goose, Antigravity according to the README) reads the conversation transcript and sends it to the server. The CLI first writes to a durable local outbox, then posts to /api/v1/ingest/session; the server returns the highest acknowledged position, and delivery is described as « at-least-once with effectively-once storage ». observal reconcile replays what is missing from the local source. Each record becomes an event: prompt, response, tool call, result, token update, error, subagent. Per-session aggregates (tokens, models, tools, duration) feed the dashboards. The documentation is frank about a useful limit: detail depends on what the harness writes, and Observal does not intercept MCP traffic or invent fields. Interface tour: sessions, turns, calls The next screenshot comes from the repository (docs/img, covered by the project’s Apache 2.0 licence). It shows a Pi session: duration, 17 turns, input and output tokens, cache reads, tool call count, models, then the expandable list of turns with their duration. Source : github.com The session list gives the overview: platform, input and output tokens, tools called, duration, and a « Score » column that stays empty in this demo capture. It is the only evaluation hint I read there; I do not know when or how that score is filled. Source : github.com From complaint to diagnosis: the documented method The « Debug agent failures » guide walks through four moves, which I paraphrase: find the session (filters by harness, agent, model, period), read the events in order, inspect tool call detail, then patch delivery gaps with observal reconcile. Its pattern table is the most telling part: the same tool re-called with identical arguments points to a loop; a call with no result suggests an abrupt stop or an incomplete transcript; an expected MCP call that never shows up means the model did not pick it, or the harness did not record it. The commands in the capture below are those of the README and that guide. Installing Observal: server first, CLI second Per the README there are two parts: ...

Powered by Readybot.io