instabox 0.8.22 → 0.8.24

package/cli/SHA256SUMS

@@ -1,6 +1,6 @@
-8f99c9a4382112e110f805b1a74b3b9b8b65e38085c7d2e5f1a72108ae8a89e2  instabox-darwin-amd64
-660ee5fc1ce6e4ddd4ac00961e9603d81476ae8e33284996d80aa79f6f787ac8  instabox-darwin-arm64
-c66df74affeaf9806e53c24caa37002a2de9b870d7fa6f6cf9ad174796e41359  instabox-linux-amd64
-de0735c82400cbfda096c2a6a772a92e0d32dbf6d3fde673e09055942f89db0c  instabox-linux-arm64
-bb9c6960262c7aa551d374c330cec7b4604be8135418b7d72cd6186655004378  instabox-windows-amd64.exe
-d2e2185d098b240879b2d61565b17856cb24b27d009b523304a0faf99f1665ff  instabox-windows-arm64.exe
+8ae411b5181e54a5e6ec086d4f10c1a0c202177df0e8fb84753ad61698bdda3d  instabox-darwin-amd64
+97489070195f07d95e6f7011bf664a722258ee3e9e2ac70c274f9891af5bf5ce  instabox-darwin-arm64
+55b611af08b7fe39ee082b071dbaae7694506b32f9b594ae1f96491ae04a9e7f  instabox-linux-amd64
+6c02723dd536761f5ee033350a8a8c9cf4f5e1b1de4c721b296d9f178d0cf5f4  instabox-linux-arm64
+200eb91643f0113f5378d97a854433e86881ee75acf4d0bebc73531d90c569c6  instabox-windows-amd64.exe
+a4dfa90ee748dda1c70deba83ad2077ced513f74c637e94e990117e9cb18b578  instabox-windows-arm64.exe

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instabox",
-  "version": "0.8.22",
+  "version": "0.8.24",
   "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

@@ -104,6 +104,7 @@ instabox rm --yes work                          # delete the box (without --yes
 - Output: `--json` (or `-o json`) works on every command (each command's `-h` lists it); `ssh`, `mosh` and `port-forward` are interactive and refuse it with the JSON error code `json_unsupported` (use `exec --json`). With JSON output a failure prints `{"error":{"code","message",...}}` on stdout instead of text on stderr and still exits non-zero (2 for usage errors, code `usage`); API errors keep the server's `code`, `status` and `requestId`. Piped, the list and status commands (`ls`, `get`, `templates`, `usage`, `snapshot ls`, `port ls`, `keys ls`, `secrets ls`, `vault ls`, `workspace ls|get|members|invites`) print JSON on their own, so `instabox ls | jq` works; `--output table` or `INSTABOX_NO_AUTO_JSON=1` keeps the table. `exec`, `ssh`, `files` and the other commands print the same output piped or not.
 - The box's HOME has `MACHINE.md` (which box it is, its size, what survives a stop, the installed tools) and `AGENTS.md`, a moment after it starts. They are reference for when a task needs a fact about the box, not steps to run first.
 - A public URL for a web server in the box: `instabox port publish work 3000` prints it (`instabox port ls`, `instabox port unpublish work 3000`). The URL works while the box runs.
+- A raw TCP service (Postgres, Redis) reachable from anywhere, where the server enables it: `instabox port publish work 5432 --tcp` prints `5432-<id>.<tcp domain>:443`; clients connect with TLS and that host as SNI (`psql "host=<host> port=443 sslmode=require user=postgres"`). Otherwise, or for a private tunnel, use `instabox port-forward work 5432`.
 - A private tunnel instead, only from your computer: `instabox port-forward work 8080:3000` (alias `forward`; `LOCAL` defaults to `REMOTE`, several ports at once) serves the box's port 3000 at `http://127.0.0.1:8080` over SSH and stays in the foreground until Ctrl-C, so start it in the background (`instabox port-forward work 8080:3000 &`) and kill it when done. It fails at once when the local port is busy.
 
 ## Organization Secrets