instabox 0.8.284 → 0.8.286

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
- 95a812d5a48c780c66fd671c5c747997165b76a3b3ed33726340f8f89c435abe instabox-darwin-amd64
2
- 6075701162f2c2aa82a097dbf606cf75579b48fa755e8a21fbc9ed28725afc8c instabox-darwin-arm64
3
- b9177251e52261486011a8170055bf50de23a1bbe08fc82871a215b255674e3b instabox-linux-amd64
4
- 90ad67df566042b722564e034e5bae57c82f19ac7a1395c0685a38b1df0fd400 instabox-linux-arm64
5
- 4c481ebc61c07c29e9a73e77bee1cd29cedd2e8ede25499c4fc7055d75ed1394 instabox-windows-amd64.exe
6
- 35bac37b3dae64172b4f8aa1e0d664e662ef1ac4a690afea663100eb6de787fa instabox-windows-arm64.exe
1
+ 7cddbd303185fc48696bac8e286aa5787bbccff7d1ac4eab3663139099c0727f instabox-darwin-amd64
2
+ 7b317daad275deba80528bb898b0bf76a2f1e852062987dfe5fb0dba9b1b8301 instabox-darwin-arm64
3
+ 0ef609f7f7cb2272aa7af5291179ec27c1d85945c50f06ca2bed14a9e4a3ad8d instabox-linux-amd64
4
+ 0ff0d3cc88a4acb9824982cdc6e5e9c097f2a6ebf394b6d0dcf306bc43cadb09 instabox-linux-arm64
5
+ 045d0d55e3b81d026040926dbe2d768bae1e583e6b1cc4edf76fc888d7ae5050 instabox-windows-amd64.exe
6
+ 9615b374dea15539660ba668fd580e207ca1396d508d55f4ac7d9b388b2da5b8 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.284",
3
+ "version": "0.8.286",
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": {
@@ -31,5 +31,5 @@
31
31
  "devDependencies": {
32
32
  "prettier": "3.9.9"
33
33
  },
34
- "gitHead": "ff7faae810293dd72a0a0f2bc92d4907010a6770"
34
+ "gitHead": "39d447457bcb4f57836db353b59a588f19c35cc2"
35
35
  }
@@ -97,6 +97,7 @@ instabox rm --yes work # delete the box (without --yes
97
97
  - 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
98
98
  - 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.
99
99
  - `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
100
+ - `instabox get`/`ls` showing `Running (host unreachable since ...)` (`--json`: `runtime.hostUnreachable: true`, `runtime.ready: false`, `runtime.hostLastSeenAt`) means the server the box runs on is not answering: exec, files and SSH fail with `503 host_unavailable`, and `start`/`resume` exit 75 instead of reporting success. Nothing to do on the box: retry later; it clears once the host answers again.
100
101
  - 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.
101
102
  - 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.
102
103
  - Need more CPU or memory? A paid box moves to another of its plan's sizes with `instabox resize <box> --vcpus N --mem-mib M` (Pro: 2/4096, 4/8192, 8/16384; Builder: 2/4096 up to 16/32768; Team: 2/4096 up to 32/65536), while it is stopped; add `--restart` on a running box, and run that from outside the box (from inside, the stop would end the command before the start, so resize refuses it; the same goes for a shrink with `--restart`). A size the plan does not have is refused before anything stops. The new size applies at the next start; free-plan boxes keep theirs.