> ## Documentation Index
> Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Mobile app

> How the LogBrew mobile app fits with the CLI-first workflow for live telemetry, push notifications, and triage.

The LogBrew mobile app is the live companion for production awareness. The CLI
is the canonical workflow for agents, while the mobile app helps humans see new
issues and important changes quickly.

## What the app shows

<CardGroup cols={2}>
  <Card title="Live stream" icon="radio">
    A live stream for new native log, issue, trace span, and action events.
  </Card>

  <Card title="Push notifications" icon="bell">
    Alerts for important unresolved issues and release activity.
  </Card>

  <Card title="Issue triage" icon="bug">
    Read the issue, status, release, environment, and occurrence count.
  </Card>

  <Card title="Release context" icon="tag">
    See which release emitted the telemetry before you open a laptop.
  </Card>
</CardGroup>

## Live event names

The live feed uses stable native event names so mobile clients, humans, and
agents can recognize the stream without guessing.

| Event type          | What it carries                                    |
| ------------------- | -------------------------------------------------- |
| `native_log`        | A log event with canonical `level` and `severity`. |
| `native_issue`      | A grouped issue event.                             |
| `native_trace_span` | A trace span event.                                |
| `native_action`     | A product action event.                            |

Each live event uses a `{ "type": "...", "data": ... }` envelope.

## How it fits with agents

Use the mobile app for awareness, then use the CLI for deeper investigation.

```bash theme={null}
logbrew read issue <issue_id> --json
logbrew read trace <trace_id> --json
logbrew explain issue <issue_id> --json
```

<Note>
  The mobile app should never be the only way to understand production. Every
  core workflow must remain available through the CLI or API.
</Note>