instabox 0.8.21 → 0.8.23

package/cli/SHA256SUMS

@@ -1,6 +1,6 @@
-f0091476b08faafa410324a5a5e055ae3fed7ff95837365adfcd95b27848fd2d  instabox-darwin-amd64
-0cff50ccffadcbb44ef498fd829039976022e95b8ccfd7ab5162a03289459812  instabox-darwin-arm64
-6152f12555fece24c7e6baf9a7788eb9273a3be867d539e337ea3b73191f7175  instabox-linux-amd64
-7c1cc65e31e590ea54052479ab0152523bfed96ed9f0a3cfb13ef9b7b66c035a  instabox-linux-arm64
-5374d5d3f5c976955daf20234d190e0844cab37ab4658ea1517f382c862206ac  instabox-windows-amd64.exe
-b41b0b5d17fca6c920a86211c67096038893cf69d98a03bcd05ccdff7d521617  instabox-windows-arm64.exe
+90475b7b160f14cabbc5dd7c9c9360b0750bd5aec80db94c0941d9893a739a7a  instabox-darwin-amd64
+137dc924f5b5948d8d49b1f57a40fe4121e27da92d0595878fabdf883d1a2bce  instabox-darwin-arm64
+fd83d22c13a25fad71f9eb3d77a42cc62b1454634b5382fbf3bfb702bca00b9b  instabox-linux-amd64
+76d6c0211ecb5f842caa85b68c3ad9016adb1def11ea348eaeadc491fdc9aff1  instabox-linux-arm64
+c709e35b903ffd8165c6cfc1389b09aa2b00b58d3b76984ec94843160178eec1  instabox-windows-amd64.exe
+9ff61641e8275a14a5aeba41c3498a0304741fe0e6a7b93da33b30df36404803  instabox-windows-arm64.exe

package/package.json

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