current-cli 0.1.20__tar.gz → 0.1.22__tar.gz

{current_cli-0.1.20 → current_cli-0.1.22}/.gitignore

@@ -21,3 +21,6 @@ uv.lock
 # Node
 node_modules/
 dist/
+
+# Storybook build output
+storybook-static/

{current_cli-0.1.20 → current_cli-0.1.22}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: current-cli
-Version: 0.1.20
+Version: 0.1.22
 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.20 → current_cli-0.1.22}/current_cli/schema.yml

@@ -586,6 +586,100 @@ paths:
                 items:
                   $ref: '#/components/schemas/ProviderInfo'
           description: ''
+  /api/integrations/messaging/react/:
+    post:
+      operationId: integrations_messaging_react
+      description: Add an emoji reaction to the message a reply_ref points at.
+      tags:
+      - integrations
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/MessagingReactRequestRequest'
+          application/x-www-form-urlencoded:
+            schema:
+              $ref: '#/components/schemas/MessagingReactRequestRequest'
+          multipart/form-data:
+            schema:
+              $ref: '#/components/schemas/MessagingReactRequestRequest'
+        required: true
+      security:
+      - tokenAuth: []
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/MessagingOk'
+          description: ''
+  /api/integrations/messaging/respond/:
+    post:
+      operationId: integrations_messaging_respond
+      description: Send a text reply into the conversation a reply_ref points at.
+      tags:
+      - integrations
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/MessagingRespondRequestRequest'
+          application/x-www-form-urlencoded:
+            schema:
+              $ref: '#/components/schemas/MessagingRespondRequestRequest'
+          multipart/form-data:
+            schema:
+              $ref: '#/components/schemas/MessagingRespondRequestRequest'
+        required: true
+      security:
+      - tokenAuth: []
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/MessagingOk'
+          description: ''
+  /api/integrations/messaging/stream/:
+    post:
+      operationId: integrations_messaging_stream
+      description: |-
+        Live progress UI for a sandbox agent run; the final reply is NOT part
+        of it — the agent posts that as a normal message through the respond
+        endpoint afterwards.
+
+        Slack: ``start`` opens a "thinking steps" streaming message in the
+        thread (plan mode: task cards grouped under one card), ``append``
+        streams task_update/plan_update chunks into it, ``stop`` settles it.
+
+        Teams: ``start`` sends one Adaptive Card (compact status header plus a
+        toggleable activity section) and returns its activity id as ``ts``;
+        ``append``/``stop`` replace the card in full, rebuilt from the chunks —
+        the sandbox always sends its complete state, so the relay stays
+        stateless.
+      tags:
+      - integrations
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/MessagingStreamRequestRequest'
+          application/x-www-form-urlencoded:
+            schema:
+              $ref: '#/components/schemas/MessagingStreamRequestRequest'
+          multipart/form-data:
+            schema:
+              $ref: '#/components/schemas/MessagingStreamRequestRequest'
+        required: true
+      security:
+      - tokenAuth: []
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/MessagingStreamResponse'
+          description: ''
   /api/integrations/teams/app-package/:
     get:
       operationId: integrations_teams_app_package
@@ -1568,7 +1662,13 @@ paths:
       description: |-
         Upsert a rendered workflow definition into a workspace and seed its
         record types (from the definition's ``emits[]`` plus the built-ins).
-        Existing workspace schemas are never overwritten.
+
+        A definition owns the schemas of the types it declares, so re-applying
+        updates them: the schema lives in the workflow repo and evolves with
+        the steps that stage the records, and a workspace pinned to the schema
+        of the *first* apply 422s every staged record the moment the two
+        drift (a renamed required property is enough). Built-in types and
+        emits that carry no schema never overwrite anything.
       tags:
       - workflows
       requestBody:
@@ -2611,6 +2711,16 @@ components:
       - role
       - workspace_id
       - workspace_name
+    ActionEnum:
+      enum:
+      - start
+      - append
+      - stop
+      type: string
+      description: |-
+        * `start` - start
+        * `append` - append
+        * `stop` - stop
     ApiUserConnectRequestRequest:
       type: object
       description: |-
@@ -2914,6 +3024,16 @@ components:
           format: uuid
       required:
       - workspace
+    EmojiEnum:
+      enum:
+      - eyes
+      - heart
+      - thumbsup
+      type: string
+      description: |-
+        * `eyes` - eyes
+        * `heart` - heart
+        * `thumbsup` - thumbsup
     ErrorDetail:
       type: object
       properties:
@@ -3213,6 +3333,66 @@ components:
       - role
       - workspace_id
       - workspace_name
+    MessagingOk:
+      type: object
+      properties:
+        ok:
+          type: boolean
+      required:
+      - ok
+    MessagingReactRequestRequest:
+      type: object
+      properties:
+        workspace:
+          type: string
+          format: uuid
+        reply_ref: {}
+        emoji:
+          $ref: '#/components/schemas/EmojiEnum'
+      required:
+      - emoji
+      - reply_ref
+      - workspace
+    MessagingRespondRequestRequest:
+      type: object
+      properties:
+        workspace:
+          type: string
+          format: uuid
+        reply_ref: {}
+        text:
+          type: string
+          minLength: 1
+      required:
+      - reply_ref
+      - text
+      - workspace
+    MessagingStreamRequestRequest:
+      type: object
+      properties:
+        workspace:
+          type: string
+          format: uuid
+        reply_ref: {}
+        action:
+          $ref: '#/components/schemas/ActionEnum'
+        ts:
+          type: string
+        chunks: {}
+      required:
+      - action
+      - reply_ref
+      - workspace
+    MessagingStreamResponse:
+      type: object
+      properties:
+        ok:
+          type: boolean
+        ts:
+          type: string
+      required:
+      - ok
+      - ts
     Observation:
       type: object
       description: |-

{current_cli-0.1.20 → current_cli-0.1.22}/llms.txt

@@ -233,6 +233,45 @@ powers the approval-routing FYI picker.
 
 GET /api/integrations/connections/{id}/teams-conversations/
 
+### current integrations messaging react post
+
+Add an emoji reaction to the message a reply_ref points at.
+
+POST /api/integrations/messaging/react/
+
+Options:
+- `--data` (required) - Request body as JSON: inline, @file.json, or - for stdin.
+
+### current integrations messaging respond post
+
+Send a text reply into the conversation a reply_ref points at.
+
+POST /api/integrations/messaging/respond/
+
+Options:
+- `--data` (required) - Request body as JSON: inline, @file.json, or - for stdin.
+
+### current integrations messaging stream post
+
+Live progress UI for a sandbox agent run; the final reply is NOT part
+of it — the agent posts that as a normal message through the respond
+endpoint afterwards.
+
+Slack: ``start`` opens a "thinking steps" streaming message in the
+thread (plan mode: task cards grouped under one card), ``append``
+streams task_update/plan_update chunks into it, ``stop`` settles it.
+
+Teams: ``start`` sends one Adaptive Card (compact status header plus a
+toggleable activity section) and returns its activity id as ``ts``;
+``append``/``stop`` replace the card in full, rebuilt from the chunks —
+the sandbox always sends its complete state, so the relay stays
+stateless.
+
+POST /api/integrations/messaging/stream/
+
+Options:
+- `--data` (required) - Request body as JSON: inline, @file.json, or - for stdin.
+
 ### current integrations teams app-package get
 
 Download the Teams app package (manifest + icons) as a zip.
@@ -535,7 +574,13 @@ Options:
 
 Upsert a rendered workflow definition into a workspace and seed its
 record types (from the definition's ``emits[]`` plus the built-ins).
-Existing workspace schemas are never overwritten.
+
+A definition owns the schemas of the types it declares, so re-applying
+updates them: the schema lives in the workflow repo and evolves with
+the steps that stage the records, and a workspace pinned to the schema
+of the *first* apply 422s every staged record the moment the two
+drift (a renamed required property is enough). Built-in types and
+emits that carry no schema never overwrite anything.
 
 POST /api/workflows/definitions/apply/
 

{current_cli-0.1.20 → current_cli-0.1.22}/pyproject.toml

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