instabox 0.8.221 → 0.8.222

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
- 18a8f3b8b742f369a7f628c4147f9a771110af21a0ac8c27085443f68669acdc instabox-darwin-amd64
2
- 675cb4755e4625ec9c3b9789e62343eb22cf547a161c584f024e889ce14816f5 instabox-darwin-arm64
3
- 1c0c5d7a7fe420a26501ba2d89a309ac9eab192d26a7f93e98c8aae374dc7929 instabox-linux-amd64
4
- 4f101cebb6ae770eb1d350e06af24a0f22da97b3b96b61f0013a9ec609629cb1 instabox-linux-arm64
5
- b6f2783fd56956c186e024050c80833e8861df6bd323a146c117ae69d6399680 instabox-windows-amd64.exe
6
- a1561b9fd4ee594b14304b7b9b3163026040e3265ee3a6199942df5c3e902cd3 instabox-windows-arm64.exe
1
+ 02221ac068903e90dc460607fa84430372998c0d98004927f43757be986bc01c instabox-darwin-amd64
2
+ c1c3937209d8716010185496035624424057c6048313c737b3d86b10a65a92cc instabox-darwin-arm64
3
+ 7f4e2fe219c431a9caa9e30425219d78e6723a4d58de2c64f5b726ec04f44e87 instabox-linux-amd64
4
+ 16a3457ee05edc8ac8c845a732816c4f7b9f7709de26a0f41705de38a9280f90 instabox-linux-arm64
5
+ 941924a0f4dc6289c25edf23204efc2342ba95ca0d7acb9a9d203625f562db31 instabox-windows-amd64.exe
6
+ 35f26860430f0403db4b44fe4bf3ad36d465cb6464260deb2eb4506d4414ff0e 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.221",
3
+ "version": "0.8.222",
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": {
@@ -73,7 +73,7 @@ instabox pull work /data/home/app/out.log # copy a file or directory out (
73
73
  instabox cp ./x.tgz work:/data/home/x.tgz # scp-style, either way (cp work:/data/home/x.tgz .)
74
74
  instabox push work ./app/ /data/home/app # trailing / (or /.): app's files into /data/home/app, no app/app
75
75
  instabox auto-suspend work 10m # idle time before a paid box pauses
76
- instabox max-run work 120 # pause a paid box after two running hours
76
+ instabox max-run work 60 # pause a paid box after one running hour
77
77
  instabox max-run work -1 # remove the runtime cap; idle policy still applies
78
78
  instabox stop work && instabox start work # stop ends processes, keeps disks
79
79
  instabox suspend work && instabox resume work # pause/resume keeps running processes
@@ -91,7 +91,7 @@ instabox rm --yes work # delete the box (without --yes
91
91
  - To find the boxes your session made, tag each with `create --meta session=ID` and list them with `instabox ls --meta session=ID [--json]` (repeat `--meta` to match several pairs, all must match). The server filters, within your own orgs only. Do not keep box IDs by hand or probe for 404s.
92
92
  - `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.
93
93
  - 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.
94
- - 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
+ - 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; the service may pause a free run earlier. Paid boxes default to `-1` and can change it. Read the current `maxRunMinutes` and `runStartedAt` instead of assuming a fixed deadline. 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.
95
95
  - 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
96
96
  - 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.
97
97
  - `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