Start

Starts an app by name. If the app-name argument is not provided, and the terminal is interactive - a list of all uploaded apps is shown. You can then interactively start an app.

By default, after starting the app the CLI attaches to the container's output stream and prints logs to the terminal. Press Ctrl-C to detach.

Starting an app always applies the UNLESS_STOPPED restart policy, so the agent automatically restarts the container if it exits unexpectedly. The container only stays stopped when it is explicitly stopped (e.g. via wendy device apps stop).

If the container keeps exiting and the agent has already performed at least one automatic restart, wendy device apps list shows the app as crash-looping (a red ↻ icon) rather than stopped, so a restart loop is not mistaken for a clean exit. Use wendy device logs --app <name> to view the crash output.

Flags

Examples

Start an app and stream its output:

wendy device apps start my-app

Start an app in the background (detached):

wendy device apps start --detach my-app
wendy device apps start -d my-app

When --detach is used, the CLI waits for the agent to confirm the container has started, then returns without streaming any output. If the agent reports an error or closes the stream before confirming the start, the command exits with a non-zero status instead of reporting success.

Reported outcome

When an attached start returns, the CLI reports the app's state at that point: started if it is still running (for example a multi-service app), stopped — or a short reason such as crashed (exit 1) — if it has exited, or crash-looping if it keeps restarting.