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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: current-cli
-Version: 0.1.29
+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.29 → current_cli-0.1.31}/current_cli/schema.yml

@@ -634,10 +634,10 @@ paths:
               schema:
                 $ref: '#/components/schemas/FileUrlResponse'
           description: ''
-  /api/inbox/inbox/:
+  /api/inboxes/inboxes/:
     get:
-      operationId: inbox_retrieve
-      description: Fetch (and lazily provision) the workspace's forwarding inbox.
+      operationId: inbox_list
+      description: List (and lazily provision) the workspace's inboxes, one per role.
       parameters:
       - in: query
         name: workspace
@@ -646,7 +646,7 @@ paths:
         description: Workspace UUID
         required: true
       tags:
-      - inbox
+      - inboxes
       security:
       - MessagingJobTokenAuth: []
       - tokenAuth: []
@@ -655,8 +655,112 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/WorkspaceInbox'
+                type: array
+                items:
+                  $ref: '#/components/schemas/WorkspaceInbox'
+          description: ''
+  /api/inboxes/inboxes/{inbox_id}/allow-lists/:
+    get:
+      operationId: inbox_allow_lists_retrieve
+      description: |-
+        Inbox-scoped AgentMail receive and send allow lists.
+
+        Every workspace member can inspect the effective entries. Only workspace
+        admins can add or remove entries, matching other integration settings.
+      parameters:
+      - in: path
+        name: inbox_id
+        schema:
+          type: string
+          format: uuid
+        required: true
+      tags:
+      - inboxes
+      security:
+      - MessagingJobTokenAuth: []
+      - tokenAuth: []
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/EmailAllowLists'
           description: ''
+    post:
+      operationId: inbox_allow_lists_create
+      description: |-
+        Inbox-scoped AgentMail receive and send allow lists.
+
+        Every workspace member can inspect the effective entries. Only workspace
+        admins can add or remove entries, matching other integration settings.
+      parameters:
+      - in: path
+        name: inbox_id
+        schema:
+          type: string
+          format: uuid
+        required: true
+      tags:
+      - inboxes
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/EmailAllowListMutationRequest'
+          application/x-www-form-urlencoded:
+            schema:
+              $ref: '#/components/schemas/EmailAllowListMutationRequest'
+          multipart/form-data:
+            schema:
+              $ref: '#/components/schemas/EmailAllowListMutationRequest'
+        required: true
+      security:
+      - MessagingJobTokenAuth: []
+      - tokenAuth: []
+      responses:
+        '201':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/EmailAllowListEntry'
+          description: ''
+    delete:
+      operationId: inbox_allow_lists_destroy
+      description: |-
+        Inbox-scoped AgentMail receive and send allow lists.
+
+        Every workspace member can inspect the effective entries. Only workspace
+        admins can add or remove entries, matching other integration settings.
+      parameters:
+      - in: query
+        name: direction
+        schema:
+          type: string
+          enum:
+          - receive
+          - send
+        description: AgentMail allow-list direction
+        required: true
+      - in: query
+        name: entry
+        schema:
+          type: string
+        description: Email address or domain to remove
+        required: true
+      - in: path
+        name: inbox_id
+        schema:
+          type: string
+          format: uuid
+        required: true
+      tags:
+      - inboxes
+      security:
+      - MessagingJobTokenAuth: []
+      - tokenAuth: []
+      responses:
+        '204':
+          description: No response body
   /api/integrations/connections/:
     get:
       operationId: integrations_connections_list
@@ -943,7 +1047,12 @@ paths:
   /api/integrations/messaging/react/:
     post:
       operationId: integrations_messaging_react
-      description: Add an emoji reaction to the message a reply_ref points at.
+      description: |-
+        Add an emoji reaction to the message a reply_ref points at.
+
+        Email has no reactions and is refused. An email job is not offered the
+        ``react`` tool at all, so reaching here means a caller sent something it
+        should not have.
       tags:
       - integrations
       requestBody:
@@ -971,14 +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.
+        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:
@@ -1053,6 +1156,10 @@ paths:
         ``append``/``stop`` replace the card in full, rebuilt from the chunks —
         the sandbox always sends its complete state, so the relay stays
         stateless.
+
+        Email has no live message to evolve and is refused. An email job builds
+        no reporter, so reaching here means a caller sent something it should
+        not have.
       tags:
       - integrations
       requestBody:
@@ -3423,6 +3530,57 @@ components:
           type: string
       required:
       - detail
+    DirectionEnum:
+      enum:
+      - receive
+      - send
+      type: string
+      description: |-
+        * `receive` - receive
+        * `send` - send
+    EmailAllowListEntry:
+      type: object
+      properties:
+        entry:
+          type: string
+        entry_type:
+          $ref: '#/components/schemas/EntryTypeEnum'
+        read_only:
+          type: boolean
+          default: false
+        created_at:
+          type: string
+          format: date-time
+      required:
+      - created_at
+      - entry
+      - entry_type
+    EmailAllowListMutationRequest:
+      type: object
+      properties:
+        direction:
+          $ref: '#/components/schemas/DirectionEnum'
+        entry:
+          type: string
+          minLength: 1
+          maxLength: 254
+      required:
+      - direction
+      - entry
+    EmailAllowLists:
+      type: object
+      properties:
+        receive:
+          type: array
+          items:
+            $ref: '#/components/schemas/EmailAllowListEntry'
+        send:
+          type: array
+          items:
+            $ref: '#/components/schemas/EmailAllowListEntry'
+      required:
+      - receive
+      - send
     EmojiEnum:
       enum:
       - eyes
@@ -3433,6 +3591,14 @@ components:
         * `eyes` - eyes
         * `heart` - heart
         * `thumbsup` - thumbsup
+    EntryTypeEnum:
+      enum:
+      - email
+      - domain
+      type: string
+      description: |-
+        * `email` - email
+        * `domain` - domain
     ErrorDetail:
       type: object
       properties:
@@ -3646,6 +3812,14 @@ components:
       required:
       - path
       - url
+    InboxRoleEnum:
+      enum:
+      - interaction
+      - ingest
+      type: string
+      description: |-
+        * `interaction` - Interaction
+        * `ingest` - Ingest
     IntegrationConnection:
       type: object
       description: |-
@@ -3957,6 +4131,11 @@ components:
             type: string
             minLength: 1
             maxLength: 1024
+        about_runs:
+          type: array
+          items:
+            type: string
+            format: uuid
       required:
       - reply_ref
       - text
@@ -5538,6 +5717,11 @@ components:
         address:
           type: string
           readOnly: true
+        role:
+          allOf:
+          - $ref: '#/components/schemas/InboxRoleEnum'
+          readOnly: true
+          default: interaction
         created_at:
           type: string
           format: date-time
@@ -5546,6 +5730,7 @@ components:
       - address
       - created_at
       - id
+      - role
       - workspace
     WorkspaceInvite:
       type: object

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

@@ -241,11 +241,45 @@ POST /api/files/upload-url/
 Options:
 - `--data` (required) - Request body as JSON: inline, @file.json, or - for stdin.
 
-### current inbox retrieve
+### current inboxes allow-lists create <inbox_id>
 
-Fetch (and lazily provision) the workspace's forwarding inbox.
+Inbox-scoped AgentMail receive and send allow lists.
 
-GET /api/inbox/inbox/
+Every workspace member can inspect the effective entries. Only workspace
+admins can add or remove entries, matching other integration settings.
+
+POST /api/inboxes/inboxes/{inbox_id}/allow-lists/
+
+Options:
+- `--data` (required) - Request body as JSON: inline, @file.json, or - for stdin.
+
+### current inboxes allow-lists destroy <inbox_id>
+
+Inbox-scoped AgentMail receive and send allow lists.
+
+Every workspace member can inspect the effective entries. Only workspace
+admins can add or remove entries, matching other integration settings.
+
+DELETE /api/inboxes/inboxes/{inbox_id}/allow-lists/
+
+Options:
+- `--direction` - AgentMail allow-list direction
+- `--entry` - Email address or domain to remove
+
+### current inboxes allow-lists retrieve <inbox_id>
+
+Inbox-scoped AgentMail receive and send allow lists.
+
+Every workspace member can inspect the effective entries. Only workspace
+admins can add or remove entries, matching other integration settings.
+
+GET /api/inboxes/inboxes/{inbox_id}/allow-lists/
+
+### current inboxes list
+
+List (and lazily provision) the workspace's inboxes, one per role.
+
+GET /api/inboxes/inboxes/
 
 Options:
 - `--workspace` - Workspace UUID
@@ -364,6 +398,10 @@ Options:
 
 Add an emoji reaction to the message a reply_ref points at.
 
+Email has no reactions and is refused. An email job is not offered the
+``react`` tool at all, so reaching here means a caller sent something it
+should not have.
+
 POST /api/integrations/messaging/react/
 
 Options:
@@ -371,14 +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.
+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/
 
@@ -416,6 +448,10 @@ toggleable activity section) and returns its activity id as ``ts``;
 the sandbox always sends its complete state, so the relay stays
 stateless.
 
+Email has no live message to evolve and is refused. An email job builds
+no reporter, so reaching here means a caller sent something it should
+not have.
+
 POST /api/integrations/messaging/stream/
 
 Options:

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

@@ -1,6 +1,6 @@
 [project]
 name = "current-cli"
-version = "0.1.29"
+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"

{current_cli-0.1.29 → current_cli-0.1.31}/tests/test_command_tree.py

@@ -45,7 +45,7 @@ def test_expected_command_paths(cli):
         ["workspaces", "members", "list"],
         ["workspaces", "invites", "accept", "create"],
         ["integrations", "connections", "channels", "list"],
-        ["inbox", "retrieve"],
+        ["inboxes", "list"],
     ]:
         _resolve(cli, parts)
 

{current_cli-0.1.29 → current_cli-0.1.31}/tests/test_requests.py

@@ -64,7 +64,7 @@ def test_default_workspace_fallback(cli, runner, transport_factory):
     config.set_value("default_workspace", "default-ws")
     transport = transport_factory(ok({}))
 
-    result = runner.invoke(cli, ["inbox", "retrieve"])
+    result = runner.invoke(cli, ["inboxes", "list"])
 
     assert result.exit_code == 0, result.output
     assert transport.requests[0].url.params["workspace"] == "default-ws"
@@ -73,7 +73,7 @@ def test_default_workspace_fallback(cli, runner, transport_factory):
 def test_required_workspace_missing_fails(cli, runner, transport_factory):
     transport = transport_factory(ok({}))
 
-    result = runner.invoke(cli, ["inbox", "retrieve"])
+    result = runner.invoke(cli, ["inboxes", "list"])
 
     assert result.exit_code != 0
     assert "--workspace" in result.output