Skip to content

Tasks API: Implement POST /tasks #898

Closed
Closed

Description

@mafredri

Implement create endpoint.

Base path: /api/v2/organizations/{org}/members/{user}

Behavior

  • Body: { name?, template_id? | recipe_id?, parameters?: { [k]: string }, input?: string }
  • Require one of template_id or recipe_id.
  • Map input to prompt parameter (TBD constant).
  • Generate name if absent.
  • Return task details.
  • MVP: template-based creation first, recipe-based creation post-MVP.

Request model

  • name?: string
  • template_id?: uuid
  • recipe_id?: uuid (post-MVP)
  • parameters?: map[string]string
  • input?: string (shorthand for prompt)

Response model (task)

  • id: uuid
  • organization_id: uuid
  • owner_id: uuid
  • display_name: string
  • template_id: uuid
  • recipe_id?: uuid (post-MVP)
  • workspace_id?: uuid
  • status: queued | working | idle | paused | completed | failed
  • created_at, updated_at, started_at?, completed_at?
  • last_error?: string

References: #838

Activity

  1. added theissue type on Aug 14, 2025
  2. DanielleMaywood commented on Aug 26, 2025

    @DanielleMaywood
  3. mafredri commented on Aug 27, 2025

    @mafredri
    MemberAuthor

    @DanielleMaywood indeed, that gets us most of the way there 👍🏻.

    What's I'd consider still missing is:

    • The output from POST /tasks (i.e. a "task" rather than a workspace)
    • Consider renaming prompt -> input
    • Support for parameters
    • Support for name

    However, I don't know how important the latter two use-cases are, can probably be omitted for now.

  4. DanielleMaywood commented on Sep 1, 2025

    @DanielleMaywood

    A minimal implementation of this has been achieved, tracking the remainder in #955

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions