current-cli 0.1.30__tar.gz → 0.1.31__tar.gz

{current_cli-0.1.30 → current_cli-0.1.31}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: current-cli
-Version: 0.1.30
+Version: 0.1.31
 Summary: Command line interface for the Current API, generated from its OpenAPI schema at runtime
 Author-email: Orin <your-email@example.com>
 License-Expression: MIT

{current_cli-0.1.30 → current_cli-0.1.31}/current_cli/schema.yml

@@ -1080,15 +1080,8 @@ paths:
     post:
       operationId: integrations_messaging_respond
       description: |-
-        Send the agent's reply into the conversation a reply_ref points at,
-        with any workspace files it chose to attach.
-
-        Slack shares the files and the text as one message (the text becomes
-        the upload's ``initial_comment``). Teams cannot: a bot there has to
-        offer each file through a FileConsentCard the recipient accepts, and
-        only in a 1:1 chat, so the text posts first and each file follows as
-        its own offer. Email is the easy one — attachments are what it is for,
-        and they ride along on the reply.
+        Relay the agent's reply, and any workspace files it chose to attach,
+        into the conversation the message came from — see :func:`send_reply`.
       tags:
       - integrations
       requestBody:
@@ -4138,6 +4131,11 @@ components:
             type: string
             minLength: 1
             maxLength: 1024
+        about_runs:
+          type: array
+          items:
+            type: string
+            format: uuid
       required:
       - reply_ref
       - text

{current_cli-0.1.30 → current_cli-0.1.31}/llms.txt

@@ -409,15 +409,8 @@ Options:
 
 ### current integrations messaging respond post
 
-Send the agent's reply into the conversation a reply_ref points at,
-with any workspace files it chose to attach.
-
-Slack shares the files and the text as one message (the text becomes
-the upload's ``initial_comment``). Teams cannot: a bot there has to
-offer each file through a FileConsentCard the recipient accepts, and
-only in a 1:1 chat, so the text posts first and each file follows as
-its own offer. Email is the easy one — attachments are what it is for,
-and they ride along on the reply.
+Relay the agent's reply, and any workspace files it chose to attach,
+into the conversation the message came from — see :func:`send_reply`.
 
 POST /api/integrations/messaging/respond/
 

{current_cli-0.1.30 → current_cli-0.1.31}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "current-cli"
-version = "0.1.30"
+version = "0.1.31"
 description = "Command line interface for the Current API, generated from its OpenAPI schema at runtime"
 readme = "README.md"
 requires-python = ">=3.10"