instabox 0.8.225 → 0.8.227

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/README.md CHANGED
@@ -52,7 +52,7 @@ npm pack # a tarball with the binarie
52
52
 
53
53
  ## Release
54
54
 
55
- Nothing to do by hand. [`npm-release.yml`](../.github/workflows/npm-release.yml) runs on every push to `main`. When anything the package ships has changed since the last `npm-v*` tag (`cmd/instabox` and the packages of this module it imports, `npm/`, `skills/`, `go.mod`, `go.sum`, `scripts/build-cli.sh`), it builds the six CLI binaries with `scripts/build-cli.sh`, puts them in `cli/` with [`scripts/bundle-cli.mjs`](scripts/bundle-cli.mjs) (each checked against `SHA256SUMS`), publishes `instabox` through npm trusted publishing (no npm token anywhere), and tags the commit `npm-v<version>`. Anyone who can merge can release.
55
+ Nothing to do by hand. [`npm-release.yml`](../.github/workflows/npm-release.yml) runs on every push to `main`. When anything the package ships has changed since the last `npm-v*` tag (`cmd/instabox` and the packages of this module it imports, `npm/`, `skills/`, `go.mod`, `go.sum`, `scripts/build-cli.sh`), it builds the six CLI binaries with `scripts/build-cli.sh`, puts them in `cli/` with [`scripts/bundle-cli.mjs`](scripts/bundle-cli.mjs) (each checked against `SHA256SUMS`), publishes `instabox` through npm trusted publishing (no npm token anywhere), and tags the commit `npm-v<version>`. Anyone who can merge can release. Only main publishes: the `npm` GitHub environment's deployment branches are limited to `main`, because npm's trusted publisher does not check the branch and `workflow_dispatch` can run the workflow on any branch.
56
56
 
57
57
  The version is [`scripts/next-version.mjs`](scripts/next-version.mjs)'s: `package.json` names a line (`0.8.0`), and merges ship `0.8.0`, `0.8.1`, `0.8.2`, … on it. `package.json` changes only to start a new line (a new minor or major); a line below the highest published stable version is refused, so a reverted `package.json` cannot move `latest` back. A version with a `-` (`0.9.0-rc.1`) is published as written, once, under the `next` dist-tag. The workflow sets the version with `npm version` at publish time; the committed `package.json` keeps the line's base. `instabox --version` prints `<npm version>+<commit>`.
58
58
 
package/cli/SHA256SUMS CHANGED
@@ -1,6 +1,6 @@
1
- f47d29c7d7985b2fc7f81ee353e51e75b515933e63ba073727e8f1a1af74cbba instabox-darwin-amd64
2
- 571c3ff0ac164dc60c9aaa9ac3723c63f8dc5cbd037e0157c3a7ca7efe8e93c3 instabox-darwin-arm64
3
- f0a1747d0cbeba128dab9481ecf2e4eedb80d22bf261ae96641ded67ca25c0ca instabox-linux-amd64
4
- 27b5ff2b424e52e7182705ecb1ccae7841d29f672d8dc104206306a52ae0e367 instabox-linux-arm64
5
- 14fd3c4c656a162b20f6257d4d738fc6ec7216da71c0469528877c907562b0a9 instabox-windows-amd64.exe
6
- f9ebfe40fecfbf211d46573fe80d0b6a5be21ecff5d0438a87fb9bccb56e5eec instabox-windows-arm64.exe
1
+ 1ce4618eeccc2a8c3fb4b0dfebb052cb5402fc0082668475138f5be3bbab73ad instabox-darwin-amd64
2
+ e1ce221d6accf7a533836d04aa210e93637dbbeaba50944f93fa7d8669e2933c instabox-darwin-arm64
3
+ 30c3a8cc8a536ece68b5f262af14835e1f8ec0e73e9e9d11088a03b8f38b0dda instabox-linux-amd64
4
+ 2a10b243c9da0185c6f64f714ffcba46109a1b1404918ee5b0852424415ac1d9 instabox-linux-arm64
5
+ a624a8a0c2b9f3760614bb96c78ce2dad0a7d56d98afd9c1c957e067a4080546 instabox-windows-amd64.exe
6
+ 45cb9f3ffff1dc70141002629bcb45166f748db4e4aeab70cc8307c7b44b486e 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.225",
3
+ "version": "0.8.227",
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": {
@@ -100,7 +100,7 @@ instabox rm --yes work # delete the box (without --yes
100
100
  - 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.
101
101
  - Use `exec` to run a command and read its output, and `ssh` for an interactive shell.
102
102
  - 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.
103
- - `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'`).
103
+ - `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'`). Always put `--` right before the command, with exec's own flags (`--cwd`, `--timeout`, `--json`, ...) before it: without it, the command's words that start with `-` are read as exec's flags, up to the command's own `--` if it has one (`instabox exec work unshare --mount -- python3` fails with `--mount is not an exec flag`, and `instabox exec work ls --json` takes `--json` for exec).
104
104
  - For a one-off job that needs no box afterwards, use `instabox run [--template T | --from SNAPSHOT] [--name N] [--push DIR] [--cwd D] [-e K=V ...] [--timeout 60s] [--keep] [--setup-file PATH|-] [--json] -- <cmd...>` instead of create + exec + rm: it deletes the box even when the command fails or the run is interrupted (Ctrl-C, SIGTERM), and exits with the command's code (124: timed out). Its own failures have their own codes: 2 usage, 75 `--fail-fast` and no host has room (retry later), 125 `run` itself failed (API, network, create, upload or cleanup), 130 interrupted; with `--json` they print the `{"error": {...}}` object, except a failed cleanup delete: the result then has `deleted: false` and `cleanup: {"error": {...}}` (stdout is always one JSON document). One argument is a shell string, several an exact argv. The same 10-minute limit as `exec` applies. `--push .` first uploads the current directory's files (those git does not ignore) into the working directory (`--cwd`, default HOME), so `instabox run --push . -- 'go test ./...'` tests your checkout. `--name N` is used as is (1-63 lowercase letters, digits or `-`, starting with a letter or digit; default `run-<8 hex digits>`). A box left behind by a killed CLI is deleted by the server at its `deleteAt`, 5 minutes after its timeout (10 with `--push`, plus another timeout with `--setup-file`); a cleanup delete that gets a 5xx, a retryable error or no answer is retried 5 times with backoff. `--setup-file PATH|-` runs a setup script (at most 64 KB) first, in HOME with the same `--timeout` and `-e` variables (after `--push`); if it fails, `run` exits with its code without running the command. `--keep` keeps the box with no deadline and, once it was created, prints `Kept NAME; delete it with: instabox rm --yes NAME` to stderr (stdout stays the command's; `--json` has it as `sandbox`); a failed create operation prints only its error (one whose wait was cut short is kept, with `Kept NAME, whose create had not finished; …`).
105
105
  - `instabox ps work [--all] [--json]` lists the processes running in the box (the server runs `ps` through exec, so it wakes a box that paused itself). Kernel threads and the listing's own processes (its shell, `ps`, `head` and the sshd sessions exec uses) are left out unless `--all`. `--json` prints an array of `{pid, ppid, user, cpuPercent, memPercent, elapsedSeconds, command}`: `instabox ps work --json | jq '.[] | select(.command | test("node"))'`. A stopped or manually paused box shows the list the server read just before it stopped or paused (a stderr note says when it is from), so you can see what was running when a box went down; a box that was never listed while running says so and asks you to start it.
106
106
  - `instabox history work [--limit N] [--json]` lists the commands run in the box through `exec` (by anyone: the CLI, the API, other agents; not SSH sessions), newest first, with ID, start time, duration and exit code, also while the box is stopped. The server keeps the newest 200 with the first 64 KiB of each output stream. `instabox output work [ex_<id>]` prints a past command's stored stdout and stderr (the last command's by default) and exits with its exit code, as `exec` did; `--json` gives `{id, command, cwd, startedAt, durationMs, status, exitCode, stdout, stderr, ...}`. Use them to find out what an earlier session or another agent ran in a box and what it printed, instead of rerunning it. The `jobs` polls and `ps` are not recorded; `exec --background` is recorded as `exec --background: <cmd>` (its output is in `jobs logs`).