@skilder-ai/runtime 0.9.23 → 0.9.25

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
@@ -45,7 +45,9 @@ When `REMOTE_PORT` is set, the runtime exposes `GET /health`:
45
45
  - **`200 { status: 'ok' }`** — NATS connected, an active round-trip probe (`flush`, 2s timeout) succeeded, and the runtime is authenticated
46
46
  - **`503 { status: 'error', message: '...' }`** — NATS disconnected, NATS unreachable (flush timed out), not authenticated, or an unexpected error occurred
47
47
 
48
- > **Note:** The health endpoint is only available when `REMOTE_PORT` is set. CLI/standalone mode (no `REMOTE_PORT`) does not start an HTTP server this is intentional.
48
+ Health is independent of the remote MCP endpoints: a runtime that serves no MCP endpoint (no `MCP_REMOTE_ENABLED`) is still healthcheckable. The container image defaults `REMOTE_PORT` to `3001`, so every runtime container has a working healthcheck out of the box.
49
+
50
+ > **Note:** `npx`-installed runtimes bind no port unless you set `REMOTE_PORT` yourself, and stdio mode (`USER_KEY`) never starts an HTTP server — it is spawned per client, so a shared port would collide.
49
51
 
50
52
  ### Docker Compose setup
51
53
 
@@ -54,7 +56,8 @@ services:
54
56
  runtime:
55
57
  image: your-runtime-image
56
58
  environment:
57
- REMOTE_PORT: "3001"
59
+ REMOTE_PORT: "3001" # web service (health); the image defaults this
60
+ MCP_REMOTE_ENABLED: "true" # also serve the remote MCP endpoints on it
58
61
  RUNTIME_KEY: "<RUNTIME_API_KEY>"
59
62
  NATS_SERVERS: "nats:4222"
60
63
  healthcheck: