instabox 0.8.185 → 0.8.187

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
- 483a10a140f79001f876e98273ffa179cbf2e5577f5fa009db0b8c393b585d67 instabox-darwin-amd64
2
- 0a6df1d244e9b1bcab0a7a9bddc0434fb8b5f086ddd2a6fb969b9e668eba68b9 instabox-darwin-arm64
3
- 5bb765652ba1425a67d4807942d90b82dd4a17bbda58a538ffbad70132faa5f2 instabox-linux-amd64
4
- 0e9beffdf7007ffd5c56d23a694668690531da2fab7771d4f462d95d6741f859 instabox-linux-arm64
5
- 13b926bbe854ad21e58f8e3b40086e343f9d64bd7a9a1764f3f830961a6c363d instabox-windows-amd64.exe
6
- 762668f68495523b7ee0dea3235b31df41bb1cc93a7c0b9103c20a81d3900bf5 instabox-windows-arm64.exe
1
+ 26f87154c13e43fd7344e106e54bf90d6e711583c741081c2765a2dab8d1b281 instabox-darwin-amd64
2
+ 9c6f5218972c8b4b25f293ffb29f016938c71285ea8ed6e21a3b4c86632f39c9 instabox-darwin-arm64
3
+ 2ce2f2566665f284af620e901bca5efc2a6c8e07f07bc605125084589fce8aaa instabox-linux-amd64
4
+ 65064e76bf4df9f05a7b0ccce10e2e702b568a3a72beb1522ca8b759306c6c70 instabox-linux-arm64
5
+ c7c26e03e664ae83f58f20e97ed071b98e5e7f668741e6a6be366e0318b0a3be instabox-windows-amd64.exe
6
+ a9b9ebce519d96a23232c80b53efec312383e8e4bbcd6fd5baa18d230746be1d 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.185",
3
+ "version": "0.8.187",
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": {
@@ -90,7 +90,7 @@ instabox rm --yes work # delete the box (without --yes
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
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.
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.md#rebooting-and-powering-off-from-inside-a-box
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.
96
96
  - 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.
@@ -184,7 +184,7 @@ For another CI, or a job that must stay on GitHub's runner, a step runs one comm
184
184
  instabox run --push . --timeout 10m -e CI=1 -- 'npm ci && npm test'
185
185
  ```
186
186
 
187
- Both ways, their limits and the reasons a job is refused: https://instabox.sh/docs/ci.md
187
+ Both ways, their limits and the reasons a job is refused: https://instabox.sh/docs/use-cases/ci.md
188
188
 
189
189
  ## Moving work onto a box
190
190
 
@@ -192,7 +192,7 @@ To move the repo the user is working in (with its worktrees, uncommitted work an
192
192
 
193
193
  ## MCP clients
194
194
 
195
- Keep using the CLI and this skill. If the user wants instabox as MCP tools in Claude Code, Cursor, Codex, OpenCode or Antigravity, `instabox mcp init claude|cursor|codex|opencode|antigravity` writes that client's config (the client then runs `instabox mcp start`, which uses this CLI's sign-in or `INSTABOX_API_KEY` and never opens a browser); `--hosted` points it at `https://api.instabox.sh/mcp` with the key read from `INSTABOX_API_KEY` (Antigravity reads no variables, so add `--inline-key` there). The user restarts the client afterwards. Details: https://instabox.sh/docs/mcp.md
195
+ Keep using the CLI and this skill. If the user wants instabox as MCP tools in Claude Code, Cursor, Codex, OpenCode or Antigravity, `instabox mcp init claude|cursor|codex|opencode|antigravity` writes that client's config (the client then runs `instabox mcp start`, which uses this CLI's sign-in or `INSTABOX_API_KEY` and never opens a browser); `--hosted` points it at `https://api.instabox.sh/mcp` with the key read from `INSTABOX_API_KEY` (Antigravity reads no variables, so add `--inline-key` there). The user restarts the client afterwards. Details: https://instabox.sh/docs/integrations/mcp.md
196
196
 
197
197
  ## When instabox itself gets in your way (feedback)
198
198