instabox 0.8.196 → 0.8.197

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
- a65a5aa6224ea2c2c99056630a68f645dde80494844bb473fddc1f974d20f5a9 instabox-darwin-amd64
2
- d24674f993cdd475d6783bbe82ec67d3ab011da62055dc1cad92a3459cb0c594 instabox-darwin-arm64
3
- 216578044863ade9130f5d3f7675063eec875966bb9bd2e2c7c01dbf79fef1ad instabox-linux-amd64
4
- a67bddfdecb11f5a4400cbfb59e3428329d48769ebc0b6a1ac33adfc83d81143 instabox-linux-arm64
5
- e3c91d8b98c924bff5cf32f7aa17a8bc8360ad4db173ce448c77c152134a2cfb instabox-windows-amd64.exe
6
- 69124723d73e34d11e30f1382f5d84d2a9bca082014b773b445d313840df726f instabox-windows-arm64.exe
1
+ ded7953b1d373a4cf76ca537b72aa44be000cf77c46e99dc157756fd3909854e instabox-darwin-amd64
2
+ 95745bad7ea37c38f4274a599e7e9ad6ee5e28f7fd777718dc3930312bd90854 instabox-darwin-arm64
3
+ 220580bfa3cad72344956b402c467fdf029542d053cb9297d62bdc8fbc212009 instabox-linux-amd64
4
+ 8d26c61894389982b246b1f95621007e7d6e8c1409c24b888a27df31c654f31f instabox-linux-arm64
5
+ ef430f5524698afa1ba037f08faf3b6e79045f4252e6613c3bbab10c19930e19 instabox-windows-amd64.exe
6
+ 8677611a03f1d09d9381178ff766ff5fd4824f236a8b4726945736bcf4027670 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.196",
3
+ "version": "0.8.197",
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": {
@@ -89,7 +89,7 @@ instabox rm --yes work # delete the box (without --yes
89
89
  - 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.
90
90
  - 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.
91
91
  - 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.
92
- - Kernel updates (a patched guest kernel, e.g. CVE-2026-98432 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.
92
+ - 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.
93
93
  - `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
94
94
  - 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.
95
95
  - Disk full (`df -h /data`)? Grow it with `instabox resize <box> --disk N` (`/data`, where HOME is), in GB. A running box grows online, no restart. A shrink, a paused box, or an image that can't grow online needs `--restart` (it stops the box, resizes the disk and starts it again; files stay, processes do not), else resize changes nothing and says so. A shrink must fit your data plus 10% (at least 1 GB), else it's refused (`disk_too_small`) and nothing changes. Free-plan boxes keep their size. The system disk (`/`) is the template's; you can't grow it.