instabox 0.8.63 → 0.8.64

package/cli/SHA256SUMS

@@ -1,6 +1,6 @@
-aded5fc340f2d1829d973bf1b8cd30025a445d0c722006a0e079c933e6e314e2  instabox-darwin-amd64
-c53d42d6622e535813d3cb89b46008c21fb0ef9771fb5dfae7fa709a7231d626  instabox-darwin-arm64
-ad6f4ef3b0b3338442ecb2a7c4dbee32074521e40065556a89b695872fbb5276  instabox-linux-amd64
-f1450029a4e198dd5a0e031ffd8acfd94fb9e263a2fa8370651588fe3ba19f61  instabox-linux-arm64
-080c350073b336f09e3f0e92491fceeb8bee30cb73d23fc51acd35d46f598bcd  instabox-windows-amd64.exe
-b6d19a962d0c7dc96fda6f5142f7eba1cc72f69867e0cbd0afc8f6d02da8e1c2  instabox-windows-arm64.exe
+f21008f2e5a4f286986ca8f34baf1bb81159a99c1457d35844d2fa1bfe6db7bd  instabox-darwin-amd64
+e3b3e4c7f5d33de29e882751242bedbc9e569de622437a76faff7ca1007f8499  instabox-darwin-arm64
+6f3c07232fe19727ae45ac3453cae120422bd87dc3c99a8d817aa1aaef733518  instabox-linux-amd64
+c620e30ae9c45a1d007bde6e9ea32646feda9a8043389b670f866259253f9c0a  instabox-linux-arm64
+614101c167f0c1287c72f40f55161f6040a998735ec205b963ac88d49b39afee  instabox-windows-amd64.exe
+30686287712f74a8addadfa7accb672672afbd44038d210284d2b092ac4d24af  instabox-windows-arm64.exe

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instabox",
-  "version": "0.8.63",
+  "version": "0.8.64",
   "description": "A cloud box for your coding agent, the instabox CLI and its agent skills in one command: npx instabox@latest",
   "type": "module",
   "bin": {

package/skills/instabox/SKILL.md

@@ -39,13 +39,14 @@ To run an older or different image (say `node:16-buster`), use Docker in the box
 
 ## Sizes
 
-A box is 4 vCPU / 8 GB of memory unless `create` names another size of the account's plan with both `--vcpus` and `--mem-mib`:
+A box is 4 vCPU / 8 GiB of memory unless `create` names another size of the account's plan with both `--vcpus` and `--mem-mib`:
 
-| Plan | Sizes (`--vcpus` / `--mem-mib`)               |
-| ---- | --------------------------------------------- |
-| Free | 4 / 8192 (default)                            |
-| Pro  | 2 / 4096, 4 / 8192 (default), 8 / 16384       |
-| Team | 2 / 4096, 4 / 8192 (default) up to 32 / 65536 |
+| Plan    | Sizes (`--vcpus` / `--mem-mib`)               |
+| ------- | --------------------------------------------- |
+| Free    | 4 / 8192 (default)                            |
+| Pro     | 2 / 4096, 4 / 8192 (default), 8 / 16384       |
+| Builder | 2 / 4096, 4 / 8192 (default) up to 16 / 32768 |
+| Team    | 2 / 4096, 4 / 8192 (default) up to 32 / 65536 |
 
 `instabox whoami --json` lists the sizes this account may create as `allowedSpecs` (the default first, then the plan's others and any an admin granted); check it rather than assuming the plan. Another size is refused with `400 spec_not_allowed`, whose message names the account's sizes. Pick a size for the work: 2 vCPU (paid plans) for light editing or a single agent, the default for most builds, 8 vCPU (paid plans) for heavy builds or many processes. `--snapshot` takes the same flags. A paid box moves to another of the plan's sizes while stopped (`instabox resize <box> --vcpus N --mem-mib M [--restart]`, applied at its next start; that start fails with `no_capacity` if its host has no room for the new size, or `host_unavailable` if the host's node-agent cannot resize yet, and the box stays stopped at the new size); a free box's size is fixed.
 
@@ -89,7 +90,7 @@ instabox rm --yes work                          # delete the box (without --yes
 - `sudo reboot` inside a box reboots it: `instabox get` shows `starting`, then `running` (same disks, processes gone); wait for `running` before the next `exec`. `sudo poweroff` inside stops it until `instabox start`. Boxes from older template versions stop on a reboot too: start them.
 - 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.
 - 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.
-- 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), 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.
+- 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.
 - Use `exec` to run a command and read its output, and `ssh` for an interactive shell.
 - Use `cp`, `push` and `pull` to move files, not `echo <base64> | base64 -d` over `exec`. `cp LOCAL work:PATH` and `cp work:PATH LOCAL` copy either way (`-r` for directories). `push work LOCAL [REMOTE]` copies a file or directory to REMOTE (default: HOME); an existing directory or a path ending in `/` receives it under its own name. REMOTE's parent directory must exist (else `missing_parent`); `-p` creates it. A file streams byte-for-byte, up to 5 GiB, and its sha256 is checked; a directory goes as a gzipped tar of at most 1 GiB. From inside a git repo, a directory push sends only tracked files (`git ls-files -c`); `--all` adds untracked files git does not ignore; `node_modules`, build output and `.git` stay behind. `pull work REMOTE [LOCAL]` copies back the same way: a file streams, any size; a directory is read as root, at most 32 MiB compressed. Over HTTP: `PUT /v1/machines/{id}/files?path=P` with the raw body, `GET /v1/machines/{id}/files/content?path=P`, and `POST /v1/machines/{id}/files/upload-url` for a signed URL that takes the PUT without a key.
 - `exec` with one argument after `--` runs it as a shell string (`instabox exec work -- 'ls | wc -l'`); several arguments run as that exact argv, each quoted for you (`instabox exec work -- bash -c 'echo a b > /tmp/x'`).