1.3.0 put suspend and resume in the main menu and on the command line, which meant remembering a separate command and picking the instance separately for each of the two. They belong where you are already looking at the instance.
The menu of one instance now ends with a single line above "Back", worded for the state that instance is in:
Instance 2 - supa2.didgibot.com - running
...
Suspend it (stop it, keep its data)
Instance 2 - supa2.didgibot.com - suspended
...
Resume it (start it again with its data)
The state is read again every time the menu is drawn, so right after suspending an instance the same line reads "Resume it". The state is in the menu title, and the instance picker names it next to every instance.
The main menu's "Suspend instance" and "Resume instance" entries are gone. "Show instance" is now "Show instance (and suspend or resume it)": one way in.
Asking for the tunnel command of a sleeping instance says it is suspended, instead of printing a command that cannot work.
The line printed after suspending, and the one supaspin list prints under a sleeping instance, point at the menu line rather than at a command.
supaspin suspend N and supaspin resume N still work for scripting.
Verified on instance 2 (supa2.didgibot.com): suspended from the instance menu, the menu came back reading "Resume it" and the picker showed "(suspended)", resumed from the same line, 12/12 pods with 0 restarts and its 55 tables and 11 MB of data intact.
1.3.0 put suspend and resume in the main menu and on the command line, which meant remembering a separate command and picking the instance separately for each of the two. They belong where you are already looking at the instance.
The menu of one instance now ends with a single line above "Back", worded for the state that instance is in:
```
Instance 2 - supa2.didgibot.com - running
...
Suspend it (stop it, keep its data)
Instance 2 - supa2.didgibot.com - suspended
...
Resume it (start it again with its data)
```
The state is read again every time the menu is drawn, so right after suspending an instance the same line reads "Resume it". The state is in the menu title, and the instance picker names it next to every instance.
- The main menu's "Suspend instance" and "Resume instance" entries are gone. "Show instance" is now "Show instance (and suspend or resume it)": one way in.
- Asking for the tunnel command of a sleeping instance says it is suspended, instead of printing a command that cannot work.
- The line printed after suspending, and the one `supaspin list` prints under a sleeping instance, point at the menu line rather than at a command.
`supaspin suspend N` and `supaspin resume N` still work for scripting.
**Verified on instance 2 (supa2.didgibot.com):** suspended from the instance menu, the menu came back reading "Resume it" and the picker showed "(suspended)", resumed from the same line, 12/12 pods with 0 restarts and its 55 tables and 11 MB of data intact.
Tests: 136 pass (6 new). Version 1.3.0 -> 1.3.1.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
1.3.0 put suspend and resume in the main menu and on the command line, which
meant remembering a separate command and picking the instance separately for
each of the two. They belong where you are already looking at the instance.
The menu of one instance now ends with a single line above "Back", worded for the
state that instance is in when the menu is drawn:
Instance 2 - supa2.didgibot.com - running
...
Suspend it (stop it, keep its data)
Instance 2 - supa2.didgibot.com - suspended
...
Resume it (start it again with its data)
The state is read again every time the menu is drawn, so right after suspending
an instance the same line reads "Resume it". The instance's state is in the menu
title, and the instance picker names it next to every instance, so you can see
which ones are awake before choosing one.
- The main menu's two entries "Suspend instance" and "Resume instance" are gone.
"Show instance" is now "Show instance (and suspend or resume it)": one way in.
- Asking for the tunnel command of a sleeping instance says it is suspended and
to resume it from this menu, instead of printing a command that cannot work.
- The line printed after suspending, and the one `supaspin list` prints under a
sleeping instance, point at the menu line rather than at a command.
`supaspin suspend N` and `supaspin resume N` still work for scripting.
Verified on instance 2 (supa2.didgibot.com): suspended from the instance menu,
the menu came back reading "Resume it" and the picker showed "(suspended)",
resumed from the same line, 12/12 pods with 0 restarts and its 55 tables and
11 MB of data intact.
Tests: 136 pass (6 new). Version 1.3.0 -> 1.3.1.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
igor
merged commit 4bcdf6907c into main2026-09-22 19:32:49 +00:00
igor
deleted branch fix/suspend-and-resume-from-the-instance-menu2026-09-22 19:32:49 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
1.3.0 put suspend and resume in the main menu and on the command line, which meant remembering a separate command and picking the instance separately for each of the two. They belong where you are already looking at the instance.
The menu of one instance now ends with a single line above "Back", worded for the state that instance is in:
The state is read again every time the menu is drawn, so right after suspending an instance the same line reads "Resume it". The state is in the menu title, and the instance picker names it next to every instance.
supaspin listprints under a sleeping instance, point at the menu line rather than at a command.supaspin suspend Nandsupaspin resume Nstill work for scripting.Verified on instance 2 (supa2.didgibot.com): suspended from the instance menu, the menu came back reading "Resume it" and the picker showed "(suspended)", resumed from the same line, 12/12 pods with 0 restarts and its 55 tables and 11 MB of data intact.
Tests: 136 pass (6 new). Version 1.3.0 -> 1.3.1.
🤖 Generated with Claude Code
1.3.0 put suspend and resume in the main menu and on the command line, which meant remembering a separate command and picking the instance separately for each of the two. They belong where you are already looking at the instance. The menu of one instance now ends with a single line above "Back", worded for the state that instance is in when the menu is drawn: Instance 2 - supa2.didgibot.com - running ... Suspend it (stop it, keep its data) Instance 2 - supa2.didgibot.com - suspended ... Resume it (start it again with its data) The state is read again every time the menu is drawn, so right after suspending an instance the same line reads "Resume it". The instance's state is in the menu title, and the instance picker names it next to every instance, so you can see which ones are awake before choosing one. - The main menu's two entries "Suspend instance" and "Resume instance" are gone. "Show instance" is now "Show instance (and suspend or resume it)": one way in. - Asking for the tunnel command of a sleeping instance says it is suspended and to resume it from this menu, instead of printing a command that cannot work. - The line printed after suspending, and the one `supaspin list` prints under a sleeping instance, point at the menu line rather than at a command. `supaspin suspend N` and `supaspin resume N` still work for scripting. Verified on instance 2 (supa2.didgibot.com): suspended from the instance menu, the menu came back reading "Resume it" and the picker showed "(suspended)", resumed from the same line, 12/12 pods with 0 restarts and its 55 tables and 11 MB of data intact. Tests: 136 pass (6 new). Version 1.3.0 -> 1.3.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>