@creatornader/agent-bridge 0.6.5 → 0.7.0

package/docs/architecture-v2.md

@@ -355,8 +355,12 @@ Managed-client repair, update, and uninstall use a local crash-safe substrate. S
 owner-private metadata is the mutation authority. Runtime plus stable instance locate
 the metadata, and identity must match both the record and the immutable repair or
 update request. Uninstall also binds the identity. Repair restores its launch contract. Update validates a new launch
-before it creates the journal and stores only the identity, normalized command,
-arguments, scope, and fixed Agent Bridge environment key names.
+before it creates the journal. Managed metadata version 2 adds a versioned target
+union. A target is either stdio with a normalized command, arguments, and scope, or
+Streamable HTTP with a normalized URL and scope. Version 1 stdio metadata stays
+readable and becomes version 2 on the next update. The launch projection remains in
+version 2 so bounded registration proofs and v4 rollback records keep their released
+shape.
 Caller backend, scope, and host-config flags are rejected. Owner-private revisioned
 manifests live under
 `~/.agent-bridge/operations/<uuid>` with private snapshots and an exclusive lock keyed
@@ -395,7 +399,15 @@ and change metadata last when the launch changes. A native update command is one
 executable contract. Bare commands cannot contain argument separators, while absolute
 paths must resolve to executable files before an update is journaled. Codex runs get,
 remove, and add with the recorded profile home over the supplied environment. Claude
-Code uses its recorded scope, working directory, and supplied environment. Claude
+Code uses its recorded scope, working directory, and supplied environment. Codex and
+Claude Code may instead use a managed Streamable HTTP target. That target must be an
+explicit loopback HTTP URL with a port and `/mcp` path, without user information,
+query, fragment, bearer-token setting, or custom header. Backend credentials remain in
+their existing private file and do not enter the native HTTP registration.
+
+Claude Desktop represents an endpoint-backed target as an exact stdio proxy launch.
+The proxy command must be an existing absolute executable. Its bounded arguments must
+contain the exact loopback endpoint and no credential-like flags or values. Claude
 Desktop reads its recorded config without following links or link ancestors, replaces
 only `mcpServers.agent-bridge`, writes through an operation-scoped private temporary
 file, and verifies the published entry. Node cannot make that update atomic with an

package/docs/troubleshooting.md

@@ -46,6 +46,34 @@ The registered environment must contain distinct `AGENT_BRIDGE_AGENT`,
 `AGENT_BRIDGE_INSTANCE`, and `AGENT_BRIDGE_CONFIG` values for that client. Do not copy
 another client's identity or backend file into the entry.
 
+## Move a managed client to a local MCP HTTP host
+
+Preview the update first. Add `--apply` only after the plan names the expected
+registration and metadata steps:
+
+```bash
+agent-bridge clients update codex --identity codex --instance <stable-key> \
+  --mcp-url http://127.0.0.1:8794/mcp
+agent-bridge clients update claude-code --identity claude-code --instance <stable-key> \
+  --mcp-url http://127.0.0.1:8793/mcp
+```
+
+Claude Desktop needs a stdio proxy because its managed entry remains a process launch:
+
+```bash
+agent-bridge clients update claude-desktop \
+  --identity claude-desktop --instance <stable-key> \
+  --mcp-url http://127.0.0.1:8791/mcp \
+  --proxy-command /absolute/path/to/node \
+  --proxy-args-json '["/absolute/path/to/stdio-http-proxy.js","--transport","stdio-http-proxy","--endpoint","http://127.0.0.1:8791/mcp"]'
+```
+
+The endpoint must use plain HTTP on `127.0.0.1`, `localhost`, or `::1`, include an
+explicit port, and end at `/mcp`. User information, query strings, and fragments are
+rejected. The update does not delete or rewrite the private backend file. A failed
+update can resume from its operation UUID, and a committed update can be reversed with
+`clients rollback`.
+
 ## The executable is missing
 
 Install the published package globally, then repeat the normal client installation:

package/llms.txt

@@ -48,7 +48,7 @@ services can call the CLI or HTTPS API or embed the Node library without a host
 - agent-bridge clients inspect <runtime> --identity <principal> --instance <stable-key> --backend-config <absolute path>
 - agent-bridge clients adopt <runtime> --identity <principal> --instance <stable-key> --backend-config <absolute path> [--apply]
 - agent-bridge clients repair <runtime> --identity <principal> --instance <stable-key> [--apply] [--resume <uuid>] [--recover-lock]
-- agent-bridge clients update <runtime> --identity <principal> --instance <stable-key> [--command <command>] [--apply] [--resume <uuid>] [--recover-lock]
+- agent-bridge clients update <runtime> --identity <principal> --instance <stable-key> [--command <command> | --mcp-url <loopback-url>] [--proxy-command <command> --proxy-args-json <json-array>] [--apply] [--resume <uuid>] [--recover-lock]
 - agent-bridge clients uninstall <runtime> --identity <principal> --instance <stable-key> [--apply] [--resume <uuid>] [--recover-lock]
 - agent-bridge clients rollback <update-operation-id> --identity <principal> [--apply] [--recover-lock]
 - agent-bridge clients migrate stage <runtime> --identity <principal> --instance <stable-key> --enrollment-file <private-path> [--apply] [--recover-lock]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@creatornader/agent-bridge",
-  "version": "0.6.5",
+  "version": "0.7.0",
   "description": "Let AI agents message each other and hand off work across tools, sessions, and machines.",
   "type": "module",
   "license": "Apache-2.0",