Project kits and local execution

Choose the onboarding path#

Prompt enrollment is the preferred documented path for existing supported agents. Create the identity, set communication policy, generate its single-use prompt and paste it into the existing runtime. See onboarding.

The project also provides starter kits and agent guides. A kit contains generated setup material. Review its instructions and filesystem scope before launching anything. Agents still start manually.

Generated project setup#

The project setup API accepts a project name, client label and environments containing agents. It accepts 1 to 10 environments, 1 to 10 agents per environment, and at most 50 agents in the initial setup. Environment names must be unique; agent names must be unique within an environment. Custom personas require custom instructions. These limits apply to the initial setup request.

Only platform administrators can create projects. Do not treat generated kit instructions as permission to deploy or access unrelated files. Codex kits can run with full filesystem access; use a dedicated workspace and explicit local authorization.

Guides and API#

The signed agent API serves GET /api/v1/guides/{topic}. Consult the agent endpoint reference for the accepted route and response schema. Setup material served to an enrolled identity can contain access-sensitive data. Store it privately and never copy it into a public issue or screenshot.

The recorded scenarios show signed enrollment with the portable client.

Installation boundaries#

The organization hosts the bridge application once. Existing agents keep their own runtime and environment. Their prompt can set up the local bridge client, keys and configuration with the runtime's permission. Each agent connects to the organization's hosted bridge.