@securecoms/agent-bridge 0.31.0 → 0.33.0

package/README.md

@@ -767,6 +767,38 @@ including its key). Each proxied call is metered server-side
 `fast_voice_tokens_in`, `fast_voice_tokens_out`), capped at
 `VOICE_FAST_CALLS_PER_MINUTE` (default 60) per agent.
 
+### Calling your own provider directly (`route: "direct"`)
+
+To keep the fast-path call off the SecureComs proxy entirely, add
+`"route": "direct"` to the credential file's `fast_path` block:
+
+```json
+"fast_path": { "enabled": true, "route": "direct", "base_url": "https://api.openai.com/v1",
+               "model": "gpt-4o-mini", "api_key_env": "SECURECOMS_VOICE_LLM_KEY" }
+```
+
+- With `route: "direct"` the daemon calls `base_url` with the file's own
+  `api_key`/`api_key_env`, and never calls `POST /api/v1/voice/fast-complete`,
+  even when the settings fetch succeeds. The backend voice settings (persona,
+  dials, voice, pace) still apply; only the fast-path provider and key come from
+  the file. A later `voice_settings_changed` refetch keeps the direct route.
+- Opt-in lives only in this file. There is no web or backend setting for it,
+  and only the exact value `"direct"` counts: a block without `route` (or with
+  any other value) behaves as described above, so an old `fast_path` block does
+  not switch to direct on upgrade.
+- If the direct provider fails (timeout, HTTP error, bad response), nothing is
+  spoken by the fast path and your full agent answers the turn. The daemon never
+  retries through the SecureComs proxy.
+- `route: "direct"` without a resolvable key is a configuration error: the
+  daemon logs `voice.fast_path_direct_no_key` once at start and runs with no
+  fast path (full agent only). It does not fall back to the proxy.
+- The prompt sent to your provider is the same call-scoped prompt the proxy
+  would get: the call's own spoken turns only, no typed chat, notes or memory.
+  The `x-securecoms-bridge-caps` header is never sent to your provider.
+- Call summaries use the same client: with `route: "direct"` they are also
+  generated by your provider, never the SecureComs proxy. With no usable key,
+  call summaries are unavailable (as is the fast path).
+
 ---
 
 ## Unified memory (0.29.0)
@@ -931,6 +963,32 @@ copied after the owner's next typed message.
 
 ---
 
+## Release notes: 0.33.0
+
+<!-- [COPY, approved by Eric 2026-10-21 ("Bridge approved")] -->
+
+**Ready for a separate call channel**
+
+- The agent can now take part in hosted calls through a separate, hidden call channel that belongs to the conversation. Spoken turns, the agent's spoken replies and the call transcript go to the call channel. Typed messages stay in the conversation.
+- Nothing changes on calls yet. The SecureComs voice service starts to use the call channel in a later update.
+- After this update, the agent tells the SecureComs voice service that it supports the call channel. When the service starts to use it, a call to an agent on an older version will not start, and the app will say the agent needs an update.
+- A message you type in the chat during a call still works as a normal chat message.
+
+Upgrade: `npm install -g @securecoms/agent-bridge@0.33.0`, then restart the agent.
+
+---
+
+## Release notes: 0.32.0
+
+<!-- [COPY, approved by Eric 2026-10-20 ("Notes ok")] -->
+
+- Privacy: the agent no longer sends its memory file, persona file text or old memory text to the SecureComs server. It sends only the persona file names and sizes. The server already removed the text it had stored.
+- Optional: an agent's quick spoken replies on calls can go straight from the agent's machine to the owner's own model provider, using a key in the agent's credential file (`voice.fast_path.route: "direct"`). It is off unless you turn it on; with it on, call summaries also use your provider, and without a usable key they are not available.
+
+Upgrade: `npm install -g @securecoms/agent-bridge@0.32.0`, then restart the agent.
+
+---
+
 ## Release notes: 0.31.0
 
 <!-- [COPY, approved by Eric 2026-10-18 (voice-scope release notes)] -->