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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: current-cli
3
- Version: 0.1.30
3
+ Version: 0.1.32
4
4
  Summary: Command line interface for the Current API, generated from its OpenAPI schema at runtime
5
5
  Author-email: Orin <your-email@example.com>
6
6
  License-Expression: MIT
@@ -1080,15 +1080,8 @@ paths:
1080
1080
  post:
1081
1081
  operationId: integrations_messaging_respond
1082
1082
  description: |-
1083
- Send the agent's reply into the conversation a reply_ref points at,
1084
- with any workspace files it chose to attach.
1085
-
1086
- Slack shares the files and the text as one message (the text becomes
1087
- the upload's ``initial_comment``). Teams cannot: a bot there has to
1088
- offer each file through a FileConsentCard the recipient accepts, and
1089
- only in a 1:1 chat, so the text posts first and each file follows as
1090
- its own offer. Email is the easy one — attachments are what it is for,
1091
- and they ride along on the reply.
1083
+ Relay the agent's reply, and any workspace files it chose to attach,
1084
+ into the conversation the message came from — see :func:`send_reply`.
1092
1085
  tags:
1093
1086
  - integrations
1094
1087
  requestBody:
@@ -4138,6 +4131,11 @@ components:
4138
4131
  type: string
4139
4132
  minLength: 1
4140
4133
  maxLength: 1024
4134
+ about_runs:
4135
+ type: array
4136
+ items:
4137
+ type: string
4138
+ format: uuid
4141
4139
  required:
4142
4140
  - reply_ref
4143
4141
  - text
@@ -4167,6 +4165,9 @@ components:
4167
4165
  format: uuid
4168
4166
  note:
4169
4167
  type: string
4168
+ observation:
4169
+ type: string
4170
+ format: uuid
4170
4171
  required:
4171
4172
  - reply_ref
4172
4173
  - workflow
@@ -5401,6 +5402,13 @@ components:
5401
5402
  - workspace
5402
5403
  WorkflowDefinition:
5403
5404
  type: object
5405
+ description: |-
5406
+ A definition as its consumers need it: the raw ``definition`` blob for
5407
+ the portal, plus the three derived properties that say what the workflow
5408
+ is called, what it is for, and whether it runs on one project. The
5409
+ messaging agent reads only the derived three (see the ``list_workflows``
5410
+ tool), which is why they are served here rather than left to every
5411
+ caller to dig out of ``definition["control"]``.
5404
5412
  properties:
5405
5413
  id:
5406
5414
  type: string
@@ -5414,6 +5422,15 @@ components:
5414
5422
  type: string
5415
5423
  readOnly: true
5416
5424
  pattern: ^[-a-zA-Z0-9_]+$
5425
+ display_name:
5426
+ type: string
5427
+ readOnly: true
5428
+ description:
5429
+ type: string
5430
+ readOnly: true
5431
+ scope:
5432
+ type: string
5433
+ readOnly: true
5417
5434
  definition:
5418
5435
  readOnly: true
5419
5436
  rendered_hash:
@@ -5426,9 +5443,12 @@ components:
5426
5443
  required:
5427
5444
  - applied_at
5428
5445
  - definition
5446
+ - description
5447
+ - display_name
5429
5448
  - id
5430
5449
  - name
5431
5450
  - rendered_hash
5451
+ - scope
5432
5452
  - workspace
5433
5453
  WorkflowRequest:
5434
5454
  type: object
@@ -409,15 +409,8 @@ Options:
409
409
 
410
410
  ### current integrations messaging respond post
411
411
 
412
- Send the agent's reply into the conversation a reply_ref points at,
413
- with any workspace files it chose to attach.
414
-
415
- Slack shares the files and the text as one message (the text becomes
416
- the upload's ``initial_comment``). Teams cannot: a bot there has to
417
- offer each file through a FileConsentCard the recipient accepts, and
418
- only in a 1:1 chat, so the text posts first and each file follows as
419
- its own offer. Email is the easy one — attachments are what it is for,
420
- and they ride along on the reply.
412
+ Relay the agent's reply, and any workspace files it chose to attach,
413
+ into the conversation the message came from — see :func:`send_reply`.
421
414
 
422
415
  POST /api/integrations/messaging/respond/
423
416
 
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "current-cli"
3
- version = "0.1.30"
3
+ version = "0.1.32"
4
4
  description = "Command line interface for the Current API, generated from its OpenAPI schema at runtime"
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.10"
File without changes
File without changes