Skip to main content
Pulumi logo Pulumi logo
  1. Docs
  2. Reference
  3. REST API Docs
  4. Schema
  5. CreateAgentTaskRequest

CreateAgentTaskRequest

    Create a new task by sending the first event in the conversation.

    Properties

    • message AgentUserEventMessage optional
      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”.
    • content string required
      The exact natural language instruction from the user.
    • entity_diff AgentEntityDiff optional
      Entities to add or remove from the agent.
    • commands map[string]AgentSlashCommand optional
      Slash Commands the user selected when creating their message.
    • pageContext PageContext optional
      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).
    • timestamp string required
      When the event occurred.
    • type string required
    • approvalMode enum optional
      Optional approval mode override for this task. If omitted, org default is used.
      Values: manual, auto, balanced
    • planMode boolean optional
      Whether to enable plan mode for this task.
    • permissionMode enum optional
      Controls the permission scope for the task. When omitted, defaults to ‘default’ (the agent uses the creating user’s full permissions).
      Values: default, read-only
    • role string optional
      Optional 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.
    • toolExecutionMode enum optional
      Where tools should be executed. Defaults to ‘cloud’ if omitted.
      Values: cloud, cli, worker
    • enabledIntegrations array[AgentTaskIntegrationRef] optional
      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.
    • id string required
      The catalog integration ID (e.g. ‘honeycomb’, ‘datadog’).
    • source enum optional
      The origin that triggered this task. Defaults to ‘api’ if omitted.
      Values: api, console, cli, slack, schedule, github, code-review
    • cliIntegrations array[CLIIntegrationRef] optional
      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.
    • catalogId string required
      The CLI catalog entry ID (e.g. ‘aws’).
    • name string required
      The user-chosen instance name. Unique within the (org, catalogId) pair.

      The infrastructure as code platform for any cloud.