Projects
Projects
Folders that group workflows, apps, skills, and shared files. Sharing a project shares everything in it.
A project is a single-home container: a workflow, app, or skill sits in at most one project, or at the root. Grants on a project flow down to what it holds. Project files are human input that every chat in the project mounts read-only at project/.
AuthenticationRequires
projects:manage on a personal API key. A CLI session always passes.Endpoints
| Endpoint | Does |
|---|---|
GET /v1/projects | Projects the member can access |
POST /v1/projects | Create |
GET /v1/projects/:id | A project and what it holds |
PATCH /v1/projects/:id | Rename, describe, set the icon |
POST /v1/projects/:id/delete | Delete, owner only |
POST /v1/projects/pin | Move a resource into or out of a project |
GET /v1/projects/:id/files | List shared files |
GET /v1/projects/:id/files/bundle | Download every file as a tar.gz |
POST /v1/projects/:id/files/bundle | Upload a tar.gz, additive |
DELETE /v1/projects/:id/files?path= | Remove one file |
Roles
role on a project is owner, editor, or viewer, resolved from the nearest grant (owner, collaborator, workspace grant). Reads need any access; writes to the project and its files need edit; deleting needs ownership.