···198198199199Run `pty up` in the project directory (or `pty up /path/to/project`) to start all sessions. Run `pty down` to stop them. You can also start specific sessions: `pty up dev serve`.
200200201201+Sessions can also declare per-session environment variables:
202202+203203+```toml
204204+[sessions.api]
205205+command = "bin/api"
206206+207207+[sessions.api.env]
208208+PORT = "8080"
209209+LOG_LEVEL = "debug"
210210+```
211211+212212+The values are exported into the session's shell before the command runs (the supervisor wraps every session command in `/bin/sh -c`). They take effect on the next `pty up` after the session has stopped — restarting a still-running session via `pty restart` reuses the existing spawn args, so `pty kill <name>` followed by `pty up` is the way to pick up a changed env block on an already-running session.
213213+201214### Supervisor
202215203216The supervisor keeps sessions alive by watching for the `strategy` tag: