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

# Event streams

> Observe Radius command activity and workspace changes as JSON Lines.

Stream events until the command is interrupted:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius events --follow --jsonl
```

Filter events to a window or group:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
radius events --window window_1 --follow --jsonl
radius events --group group_example --follow --jsonl
```

## Command lifecycle events

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
command.started
command.finished
command.failed
```

Each line is one JSON object:

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{"event":"command.finished","timestamp":"2026-08-14T19:42:01.000Z","windowId":"window_1","payload":{"value":{"id":"tab_42"}}}
```

Use event streams for logging, agent observation, and coordination between
long-running tools. A normal shell script that runs commands sequentially does
not need to subscribe.

<Note>
  Events describe activity that has already occurred. Subscribing does not give
  the subscriber ownership of tabs or cause Radius to keep enforcing a layout.
</Note>