@m64/nats-pi-bridge 0.0.2 → 0.0.3

package/README.md

@@ -93,10 +93,63 @@ Each session is its own NATS microservice instance (the same pattern that `nats-
 ```
 nats micro list
 → pi-exec │ 0.0.1 │ ABC123 │ intake
-         │       │ DEF456 │ worker-1 — /home/mario/code/nats-zig
-         │       │ GHI789 │ sid-gpt — /home/mario/code/sid-gpt
+          │       │ DEF456 │ worker-1 — /home/mario/code/nats-zig
+          │       │ GHI789 │ sid-gpt — /home/mario/code/sid-gpt
 ```
 
+## NATS server
+
+The Quick Start uses `demo.nats.io` because it's zero-setup, but you'll usually want your own server. The bridge picks the server from a [NATS CLI context](https://docs.nats.io/using-nats/nats-tools/nats_cli#contexts) named via the `NATS_CONTEXT` environment variable.
+
+### Localhost
+
+```bash
+# 1. One-time: create a context pointing at your local NATS
+nats context save local --server nats://localhost:4222
+
+# 2. Run the bridge against it
+NATS_CONTEXT=local npx @m64/nats-pi-bridge
+```
+
+```
+pi-exec: connecting to nats://localhost:4222 (context: local)
+pi-exec: connected
+pi-exec: intake registered on agents.pi-exec.m64
+```
+
+> **Don't have a local NATS server yet?** The fastest way:
+>
+> ```bash
+> docker run --rm -p 4222:4222 nats:latest
+> ```
+>
+> Or grab a binary from the [nats-server releases](https://github.com/nats-io/nats-server/releases).
+
+### Make a context the default
+
+To avoid setting `NATS_CONTEXT` on every invocation, drop a one-line config file:
+
+```bash
+mkdir -p ~/.pi-exec
+echo '{"context":"local"}' > ~/.pi-exec/config.json
+```
+
+After that, plain `npx @m64/nats-pi-bridge` connects to your chosen server.
+
+### Authenticated and remote servers
+
+The same context format works for any NATS auth scheme — credentials files, NKeys, JWTs, TLS, user/password. Anything `nats context save` can store, the bridge can use:
+
+```bash
+nats context save prod \
+  --server nats://nats.example.com:4222 \
+  --creds ~/.nkeys/creds/synadia/MyAccount/me.creds
+
+NATS_CONTEXT=prod npx @m64/nats-pi-bridge
+```
+
+Context files live at `~/.config/nats/context/<name>.json`. See the [NATS CLI context docs](https://docs.nats.io/using-nats/nats-tools/nats_cli#contexts) for the full list of supported fields.
+
 ## Install
 
 ```bash
@@ -149,7 +202,7 @@ Environment overrides:
 | `PI_EXEC_DEFAULT_MODEL` | Default model spec, e.g. `anthropic/claude-sonnet-4-5` |
 | `PI_EXEC_DEFAULT_MAX_LIFETIME` | Default max session lifetime in seconds |
 
-PI credentials are read from `~/.pi/agent/auth.json` (the standard PI agent location). Run `pi /login` interactively once to populate it.
+PI credentials are read from `~/.pi/agent/auth.json` (the standard PI agent location). Create the file directly — see the [Quick Start prerequisite](#quick-start) for the one-liner. If you have PI installed locally, `pi /login` populates it automatically.
 
 ## Intake protocol
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@m64/nats-pi-bridge",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "description": "Standalone headless service that spawns and manages PI coding agent sessions on demand via NATS. Control plane / data plane split, streaming wire protocol, multi-session microservice registration.",
   "author": "m64",
   "license": "Apache-2.0",