Projects
A project's lifecycle, access, membership roles, and agent configuration.
A project belongs to exactly one team. The team owns billing, members, and API keys, and the project scopes the chats, Runs, and agent configuration that work inside it, with its own membership list.
Lifecycle
A project has one of three statuses, and the API returns them as ACTIVE,
ARCHIVED, and DELETED:
ACTIVE- the project is in the working set.ARCHIVED- the project stays readable but is out of the working set.DELETED- the project is removed from the working set.
Access
A project is either OPEN or RESTRICTED:
OPEN- every team member can read the project.RESTRICTED- only the project's own members and the team's owners and admins can read it, so a restricted project is also the only kind that never appears in a team-wide suggestion for anyone else.
Membership roles
A project member holds one of three roles, which scope what the member may do inside the project:
ADMIN- manage the project, its members, and its configuration.WRITE- read the project and mutate its content, including dispatching its Runs.READ- read the project and its history without mutating it.
Capabilities on an API key do not replace project membership; the project policy is evaluated with the key's capabilities and may deny the request or require approval. See the API overview for the capability levels and action grants.
Agent configuration
A project can carry an agentTemplateSlug and an agentConfig that describe
the agent its Runs use. See Factory for the
deployable agent configuration and its lifecycle.
Creating a project
Creating a project through the Developer API can start a setup Run. The create
response returns a bootstrap value that reports how that setup went:
ready- the setup Run started, with itschatIdandrunId.not_applicable- no setup Run was needed, with areason.setup_failed- the setup Run failed, with aretryableflag.
See the API overview for the project endpoint family, and Start a project Run and read its result for the request flow.