> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quiva.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Update one backlog item

> Sparse patch addressed by `scope` + `id`; a nil field is left alone, and at least one of `status`, `content`, `details`, `follow_up_at` must be present. Cancelling is `status: "cancelled"` through this same path.

`scope=user` always resolves to the **caller's own** document — there is no `user_id` field, so a caller can never address a colleague's backlog. `scope=organisation` is writable by any authenticated account member.

`follow_up_at` means "chase the person this item is stuck on", not "start this later", so it **must** be sent together with `status: "awaiting_user"` — otherwise nothing would ever clear it again. Deferring a start is a schedule, which this endpoint deliberately does not expose.

Side effects: closing an item disarms any schedule on it; un-parking one republishes the work event carrying `approved_tool_ids`/`approved_server_ids`/`denied_server_ids` so the resuming run does not hit the same wall; cancelling one also stops the hop already in flight. Subject: `microstrate.hub.put.coworker-todo`.



## OpenAPI

````yaml /api-reference/endpoint/abbie/openapi.json put /hub/coworker/todo
openapi: 3.1.0
info:
  title: Abbie API (beta)
  version: 1.0.0
  description: >
    **Beta.** This API is in beta: operations and fields may change without a
    deprecation period. Do not depend on undocumented fields. It covers the
    subset of Abbie's API used by the Quiva coworker MCP server: skills, todos,
    memory, profile, corrections, environment and models.


    HTTP surface of hub-service for Abbie/Coworker configuration, agent rapport
    & context, chat-session sharing, and MCP registration.


    ## Transport and response envelope


    Every operation here is a gateway mapping onto a Bellerophon/kraken subject
    of the form `microstrate.hub.<method>.<endpoint-slug>` (see
    `hub-service/service/service.go` and `docs/abbie-gateway-mappings.md`).
    Handlers reply on the mesh with an envelope `{"status_code": <int>, "body":
    <object>}`; the gateway unwraps it, so `status_code` becomes the HTTP status
    and `body` becomes the HTTP response body. **The schemas below describe the
    unwrapped `body`.**


    Errors are always `{"error": "<message>"}` with the matching HTTP status.


    ## Parameter conventions


    The gateway forwards URL parameters to the handler as request headers:


    - `x-param-query-<name>` — a query-string parameter (`?name=value`)

    - `x-param-<name>` — a path parameter


    Every parameter documented as `in: query` or `in: path` below corresponds to
    one of those headers, and the header suffix is named in each parameter's
    description where it is not obvious.


    ## Authentication


    All operations require the caller's bearer token; the account id, user id
    and user public key are always taken from the JWT and never from the URL or
    body. Endpoints that additionally require an account **admin** role are
    marked in their description — a failed role lookup answers **502**, never
    403 and never a pass.


    ## Two path notes


    - `PATCH /hub/agent-session-visibility/{session_id}` — the handler reads the
    path parameter as `x-param-session_id`, matching its sibling `PATCH
    /hub/agent-session/{session_id}`.

    - `GET|POST|PUT /hub/agent/user-context/{id}` — the handler requires the
    **agent id** as `x-param-id`; the frontend calls
    `/hub/agent/user-context/<agentId>`.
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Skills
  - name: Todos
  - name: Memory
  - name: Profile and personality
  - name: Corrections
  - name: Environment
  - name: Models
paths:
  /hub/coworker/todo:
    put:
      tags:
        - Todos
      summary: Update one backlog item
      description: >-
        Sparse patch addressed by `scope` + `id`; a nil field is left alone, and
        at least one of `status`, `content`, `details`, `follow_up_at` must be
        present. Cancelling is `status: "cancelled"` through this same path.


        `scope=user` always resolves to the **caller's own** document — there is
        no `user_id` field, so a caller can never address a colleague's backlog.
        `scope=organisation` is writable by any authenticated account member.


        `follow_up_at` means "chase the person this item is stuck on", not
        "start this later", so it **must** be sent together with `status:
        "awaiting_user"` — otherwise nothing would ever clear it again.
        Deferring a start is a schedule, which this endpoint deliberately does
        not expose.


        Side effects: closing an item disarms any schedule on it; un-parking one
        republishes the work event carrying
        `approved_tool_ids`/`approved_server_ids`/`denied_server_ids` so the
        resuming run does not hit the same wall; cancelling one also stops the
        hop already in flight. Subject: `microstrate.hub.put.coworker-todo`.
      operationId: putCoworkerTodo
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PutTodoRequest'
      responses:
        '200':
          description: The item as updated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TodoItem'
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  schemas:
    PutTodoRequest:
      type: object
      required:
        - id
      properties:
        id:
          type: string
        scope:
          type: string
          enum:
            - organisation
            - user
          description: '`user` always means the caller''s own document'
        status:
          $ref: '#/components/schemas/TodoStatus'
        content:
          type: string
        details:
          type: string
          description: An explicit empty string clears it; a blank `content` is refused
        follow_up_at:
          type: string
          format: date-time
          description: 'Must be sent together with `status: awaiting_user`'
        approved_tool_ids:
          type: array
          items:
            type: string
          description: >-
            Answer to the consent card that parked this item. **Not stored** —
            forwarded on the work event so the resuming run carries the consent.
            Ignored unless the patch un-parks the item.
        approved_server_ids:
          type: array
          items:
            type: string
          description: >-
            "Just this once" server approvals. Forwarded, never stored — an
            approval that settled on the item would become the standing grant
            the Authorise button exists to make deliberate.
        denied_server_ids:
          type: array
          items:
            type: string
          description: Forwarded, never stored
    TodoItem:
      type: object
      properties:
        id:
          type: string
        content:
          type: string
          description: The one-line item
        details:
          type: string
          description: Long-form context behind `content`
        status:
          $ref: '#/components/schemas/TodoStatus'
        owner_user_id:
          type: string
          description: Mesh identity of the item's owner
        session_id:
          type: string
        blocked_on:
          type: string
        follow_up_at:
          type: string
          format: date-time
          description: >-
            "Chase the person this item is parked on" — only meaningful on an
            `awaiting_user` item
        kind:
          type: string
        scheduled_for:
          type: string
          format: date-time
        cron:
          type: string
        created:
          type: string
          format: date-time
        updated:
          type: string
          format: date-time
        scope:
          type: string
          enum:
            - organisation
            - user
          description: Added by the read/write handlers; not part of the stored document
    TodoStatus:
      type: string
      enum:
        - pending
        - in_progress
        - done
        - awaiting_user
        - cancelled
    Error:
      type: object
      description: The unwrapped error body. The HTTP status carries the code.
      properties:
        error:
          type: string
      required:
        - error
  responses:
    BadRequest:
      description: Malformed payload or a failed validation rule
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: No account (or user) identity in the auth context
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: The addressed resource does not exist for this caller
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.