---
title: "wendy data export-stream"
description: "Export durable stream records, optionally capturing continuously"
---

## Syntax

```sh
wendy data export-stream <app-id> <stream> [flags]
```

## Examples

```sh
wendy data export-stream --help
```

## Arguments

Argument notation from the CLI: `<app-id> <stream>`. 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 |
| --- | --- | --- | --- |
| `--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 |
| `--follow` | bool | `false` | Continuously export chunks into --output directory; requires --reclaim |
| `--interval` | duration | `1s` | Delay between continuous export chunks |
| `--json` | bool | `false` | Output in JSON format |
| `--output` / `-o` | string | (empty) | New output file, or destination directory with --follow |
| `--reclaim` | bool | `false` | Export an oldest journal chunk, sync it locally, then reclaim it on the device |
| `--service` | string | (empty) | Application service name |

## 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 data](../../../../reference/cli/data/)
- [CLI conventions and configuration](../../../../reference/)

## Details



Use the command help for additional guidance.