Skip to main content
A project’s config is validated by projectConfigSchema in packages/contracts/src/projects.ts. You normally edit it in the web project editor. Over MCP, use the project config tools.
The schema still carries fields from earlier designs, such as instance, studio and hardening settings. This page lists the fields that matter for the local runner. For the full shape, read the schema.

Top-level fields

Repository (repos[])

key, name, aliases, gitUrl, defaultBranch, enabled, runtime (node or python), installCommand, prepareCommands, devCommand, port, needsDatabase, env and more.

Kiro agent (kiroCli)

MCP server entry

Transport is stdio, http or sse. Header and env values may be ${...} placeholders. Over MCP, secret values are masked on read and the placeholder round-trips safely on write.