lotel docs
Run one binary, point your coding agents at it, and see what they did. Start with the quickstart.
- QuickstartThis page gets lotel running and shows you what your coding agents did. To get the binary, see Install.
- Installlotel is one binary for macOS and Linux, on arm64 or x86_64. The DuckDB extensions it needs are built in, so there is nothing else to install. Pick one of the ways below, then go to the Quickstart.
- Sending telemetrylotel accepts OpenTelemetry over OTLP/HTTP from any app or SDK. This page covers the endpoints, formats and auth. To point a coding agent at lotel, see Quickstart.
- Retentionlotel forgets on a schedule. Every table has a use-by policy: a maximum age and a maximum size. Old data is deleted by the storage layer, the capped DuckDB extension, not by a cleanup job you have to run.
- Configurationlotel has no config file and one command-line flag. Everything else is an environment variable, read once at start. Restart lotel to apply a change.
- PrivacyCoding agents can send the text of your prompts, tool inputs and outputs, and command lines. lotel's default is to hide that content in the UI and to forget it at the retention line. This page explains what lotel stores, what it shows, and how to change that.
- The UIlotel serves its UI at http://127.0.0.1:8080. Pages are rendered on the server. A small script adds live updates, charts and faster navigation. The sidebar groups them: the Dashboard, then Agents, then Telemetry.