current-cli 0.1.27__tar.gz → 0.1.28__tar.gz

{current_cli-0.1.27 → current_cli-0.1.28}/PKG-INFO

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

@@ -744,6 +744,45 @@ paths:
               schema:
                 $ref: '#/components/schemas/ManifestResponse'
           description: ''
+  /api/integrations/messaging/history/:
+    post:
+      operationId: integrations_messaging_history
+      description: |-
+        What was already said in this conversation, oldest last.
+
+        The agent is dispatched with one message and no memory of the last
+        one, so without this every turn answers out of context — "send it to
+        the same person" has no referent. Neither provider will give the
+        history back (see ``integrations.transcript``), so this reads current's
+        own ledger: the messages people sent the bot, and the replies the bot
+        sent them.
+
+        Unlike the send paths this needs no anti-spoofing guard. It only ever
+        reads the calling workspace's own observations, so a forged
+        conversation id reads nothing rather than reaching another tenant.
+      tags:
+      - integrations
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/MessagingHistoryRequestRequest'
+          application/x-www-form-urlencoded:
+            schema:
+              $ref: '#/components/schemas/MessagingHistoryRequestRequest'
+          multipart/form-data:
+            schema:
+              $ref: '#/components/schemas/MessagingHistoryRequestRequest'
+        required: true
+      security:
+      - MessagingJobTokenAuth: []
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/MessagingHistoryResponse'
+          description: ''
   /api/integrations/messaging/react/:
     post:
       operationId: integrations_messaging_react
@@ -1460,6 +1499,41 @@ paths:
               schema:
                 $ref: '#/components/schemas/Project'
           description: ''
+  /api/projects/projects/search/:
+    get:
+      operationId: projects_projects_search_retrieve
+      description: |-
+        Find projects by their current field values (see state.search_projects).
+
+        Compact on purpose: the full project list serializes every field
+        value of every project — megabytes at production scale — which no
+        chat agent or picker can consume. A hit carries just enough to
+        choose a project and fetch its detail.
+      parameters:
+      - in: query
+        name: q
+        schema:
+          type: string
+        description: Case-insensitive regular expression; a plain word searches as
+          a keyword
+        required: true
+      - in: query
+        name: workspace
+        schema:
+          type: string
+        description: Filter by workspace UUID
+      tags:
+      - projects
+      security:
+      - MessagingJobTokenAuth: []
+      - tokenAuth: []
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ProjectSearchResponse'
+          description: ''
   /api/tasks/tasks/:
     get:
       operationId: tasks_tasks_list
@@ -3583,6 +3657,24 @@ components:
       - role
       - workspace_id
       - workspace_name
+    MessagingHistoryRequestRequest:
+      type: object
+      properties:
+        workspace:
+          type: string
+          format: uuid
+        reply_ref: {}
+        limit:
+          type: integer
+      required:
+      - reply_ref
+      - workspace
+    MessagingHistoryResponse:
+      type: object
+      properties:
+        messages: {}
+      required:
+      - messages
     MessagingOk:
       type: object
       properties:
@@ -4137,6 +4229,56 @@ components:
         fields: {}
       required:
       - workspace
+    ProjectSearchMatch:
+      type: object
+      description: One field whose current value matched the search pattern.
+      properties:
+        field:
+          type: string
+        value:
+          type: string
+      required:
+      - field
+      - value
+    ProjectSearchResponse:
+      type: object
+      description: |-
+        ``count`` is the total number of matching projects; ``results`` is
+        capped (see ``state.SEARCH_RESULT_LIMIT``), name-field hits first.
+      properties:
+        count:
+          type: integer
+        results:
+          type: array
+          items:
+            $ref: '#/components/schemas/ProjectSearchResult'
+      required:
+      - count
+      - results
+    ProjectSearchResult:
+      type: object
+      description: 'One project hit: identity plus the fields that matched.'
+      properties:
+        id:
+          type: string
+          format: uuid
+        workspace:
+          type: string
+          format: uuid
+        name:
+          type: string
+        status:
+          type: string
+        matched:
+          type: array
+          items:
+            $ref: '#/components/schemas/ProjectSearchMatch'
+      required:
+      - id
+      - matched
+      - name
+      - status
+      - workspace
     PromoteRequestRequest:
       type: object
       properties:

{current_cli-0.1.27 → current_cli-0.1.28}/llms.txt

@@ -284,6 +284,26 @@ messaging-job endpoint uses.
 
 POST /api/integrations/messaging/files/manifest/
 
+### current integrations messaging history post
+
+What was already said in this conversation, oldest last.
+
+The agent is dispatched with one message and no memory of the last
+one, so without this every turn answers out of context — "send it to
+the same person" has no referent. Neither provider will give the
+history back (see ``integrations.transcript``), so this reads current's
+own ledger: the messages people sent the bot, and the replies the bot
+sent them.
+
+Unlike the send paths this needs no anti-spoofing guard. It only ever
+reads the calling workspace's own observations, so a forged
+conversation id reads nothing rather than reaching another tenant.
+
+POST /api/integrations/messaging/history/
+
+Options:
+- `--data` (required) - Request body as JSON: inline, @file.json, or - for stdin.
+
 ### current integrations messaging react post
 
 Add an emoji reaction to the message a reply_ref points at.
@@ -517,6 +537,21 @@ POST /api/projects/projects/{id}/revert/
 Options:
 - `--data` (required) - Request body as JSON: inline, @file.json, or - for stdin.
 
+### current projects search retrieve
+
+Find projects by their current field values (see state.search_projects).
+
+Compact on purpose: the full project list serializes every field
+value of every project — megabytes at production scale — which no
+chat agent or picker can consume. A hit carries just enough to
+choose a project and fetch its detail.
+
+GET /api/projects/projects/search/
+
+Options:
+- `--q` - Case-insensitive regular expression; a plain word searches as a keyword
+- `--workspace` - Filter by workspace UUID
+
 ### current projects update <id>
 
 Projects across the caller's workspaces. Any member can create and edit.

{current_cli-0.1.27 → current_cli-0.1.28}/pyproject.toml

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