# What's new in renest 0.1.15

> After a restore, renest now tells you how to start the app, adds a renest start command, checks the GPU before you pay for the download, and names plugins that came back broken.

Published: 2026-10-01 · Releases
Canonical page: https://renest.ai/blog/renest-0-1-15

**renest 0.1.15 is on PyPI.** Upgrade with:

```
uv tool install --upgrade renest
```

This release came from watching someone outside the team restore a setup from nothing but a hand-off link. Everything below is either something that cost them time, or something the tool should have said and didn't.

## After a restore, it tells you what to do next

A restore now ends with **What's next**: where your output lands, the command that starts the app, where the packed workflow file is, and a reminder that the same restore command works on another machine. Every line is read off the nest; nothing is guessed.

The new **`renest start`** command runs that start command for you, so you don't have to copy it out and paste it back:

```
renest start --dir ./run --listen 0.0.0.0
```

If the recorded start command only listens on `127.0.0.1`, both the summary and `renest start` now say so — that address is unreachable from your browser even after you expose the port in your provider's panel. `--listen 0.0.0.0` fixes that one value.

## The pre-flight check looks harder before you pay for the download

- It now asks the GPU for a little memory and gives it back — the first check that actually touches the card instead of reading version strings.
- It runs a full `nvidia-smi` query, so a machine whose driver has come apart is caught before the download, not after.
- Both are warnings for now, not refusals: a wrong refusal would cost you a machine you already rented.

## Plugins that come back broken are named

- New nests record which system libraries each plugin's compiled files ask for, so a restore can warn about a missing library before you first drag that plugin into a workflow.
- After the app starts, the launch log is read for plugins that failed to import because a shared library is missing, and they are reported by name.

## Fixes

- `pack` could finish successfully and still print "Pack failed" as its last line.
- `capture` no longer stops with an operating-system error on certain prompt file names.

The [quick start](/docs/quick-start) and [After the restore](/docs/after-restore) pages cover the new commands.