---
title: "wendy device drivers install"
description: "Install a driver add-on from the registry, or a local .raw with --file"
---

## Syntax

```sh
wendy device drivers install <name> [flags]
```

## Examples

```sh
wendy device drivers install --help
```

## Arguments

Argument notation from the CLI: `<name>`. 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 |
| `--file` | string | (empty) | Install from a local .raw add-on instead of the registry |
| `--json` | bool | `false` | Output in JSON format |
| `--module` | stringArray | `[]` | Override the add-on's built-in module list (repeatable; --file only; normally the driver declares its own) |
| `--pr` | int | `0` | Resolve against a per-PR build manifest instead of releases |
| `--signature` | string | (empty) | Base64 detached signature over the .raw's sha256 (--file only; required once a signing key is embedded) |

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

## Details

With --file, streams a local .raw driver add-on to the device. Without it, resolves
&lt;name&gt; against the release manifest for the device's OS + kernel. Either way the add-on
is verified (sha256 + signature) before it is applied. &lt;name&gt; is the extension name and
must match the .raw's embedded extension-release, or the device refuses to merge it.

Use the command help for additional guidance.