instabox 0.8.285 → 0.8.287

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
- 9e9d2aefbbbd88137615da1a57b9e8ec4231eb2d6113720e7b1c33d6bd086d58 instabox-darwin-amd64
2
- ccd1c53176c8af84e7cb254410d94b697237b20edfa7d36fae67b5ae5708a244 instabox-darwin-arm64
3
- b5cb47de688f1286ca9b8054c5315262111a01209b128f6169269328e318b6dc instabox-linux-amd64
4
- 8ca3e2f377023d97e87a5c6552b5322f180b0b91dbaeafb8bc9f386c98a4b70e instabox-linux-arm64
5
- d60e4241c087154a4d3d1b82f316e50aac8d8f3fca805a7a5e48267cd0337272 instabox-windows-amd64.exe
6
- a691de9f7845cc446df63e5e17b23b6014d62eb26fe6de57cd62e69a1a92d153 instabox-windows-arm64.exe
1
+ 68cb67e30938e8f119cad94cd1d7536acfa67f7ad0f414eeb92ab15732e86e0f instabox-darwin-amd64
2
+ 5328c76ab666c1b998afec1409541749b75479b9ba90193e4ff299f8eb180884 instabox-darwin-arm64
3
+ a4b8ed70e8a6656f031431b82d1c92d0f197f968cd9d721ce862b65c1f161ecc instabox-linux-amd64
4
+ 3d81ed19b32f7474d306e88d6f6eacd10177137b2cd7e5fee2e71d71a62fbfa4 instabox-linux-arm64
5
+ 00100d8e498ac957340ad277be2c7439b660262c280a2899212081cb98de5087 instabox-windows-amd64.exe
6
+ 36412da0c9ea327a91fada0b23fea4b84c50aa2a21d4792146b11149cd29f81e 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.285",
3
+ "version": "0.8.287",
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": "eb01ec8a7405bf79461ecd59913969163dac4b23"
34
+ "gitHead": "846265b669c62bbbe3a45c3ce7c86c50ea0a4689"
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.