You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/agents/index.md
+26-5Lines changed: 26 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -244,20 +244,41 @@ vp list --running # shows only running agents
244
244
vp list --json # machine-readable output
245
245
```
246
246
247
-
Stop a specific agent or all agents:
247
+
Stop a specific agent, a single container, or all agents:
248
248
249
249
```bash
250
-
vp stop claude # graceful stop (10 s timeout)
251
-
vp stop claude -f # force stop immediately
252
-
vp stop --all # stop every VibePod container
250
+
vp stop claude # stop every container for the `claude` agent
251
+
vp stop vibepod-claude-a1b2c3d4 # stop one specific container (from `vp list`)
252
+
vp stop claude -f # force stop immediately
253
+
vp stop --all # stop every VibePod container
253
254
```
254
255
256
+
The argument is resolved as an agent name/shortcut first; anything else is looked up as a container name or ID. Only VibePod-managed containers can be stopped this way.
257
+
255
258
### Caveats
256
259
257
260
-**`auto_remove` (default: `true`)** — By default, containers are automatically removed when they stop. This means you cannot restart a stopped detached container; you need to `vp run` again. Set `auto_remove: false` in your [configuration](../configuration.md) if you want stopped containers to persist.
258
-
- **No built-in re-attach** — VibePod does not currently have a command to re-attach your terminal to a detached container. Use `docker attach <container>` or `docker exec -it <container> bash` directly.
259
261
-**Session logging** — Sessions started with `--detach` are not recorded in the VibePod session log since VibePod does not capture the interactive I/O. If you need session logging, run without `--detach`.
260
262
263
+
## Reattaching a terminal
264
+
265
+
Closing the terminal window that runs `vp run` does **not** stop the container — the agent keeps running in the background under Docker. This is by design: the container's lifecycle is tied to Docker, not to your shell. Use it as a feature when you want to keep a long-running session alive across terminal restarts.
266
+
267
+
To rejoin a running container:
268
+
269
+
```bash
270
+
vp list --running # find the container name
271
+
vp attach <container># reattach your terminal
272
+
```
273
+
274
+
If exactly one managed container is running you can omit the name:
275
+
276
+
```bash
277
+
vp attach
278
+
```
279
+
280
+
`vp attach` only works for containers that are already running and managed by VibePod. When you are done, close the terminal to leave it running, or stop it explicitly with `vp stop <container>`, `vp stop <agent>`, or `vp stop --all`.
281
+
261
282
## Connecting to a Docker Compose network
262
283
263
284
When your workspace contains a `docker-compose.yml` or `compose.yml`, VibePod detects it and offers to connect the agent container to an existing network so it can reach your running services.
Copy file name to clipboardExpand all lines: docs/quickstart.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,9 @@ VibePod will:
35
35
36
36
Press **Ctrl+C** to stop the container when you are done.
37
37
38
+
!!! note
39
+
Closing the terminal window does not stop the container — the agent keeps running in the background. Use `vp list --running` to see it and `vp attach <container>` to rejoin the session. See [Reattaching a terminal](agents/index.md#reattaching-a-terminal) for details.
40
+
38
41
## Shortcuts
39
42
40
43
You can start agents with either the full name or a single-letter shortcut:
0 commit comments