@securecoms/agent-bridge 0.30.2 → 0.31.0

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
@@ -931,6 +931,59 @@ copied after the owner's next typed message.
931
931
 
932
932
  ---
933
933
 
934
+ ## Release notes: 0.31.0
935
+
936
+ <!-- [COPY, approved by Eric 2026-10-18 (voice-scope release notes)] -->
937
+
938
+ **Agent calls use only what was said on the call**
939
+
940
+ - When you talk to your agent on a hosted call, its quick spoken replies now use only what was said on that call. They no longer use your typed chat history or saved memory facts.
941
+ - The agent's longer answers on a call follow the same rule. Saved notes and recalled items are not used for spoken turns.
942
+ - A message you type in the chat during a call still works as a normal chat message.
943
+ - On spoken turns, the agent can use only two tools: the current time and web search.
944
+ - After this update, the agent tells the SecureComs voice service that it supports this behavior. Older agent versions will stop getting quick spoken replies once the service starts to require it. They still answer, a little more slowly.
945
+
946
+ Upgrade: `npm install -g @securecoms/agent-bridge@0.31.0`, then restart the agent.
947
+
948
+ ---
949
+
950
+ ## Release notes: 0.30.3
951
+
952
+ <!-- [COPY, approved by Eric 2026-10-17 (search release notes) and 2026-10-16 (held items); adapted to 0.30.3 on 2026-10-18] -->
953
+
954
+ 0.30.3 enforces the owner's signed search provider and daily limit, gates the
955
+ new page reading tool, and keeps older runtimes from using a provider the
956
+ owner did not sign. Install it together with `@securecoms/agent-runtime`
957
+ 0.14.0 and restart both.
958
+
959
+ - **Upgrade the bridge and the runtime together.** An older bridge with a new
960
+ runtime can still use install-time search keys after a search setup
961
+ mismatch.
962
+ - **Signed search settings.** An owner may sign one of five search providers
963
+ (Brave, Tavily, Parallel, Exa, Firecrawl) and a daily search limit from 0 to
964
+ 2000 for the private chat. An older bridge reads a manifest with a new
965
+ provider or a limit as invalid and keeps its last good one.
966
+ - **Read web pages.** `web_extract` is offered in the owner's private chat only
967
+ when every attached runtime supports it. An attached harness connector,
968
+ such as OpenClaw or Hermes, turns it off.
969
+ - **Older runtimes.** On an agent whose owner signed any provider other than
970
+ Brave (Tavily included) and that runs an older runtime, web search is
971
+ withheld everywhere until the runtime is updated. The owner sees "Update the
972
+ agent to use this search provider."
973
+ - **No fallback after a mismatch.** When the server's search setting does not
974
+ match the signed provider and no earlier good setting was saved, the agent
975
+ gets the signed provider with no key file, so a new runtime has no search
976
+ instead of using install-time keys.
977
+ - **Linux reinstall.** Install on Linux now restarts a running service, so the
978
+ new version starts.
979
+ - **Release check.** The publish workflow refuses to publish when the live Node
980
+ 24 checksum list no longer parses.
981
+
982
+ Each runtime restart on an agent with signed tool settings causes one or two
983
+ extra config refreshes. You do not need to change anything after the upgrade.
984
+
985
+ ---
986
+
934
987
  ## Release notes: 0.30.2
935
988
 
936
989
  <!-- [COPY, approved by Eric 2026-10-15] -->