instabox 0.8.80 → 0.8.82
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 +6 -6
- package/cli/instabox-darwin-amd64 +0 -0
- package/cli/instabox-darwin-arm64 +0 -0
- package/cli/instabox-linux-amd64 +0 -0
- package/cli/instabox-linux-arm64 +0 -0
- package/cli/instabox-windows-amd64.exe +0 -0
- package/cli/instabox-windows-arm64.exe +0 -0
- package/package.json +1 -1
- package/skills/instabox/SKILL.md +9 -4
package/cli/SHA256SUMS
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
1
|
+
e4af72892340675d06c7924ec116660890d073b3fba55faf2d13aab75bd18623 instabox-darwin-amd64
|
|
2
|
+
1c35e59478a5b686847c2ff47f3c4dc7b73ca21047777aee8e30ebcde3cde136 instabox-darwin-arm64
|
|
3
|
+
93fe9d18da94077984a6fa653565cd12bb4b6e788ebb8bad938520a0f3b2fa1a instabox-linux-amd64
|
|
4
|
+
b33b52b1613e061e140d4d450ef586222599f5cb08d8294ed1dcf567e959e5ec instabox-linux-arm64
|
|
5
|
+
6031b7260b72d6d787e6efd18ce7812eca92bda2ff7dca25898c38bbcb041873 instabox-windows-amd64.exe
|
|
6
|
+
8493f505d0c52d73788eaa58cbdd18efa0c8fa80c7d95cf5782a05a8c4db5a35 instabox-windows-arm64.exe
|
|
Binary file
|
|
Binary file
|
package/cli/instabox-linux-amd64
CHANGED
|
Binary file
|
package/cli/instabox-linux-arm64
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|
package/package.json
CHANGED
package/skills/instabox/SKILL.md
CHANGED
|
@@ -26,9 +26,9 @@ With no key and nobody at the keyboard, sign up by yourself: `instabox login --a
|
|
|
26
26
|
|
|
27
27
|
## Templates
|
|
28
28
|
|
|
29
|
-
`agent-browser` is the default, so `create` needs no `--template` for ordinary work. It is Debian 13 (trixie, amd64, kernel 6.18.54) with git, gh, Node.js 22 (npm, pnpm, Yarn), Bun, Python 3.13 (`python3 -m venv`, pip, uv), Go, Rust, a C toolchain, Docker, Claude Code and
|
|
29
|
+
`agent-browser` is the default, so `create` needs no `--template` for ordinary work. It is Debian 13 (trixie, amd64, kernel 6.18.54) with git, gh, Node.js 22 (npm, pnpm, Yarn), Bun, Python 3.13 (`python3 -m venv`, pip, uv), Go, Rust, a C toolchain, Docker, Claude Code, Codex and OpenCode, plus a desktop (VNC, Chromium) ready for browsing or driving a GUI from the start, on a 16 GiB root disk and a 20 GiB persistent disk at `/data`. The dashboard shows it as **standard**. Pick another template only for its one purpose:
|
|
30
30
|
|
|
31
|
-
- `herdr`: for the herdr client. The dev tools (gh, Node.js 22, Python 3.13 with venv and pip, Claude Code, Codex, the desktop) without Docker, uv, Go, Rust or a C toolchain; an 8 GiB root disk.
|
|
31
|
+
- `herdr`: for the herdr client. The dev tools (gh, Node.js 22, Python 3.13 with venv and pip, Claude Code, Codex, OpenCode, the desktop) without Docker, uv, Go, Rust or a C toolchain; an 8 GiB root disk.
|
|
32
32
|
- `orca`: for Orca desktop and mobile. The same tools as `herdr` plus the Orca runtime instead of herdr; an 8 GiB root disk.
|
|
33
33
|
- `t3`: for the T3 Code desktop and mobile clients. `agent-browser`'s tools without the preinstalled desktop (it installs itself the first time it is used), plus the T3 Code server (port 3774); a 16 GiB root disk.
|
|
34
34
|
|
|
@@ -162,12 +162,17 @@ Every `webhooks` subcommand takes `--json` (or `-o json`).
|
|
|
162
162
|
When the user asks to run their CI on instabox, set up `runs-on: instabox-medium` in their repo, end to end. Each job then runs on a fresh Ubuntu 24.04 box (like `ubuntu-latest`) that is deleted when the job ends.
|
|
163
163
|
|
|
164
164
|
1. Get OWNER/REPO: `gh repo view --json owner,name,visibility --jq '.owner.login+"/"+.name+" "+.visibility'`. If it's public, tell the user that pull requests from forks will run on their workspace too, on their plan, and that GitHub's **Require approval for all external contributors** (the repository's **Settings** > **Actions** > **General**) makes each one wait for their approval. Then run `instabox ci` (with `--org ORG` for a workspace): if it says GitHub Actions jobs aren't open on this account yet, use the CLI way below instead.
|
|
165
|
-
2. Pick the workspace that runs and pays for the jobs: when `instabox workspace ls` lists more than one, ask the user which. Send them the App link with its ID, https://dashboard.instabox.sh/auth/github-app/install?org=ORG_ID (without `?org=` the page asks which workspace when they are in more than one). Linking takes an owner or admin of that workspace.
|
|
165
|
+
2. Pick the workspace that runs and pays for the jobs: when `instabox workspace ls` lists more than one, ask the user which. Send them the App link with its ID, https://dashboard.instabox.sh/auth/github-app/install?org=ORG_ID (without `?org=` the page asks which workspace when they are in more than one). Linking takes an owner or admin of that workspace. The link has them confirm their GitHub account, then lists the GitHub accounts with the App: ask them to click **Link** next to OWNER (when OWNER is not listed, **Install on another GitHub account**, install it on OWNER and give it access to REPO), and wait until they say it's done. The page it ends on names the workspace it linked. If it says "your personal workspace" and they meant another, see the end of this section. You can't do this step for them.
|
|
166
166
|
3. Change `runs-on:` of the jobs to move to `instabox-medium` (4 vCPU / 8 GiB), or `instabox-small` (2 / 4) or `instabox-large` (8 / 16) where the plan has them (the free plan runs `instabox-medium` only; any other `instabox` label, `instabox` alone included, is refused). Leave the steps alone; the jobs' secrets stay GitHub Actions secrets, as the box gets none of the user's instabox secrets.
|
|
167
167
|
4. Show the user the diff and push only with their OK.
|
|
168
168
|
5. Check the first run: `gh run watch`, and `instabox ci` (with `--org ORG` for a workspace) shows each job's state and why it waits or was refused. When nothing is linked, `instabox ci` says so and prints the App install link to send. A job that stays queued on GitHub with nothing in `instabox ci` means the App has no access to REPO; go back to step 2.
|
|
169
169
|
|
|
170
|
-
|
|
170
|
+
A GitHub account runs CI for one workspace at a time. To move OWNER to another workspace, an owner or admin unlinks it (**Unlink** in the account menu of the dashboard's CI page), then links it from the App link of the other workspace. One linked to the user's personal workspace links straight to another workspace they manage, after a confirmation. The App stays installed on GitHub through all this.
|
|
171
|
+
|
|
172
|
+
When linking does not work:
|
|
173
|
+
- The user cannot link a workspace, or `instabox ci` says only an owner or admin links the App: they are a member there. Ask an owner or admin (`instabox workspace members WS` lists them) to link it, or to make the user an admin.
|
|
174
|
+
- OWNER shows **Already used for CI**: its CI runs in another workspace. With **Open**, the user is in that workspace and unlinks it there first. Without it, they are not: ask whoever set up CI for OWNER to invite them, or to unlink it.
|
|
175
|
+
- OWNER is not listed: the App is not installed on it, or their GitHub account cannot see it. **Install on another GitHub account** installs it.
|
|
171
176
|
|
|
172
177
|
For another CI, or a job that must stay on GitHub's runner, a step runs one command in a box with the CLI, with INSTABOX_API_KEY from a CI secret:
|
|
173
178
|
|