---
title: "wendy cloud device logs"
description: "Stream logs from containers on the device"
---

## Syntax

```sh
wendy cloud device logs [app] [flags]
```

## Examples

```sh
wendy cloud device logs --help
```

## Arguments

Argument notation from the CLI: `[app]`. Angle brackets mark required values; square brackets mark optional values. See Details for command-specific validation.

## Flags

Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--app` | string | (empty) | Filter by application name |
| `--broker-url` | string | (empty) | Tunnel broker host:port (default: cloud :443 endpoint, otherwise <cloud-host>:50052) |
| `--cloud-grpc` | string | (empty) | Cloud gRPC endpoint (optional when a default session is set via 'wendy auth use') |
| `--device` | string | (empty) | Target device hostname; `wendy run` accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
| `--json` | bool | `false` | Output in JSON format |
| `--level` | string | (empty) | Minimum log level (trace, debug, info, warn, error, fatal) |
| `--min-severity` | int32 | `0` | Minimum log severity number |
| `--no-follow` | bool | `false` | Print the logs the device replays (see --tail) and exit instead of following new output; device agents released before 2026-08-19 replay history only with --tail |
| `--read-only` | bool | `false` | Observe an existing device without starting VMs or managing updates |
| `--service` | string | (empty) | Filter by service name |
| `--tail` | int32 | `0` | Request the last N stored log batches matching the filters (default 0); continue live unless --no-follow |

## Output

Output depends on the operation and selected target. Use the command help for additional guidance..

## JSON output

The global `--json` option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.

## Exit codes

The CLI entry point returns `0` on success and for its user-cancelled or default-cleared results. Other returned errors exit with `1` and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.

## Common errors

Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see [deployment troubleshooting](../../../../../errors/). Command-specific constraints are in Details.

## See also

- [wendy cloud device](../../../../../reference/cli/cloud/device/)
- [CLI conventions and configuration](../../../../../reference/)

## Details

Stream logs from containers on the device.

Pass an app name (positionally or with --app) to see only that app's
logs. Without a filter, logs from every container and the agent itself
are streamed, which can include agent lifecycle messages.

Pass --no-follow (usually with --tail N) to print the recent logs the
device replays and exit instead of following new output.

To inspect the device kernel ring buffer (dmesg), use `wendy device os-logs`.

Use the command help for additional guidance.