instabox 0.8.203 → 0.8.204

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/cli/SHA256SUMS CHANGED
@@ -1,6 +1,6 @@
1
- e86020ce6005918942cbe21f227fdc8b92dcd5bed48680fb76366e139c7cf8e5 instabox-darwin-amd64
2
- 067faedb41e90521806e8a774892be0b0d456d1b97d97a9e73150c77db77c4db instabox-darwin-arm64
3
- c9a7fdc00ff5fad6f84657947a67b711c11493f414590d37dc3b8f76e6cbf6fa instabox-linux-amd64
4
- 6a92faf3d6db53f7aed25a4094beb058c032a5e857daa5e59c2456f9b14599d0 instabox-linux-arm64
5
- e4d91900942d720a8d17f1012abf60adbc74853567543f85865a94e971726257 instabox-windows-amd64.exe
6
- b308f0cc3cb8d96897de91c9a7713432078394161008e95e1b4d3ed290244199 instabox-windows-arm64.exe
1
+ d105d6bb2f73ebe07d295bf6f6c4723bc855e3080133f324fac31119925a7d7f instabox-darwin-amd64
2
+ a8090ae94b46b9350d07025e0ee6e7011dee7f679ae4f23d2fb035fab2cfcf8e instabox-darwin-arm64
3
+ 9ec51733c7a43d38f3b11d12c5ca726b904cc5fa5185d8c916ac0f755167884c instabox-linux-amd64
4
+ 54156b421e0e0a89482f204d33eb0580d7b5e8378b161641a1db64634876dac8 instabox-linux-arm64
5
+ ed48f01912ae8cb2ac437eecbcd8253f64bb6651b54af6e9dde78f1beb93375f instabox-windows-amd64.exe
6
+ 1f3f400d70d787f1452f8a96e8f711aaed369ee8c51db572e4eaa1cc4970d040 instabox-windows-arm64.exe
Binary file
Binary file
Binary file
Binary file
Binary file
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "instabox",
3
- "version": "0.8.203",
3
+ "version": "0.8.204",
4
4
  "description": "A cloud box for your coding agent, the instabox CLI and its agent skills in one command: npx instabox@latest",
5
5
  "type": "module",
6
6
  "bin": {
@@ -91,7 +91,7 @@ instabox rm --yes work # delete the box (without --yes
91
91
  - `create --ready-timeout D` (1s-1h): if the box is not running D after the request, `create` tries to delete it and exits 6 with `create_timeout` within seconds (Ctrl-C while it waits does the same, exit 130). The server deletes a box only once its create has ended, so a create still running is left: the `--json` error then has `deleted: false` and `createRunning: true`, and `hint` gives the `instabox rm --yes` command to run once `instabox get` no longer shows it creating. `deleted` is `true` only once the delete is confirmed; `deletePending: true` (with `deleteOperationId`) means the delete was requested but not confirmed within 20 s, so check with `instabox get` and `rm` it if it is still there. Always check `deleted`; add `--delete-after` as a backstop. `machineId` names the box (absent only when the create request got no answer: check with `instabox get NAME`). It bounds only the create, not the box's life: a box ready in time runs as usual. The setup script and devcontainer are not counted. On exit 6, create again or try another size or template.
92
92
  - Idle auto-pause defaults to 30 minutes. Paid boxes allow any whole minute from 5 to 30 (a part minute, below 5m or above 30m is refused, nothing created), or `0` to turn it off. Free boxes keep 30 minutes unless an admin grants an idle override; asking another value on a free box fails (`spec_not_allowed`, exit 5, nothing created), so leave `--auto-suspend` out there. Idle means no agent working, no terminal use and little CPU. `create --json` and `get --json` show the effective setting as `autoSuspendAfterSeconds` (`0`: off), and `readyAt` minus `createdAt` is the create time.
93
93
  - Max run minutes is independent of idle activity: `-1` is unlimited, `0` pauses immediately, and a positive integer forces a pause after that many running minutes. Free boxes default to a managed 480-minute cap that only an admin session can override; paid boxes default to `-1` and can change it. With dynamic runtime enabled, free runs start at 120 minutes; work can extend the deadline, up to 480 minutes total. Read the current `maxRunMinutes` and `runStartedAt` instead of assuming a fixed deadline. Lease renewals and wake requests do not earn extensions. An idle override does not permit changes to a free box's runtime cap. The first limit reached pauses the box; both timers restart after sleep and wake.
94
- - A runtime pause blocks every wake path during a server-configured cooldown, 5 to 20 minutes by default (`409 machine_cooldown` with `Retry-After`). On the free plan, back-to-back max-run pauses rest longer: 60 to 75 minutes for the 2nd in a row and 120 to 135 for later ones; the count starts over when a run ends with no cooldown owed (idle pause, a user pause or stop) or starts 2 hours or more after the last cooldown. A security lock (up to 24 h) is a cooldown too and keeps the count. Wait until the `cooldownUntil` deadline shown by `instabox get`; edits cannot clear it. Afterward, a box that paused itself (idle or runtime) wakes on `exec`, `ssh`, `files`, a public port request or `instabox wake <box>`. A box you paused (`instabox suspend`) or stopped does not wake on any of these, `wake` included: run `instabox resume <box>` or `instabox start <box>`. A zero runtime cap must be changed before waking. A normal pause preserves memory and processes.
94
+ - A runtime pause blocks every wake path during a server-configured cooldown, 5 to 20 minutes by default (`409 machine_cooldown` with `Retry-After`). On the free plan, back-to-back max-run pauses rest longer: 60 to 75 minutes for the 2nd in a row and 120 to 135 for later ones; the count starts over when a run ends with no cooldown owed (idle pause, a user pause or stop) or starts 2 hours or more after the last cooldown. A security lock (up to 24 h) is a cooldown too and keeps the count. Wait until the `cooldownUntil` deadline shown by `instabox get`; edits cannot clear it. Afterward, a box that paused itself (idle or runtime) wakes on `exec`, `ssh`, `files`, a public port request or `instabox wake <box>`. A box you paused (`instabox suspend`) or stopped does not wake on any of these, `wake` included: run `instabox resume <box>` or `instabox start <box>`. A zero runtime cap must be changed before waking. A normal pause preserves memory and processes. `ps`, file writes and taking an activity lease wake it too; `get`, `ls`, `logs` and exec history never do. Full list: https://instabox.sh/docs/machines/auto-pause#what-wakes-a-machine
95
95
  - Kernel updates (a patched guest kernel, e.g. CVE-2026-98432, fixed in 6.18.60): a box runs the new kernel from its next cold boot, files kept. Running box: `instabox restart <box>` (or `instabox stop <box> && instabox start <box>`). Stopped box: `instabox start <box>`. Paused box (suspend or idle auto-pause): `instabox resume <box> && instabox restart <box>`; a paused box refuses `stop` and `restart`, and `start` resumes it with the old kernel in memory. A `sudo reboot` inside a box that comes back by itself is a cold boot too. Resume alone is not. New boxes start on the new kernel, and so do boxes from a snapshot of a box whose template does not pin its kernel. Check with `uname -r` (`6.18.60-instabox`). Templates with a pinned kernel: `android` (`-instabox-android`) and `omarchy` (restricted access, `-instabox-drm`). Their boxes keep the kernel they were created with through all of the above, and boxes from their snapshots or forks keep it too. Create a new box from the template and copy your files across (`instabox pull`, then `push`). A kernel package installed inside the box changes nothing.
96
96
  - `sudo reboot` (or `reboot -f`) inside a box boots it again by itself, in about 20 seconds: same disks, processes and `/tmp` gone. `instabox get` lags by up to 30 seconds, so `running` does not mean it is back: retry the next `exec` while it fails with `retryable: true` (`503 host_unavailable`, or `409` "machine is restarting"), and compare `cat /proc/sys/kernel/random/boot_id` to know it rebooted. Do not `start` or `restart` it meanwhile: `restart` on it does nothing and exits 75, and that 75 does not mean run `restart` again (once the box is back it would power-cycle it). `sudo poweroff`, `halt` or `shutdown -h` inside stops it until `instabox start`. Boxes from older template versions stop on `sudo reboot` too: start them. https://instabox.sh/docs/machines/lifecycle#reboot-or-shut-down-from-inside-the-machine
97
97
  - If `exec`/`ssh` stop answering (hang or time out on a running box), run `instabox restart <box>` (alias `recover`; `--timeout 20s` shortens the wait, `--json` prints the box). It stops the box, killing the VM if it has not shut down by the timeout (60 seconds by default), then starts it and waits until it runs. Files on the root disk and `/data` stay; processes do not, so start your servers again. A paused box is not hung: resume it. A box stuck in `starting` with no start in progress cannot be restarted; restart says so.