CreateAgentTaskRequest
Create a new task by sending the first event in the conversation.
Properties
- The message content. This is the first event in the conversation and must be a user message, so its discriminator field must be set to “type”: “user_message”.
- ↳
contentstring requiredThe exact natural language instruction from the user. - Entities to add or remove from the agent.
- Slash Commands the user selected when creating their message.
- Optional Pulumi Cloud page the user has the Neo pane open on at the moment they sent this event. Persisted with the event so cold-start replay can reproduce per-turn page context exactly. Omitted by clients with no concept of a current page (CLI, scheduled tasks, Slack, GitHub triggers, API consumers).
- ↳
timestampstring requiredWhen the event occurred. - ↳
typestring required approvalModeenum optionalOptional approval mode override for this task. If omitted, org default is used.Values:manual,auto,balancedplanModeboolean optionalWhether to enable plan mode for this task.permissionModeenum optionalControls the permission scope for the task. When omitted, defaults to ‘default’ (the agent uses the creating user’s full permissions).Values:default,read-onlyrolestring optionalOptional RBAC role the task assumes, identified by role id. When set, the task operates with that role’s permissions in place of the creating user’s own assignments. You may only assume a role that is assigned to you, directly or through a team; a role you do not hold is rejected with a 403. Omitted/null means no assumed role: the task uses the creating user’s full permissions. Orthogonal to permissionMode, which controls the read-only behavior posture independently.toolExecutionModeenum optionalWhere tools should be executed. Defaults to ‘cloud’ if omitted.Values:cloud,cli,worker- Optional list of integrations to enable for this task. Semantics: omitted/null → inherit all org-enabled integrations; empty list → explicit opt-out (no integration credentials for this task); populated list → whitelist of specific integrations by ID. Modeled as an object array rather than a bare string array so multi-instance support (instance_name, scope, etc.) can be added later without a wire break.
- ↳
idstring requiredThe catalog integration ID (e.g. ‘honeycomb’, ‘datadog’). sourceenum optionalThe origin that triggered this task. Defaults to ‘api’ if omitted.Values:api,console,cli,slack,schedule,github,code-review- Optional filter for CLI integrations to enable for this task. Semantics: omitted/null → enable all CLI integrations connected for the org; empty list → explicit opt-out (no CLI integrations for this task); populated list → whitelist by (catalogId, name) of the configured instances to enable. Entries with missing or unknown catalogId, missing name, or referencing a (catalogId, name) pair that is not connected for the organization are rejected with a 400 response. catalogId matching is case-insensitive.
- ↳
catalogIdstring requiredThe CLI catalog entry ID (e.g. ‘aws’). - ↳
namestring requiredThe user-chosen instance name. Unique within the (org, catalogId) pair.