Factories

Get a factory task by conversation

Changed on

Get the factory task bound to an agent conversation. Conversation bindings are unique across factories, but the lookup is factory-scoped: a task owned by a different factory is 404.

get/factory/{uid}/task-by-conversation

Request

  • Base URL
    https://app.warp.dev/api/v1
  • Auth
    HTTP bearer

Path parameters

uidstring required

The public UID of the factory.

Query parameters

conversation_idstring required

The agent conversation ID the task is bound to.

Response

Factory task details with derived outputs

uidstring required

Public UID of the task.

factory_uidstring required

Public UID of the factory the task belongs to. Fixed at creation.

conversation_idstring required

UUID of the agent conversation the task is bound to.

run_idstring required

ID of the bound conversation's most recent run at task creation. This is a provenance snapshot and is not updated afterward; consumers needing the conversation's live latest run should resolve it via the conversation.

titlestring required

Human-readable title of the task.

ticket_sourcestring

Canonical ticket source from the bound run. Present on list responses only when full_list=true and ticket metadata exists.

ticket_idstring

Canonical ticket ID from the bound run. Present on list responses only when full_list=true and ticket metadata exists.

descriptionstring nullable

Optional description of the task.

stage'TRIAGE' | 'SPEC' | 'IMPLEMENT' | 'REVIEW' | 'COMPLETE' | 'CANCELLED' required

Lifecycle stage of a factory task, mirroring the seeded factory agent roles plus the terminal COMPLETE and CANCELLED states. COMPLETE and CANCELLED are terminal in intent but not enforced: any stage may be written explicitly at any time. CANCELLED is set automatically when the task's current top-level run is cancelled, regardless of that run's agent type.

created_atstring date-time required

Time the task was created.

updated_atstring date-time required

Time the task was last created, updated, or deleted. Artifact reporting does not bump this; new outputs appear on the next detail read.

Changes

    • breaking

      removed the required property //////// from the response with the status

    • info

      added the optional property to the response with the status

    • info

      endpoint added