Tasks: Server-side input queue for auto-resume

Repo: coder/coder

Scope: Allow /send to accept messages for paused tasks, queue them, and deliver asynchronously.

Note: Consider ACP (Agent Communication Protocol) impact before implementation. ACP standardization may influence message queue design and delivery mechanism.

Changes:

• Create task_pending_inputs table:
  • id UUID PRIMARY KEY
  • task_id UUID REFERENCES tasks(id)
  • content TEXT NOT NULL
  • status TEXT NOT NULL DEFAULT 'pending'
  • created_at TIMESTAMPTZ NOT NULL
  • delivered_at TIMESTAMPTZ
  • error TEXT
• Modify /send to accept messages for paused tasks
• Return 202 Accepted with message ID for queued messages
• Background worker: trigger workspace start, poll for ready, deliver message, update status
• Handle failures (build fails, delivery fails) with appropriate status updates

Benefits beyond auto-resume (per RFC):

• Solves Terraform env var length limits for long prompts
• Unifies initial prompt + follow-up delivery path
• Enables prompt modification until task starts
• Enables prebuilds for tasks

Files:

• New migration for task_pending_inputs table
• coderd/aitasks.go (modified send handler)
• New background worker or integration with existing job system

Acceptance criteria:

• /send to paused task returns 202 and queues message
• Workspace automatically starts
• Message delivered when workspace ready
• Failure states handled gracefully with status tracking
• Direct API consumers no longer need orchestration logic

Dependencies:

• GA phase complete
• ACP (Agent Communication Protocol) evaluation (does not block, but may influence design)

References:

• PRD: Start/Pause/Resume the Task Workspace
• RFC: Tasks: Start/Pause/Resume Lifecycle: Auto-Resume Option B

Inizia da coderd/aitasks.go e dalla nuova migration per task_pending_inputs, quindi esamina il lifecycle RFC indicato e l’integrazione esistente con il sistema di job. Traccia come /send gestisce i task in pausa e come vengono rappresentati la disponibilità del workspace e il recapito. Il lavoro è completato quando i messaggi accodati restituiscono 202 con un ID, vengono recapitati dopo l’avvio automatico del workspace e registrano gli stati di errore come specificato.