Agent-first observability

Monitor logs, issues, events, and traces without making agents guess.

LogBrew gives builders a single place to read production signals, inspect context, and hand exact commands to local agents.

  1. 1
    Check the local CLI

    Run status first so LogBrew can report API reachability and auth state without exposing tokens.

  2. 2
    Open the workspace

    Use the dashboard to scan logs, issues, actions, traces, releases, and projects from one route.

  3. 3
    Hand context to an agent

    Share the Markdown mirrors or JSON commands when an agent needs exact recovery steps.

Open dashboardRead agent page
First agent read
logbrew status --json
LogsLive

Level, release, environment, project, trace, and text filters.

IssuesActionable

Open, resolved, ignored, and trace-linked failure groups.

AgentsReadable

Stable JSON, Markdown mirrors, and copy-ready CLI paths.

Start from a command

The CLI exposes token-safe status, log search, issue reading, trace detail, and mutation shortcuts that agents can parse.

Then scan the workspace

The web dashboard keeps logs, issues, actions, traces, releases, and projects visible with empty, loading, and error states.

Keep public pages readable

Every public route is planned with Markdown mirrors, metadata, robots, sitemap, and llms.txt support.