signalwire-sdk 3.7.1.dev129__tar.gz → 3.7.1.dev130__tar.gz

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130}/CHANGELOG.md

@@ -8,8 +8,9 @@
   wraps the platform's reserved `startup_hook` function. A handler receives
   the SWAIG request and may return a `FunctionResult`: its actions run at
   once, and its response text is added to the conversation as a system
-  message the model reads before it speaks. Handlers run in registration
-  order, and an exception is logged, not raised.
+  message the model reads before it speaks, except on an OpenAI Realtime
+  agent, which drops the text. Handlers run in registration order, and an
+  exception is logged, not raised.
 
 ### Documentation
 - How to reject a call from the per-call configuration callback

{signalwire_sdk-3.7.1.dev129/signalwire/signalwire_sdk.egg-info → signalwire_sdk-3.7.1.dev130}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: signalwire-sdk
-Version: 3.7.1.dev129
+Version: 3.7.1.dev130
 Summary: SignalWire SDK for AI voice agents, live call control (RELAY) and REST. Run sw-pydocs for its documentation.
 Author-email: SignalWire Team <info@signalwire.com>
 License: MIT

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130}/docs/agent_guide.md

@@ -2156,7 +2156,7 @@ def save_call(call_log, raw_data):
 An `on_call_start` handler receives the SWAIG request (`call_id`, `global_data`, `caller_id_num` and the rest) and may return a `FunctionResult` or `None`. The platform runs the hook once, after the call is answered and before the AI's first turn, and uses its reply:
 
 - The actions run at once, such as `update_global_data()` to give the call data before the conversation starts. Several handlers' actions run in registration order. `post_process` isn't used.
-- The response text is added to the conversation as a system message, so the model reads it before it speaks. Several handlers' texts are joined, one per line. Only a plain string response is used.
+- The response text is added to the conversation as a system message, so the model reads it before it speaks. Several handlers' texts are joined, one per line. Only a plain string response is used. An OpenAI Realtime agent runs the actions but drops the text, so put what its first greeting needs in the prompt from a per-call configuration callback instead.
 
 The platform waits for the hook before the AI starts, so a slow handler delays the greeting; keep it short (see [Slow tools and the webhook timeout](#slow-tools-and-the-webhook-timeout)).
 
@@ -2283,7 +2283,7 @@ def hangup_hook(self, args, raw_data):
 2. **Error Handling**: Always implement proper error handling in hooks - failures shouldn't crash the voice session
 3. **Timing**: `startup_hook` is called before the AI starts speaking to the caller
 4. **Session Data**: Any data you need to persist across the session should be stored in external storage (Redis, database, etc.)
-5. **Return Values**: Both hooks must return a `FunctionResult` object. The `startup_hook`'s actions run and its response text is added to the conversation as a system message; the `hangup_hook`'s response is unused, since the call is over
+5. **Return Values**: Both hooks must return a `FunctionResult` object. The `startup_hook`'s actions run and its response text is added to the conversation as a system message (except on an OpenAI Realtime agent, which drops the text); the `hangup_hook`'s response is unused, since the call is over
 
 ### SIP Routing
 

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130}/docs/api_reference.md

@@ -1389,7 +1389,7 @@ def on_call_start(
 
 The handler receives `raw_data`, the SWAIG request (`call_id`, `global_data`, `caller_id_num` and the rest), and may return a `FunctionResult` or `None`:
 - Its actions run at once, in registration order across handlers. `post_process` isn't used.
-- Its response text is added to the conversation as a system message the model reads before it speaks. Several handlers' texts are joined, one per line. Only a plain string response is used.
+- Its response text is added to the conversation as a system message the model reads before it speaks. Several handlers' texts are joined, one per line. Only a plain string response is used. An OpenAI Realtime agent runs the actions but drops the text, so put what its first greeting needs in the prompt from a per-call configuration callback instead.
 
 An exception is logged, not raised, and that handler's result is dropped. The platform waits for the hook before the AI starts, so keep the handler short.
 

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "signalwire-sdk"
-version = "3.7.1.dev129"
+version = "3.7.1.dev130"
 description = "SignalWire SDK for AI voice agents, live call control (RELAY) and REST. Run sw-pydocs for its documentation."
 authors = [
     {name = "SignalWire Team", email = "info@signalwire.com"}

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130}/signalwire/signalwire/__init__.py

@@ -59,7 +59,7 @@ if TYPE_CHECKING:
     from signalwire.utils.schema_utils import SchemaValidationError
     from signalwire.web import WebService
 
-__version__ = "3.7.1.dev129"
+__version__ = "3.7.1.dev130"
 
 # §6.2-python (owner decision: NO packaging split — one package, all deps required;
 # IMPORT-TIME behavior only): the agent/web symbols are lazy-imported via module

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130}/signalwire/signalwire/agent_server.py

@@ -68,7 +68,7 @@ class AgentServer:
         self.app = FastAPI(
             title="SignalWire AI Agents",
             description="Hosted SignalWire AI Agents",
-            version="3.7.1.dev129",
+            version="3.7.1.dev130",
             redirect_slashes=False,
             docs_url=None,
             redoc_url=None,

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130}/signalwire/signalwire/core/agent_base.py

@@ -781,10 +781,13 @@ class AgentBase(  # type: ignore[misc]  # intentional diamond: WebMixin's serve/
           the conversation starts);
         - its response text is added to the conversation as a system message
           the model reads before its first turn. The texts of several handlers
-          are joined, one per line. Only a plain string response is used.
+          are joined, one per line. Only a plain string response is used. An
+          OpenAI Realtime agent runs the actions but drops the text, so put
+          what its first greeting needs in the prompt from a per-call
+          configuration callback instead.
         `post_process` is not used: the combined result runs its actions at
-        once. The platform adds every hook reply to the conversation, so a
-        hook whose handlers return no text still adds a short placeholder
+        once. The text pipeline adds every hook reply to the conversation, so
+        a hook whose handlers return no text still adds a short placeholder
         line, as any function with an empty reply does.
 
         Exceptions are caught and logged rather than raised, and that

{signalwire_sdk-3.7.1.dev129 → signalwire_sdk-3.7.1.dev130/signalwire/signalwire_sdk.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: signalwire-sdk
-Version: 3.7.1.dev129
+Version: 3.7.1.dev130
 Summary: SignalWire SDK for AI voice agents, live call control (RELAY) and REST. Run sw-pydocs for its documentation.
 Author-email: SignalWire Team <info@signalwire.com>
 License: MIT