Projects
Create a project
Create a project owned by the member.
POST
https://cloud.generalinput.com/v1/projectsAuthenticationRequires
projects:manage on a personal API key. A CLI session always passes.Body
Two shapes are accepted. Scripts and the CLI send a named project; a client that only has the user's intent can send a goal instead, and the server drafts the specialist's name from it.
Named
| Field | Type | Required | Notes |
|---|---|---|---|
name | string | yes | 1 to 255 characters. |
description | string | no | Up to 4000 characters. |
icon | string | no | A single emoji. Legacy; the product now draws a worker figure, not the emoji. |
workerColor | string | no | The specialist figure's color: black, red, blue, yellow, green, orange, or purple. Random when omitted. |
workerAccessories | object | no | { head, shirt, hand }, each an accessory id (from the picker's catalog) or null. |
Goal
| Field | Type | Required | Notes |
|---|---|---|---|
goal | string | yes | What the specialist is for, in plain words (up to 2000 characters). The server names it from this. |
workerColor | string | no | As above. |
workerAccessories | object | no | As above; omit (or send an all-null set) to let the server pick one that fits the goal. |
Response
201 Created with the project summary (one entry of list projects) plus introductionThreadId — the chat the specialist opened to greet its creator.