# LogBrew for agents
This page explains how agents should read LogBrew without needing browser state, hidden context, or private dashboard access.

## First safe read
```bash
logbrew status --json
```

## Use predictable public URLs
Agents should find public LogBrew context through stable localized pages, Markdown mirrors, llms.txt, robots.txt, and sitemap.xml.

- Use /en/agents.md when plain text is the safest input.
- Use /en/docs.md for command and API route context.
- Use /llms.txt to discover public agent-readable resources.

## Start with token-safe status
The CLI should tell agents whether local auth, API reachability, and recovery steps are ready without exposing token material.

- Run logbrew status --json before project reads.
- Follow next steps from JSON and human output instead of guessing.
- Keep token material out of prompts, logs, screenshots, and public pages.

## Prefer resource-specific reads
Agents should read logs, issues, actions, traces, releases, and projects through the same resource vocabulary used by humans.

- Use filters for release, environment, project, trace, level, status, name, and user.
- Use issue and trace detail routes when an identifier is known.
- Use Markdown mirrors for public context and the authenticated API for private project data.

## Keep private data behind auth
Public agent surfaces must stay readable, while dashboard and project data remain protected by backend auth and noindex metadata.

- Do not scrape dashboard data without a valid user session.
- Do not publish private project names, tokens, traces, or deployment details.
- Use public pages for general learning and authenticated routes for scoped user data.

## Public agent links
- Agents: https://logbrew.co/en/agents
- Agents Markdown: https://logbrew.co/en/agents.md
- Docs Markdown: https://logbrew.co/en/docs.md
- Home Markdown: https://logbrew.co/en/page.md
- llms.txt: https://logbrew.co/llms.txt
- Sitemap: https://logbrew.co/sitemap.xml