> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiml-code-it.automat-it.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Project config

> The top-level fields of a project's config and what they control.

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.

> [!WARNING]
>
> 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

| Field | What it controls |
| - | - |
| `repos` | At least one repository, with at least one enabled. Keys, directory names and aliases must be unique |
| `git` | Ticket branch base, whether to create a ticket branch on launch, protected branches, commit author name and email |
| `naming` | Instance prefix, project tag, unit prefix |
| `ticketProvider`, `asana` | Asana is the only provider. Needs the Asana workspace and project ids |
| `kiroCli` | Everything about the Kiro agent. See below |
| `triggers` | [Scheduled starts](https://docs.aiml-code-it.automat-it.io/guides/scheduled-starts.md) |
| `pullRequests` | PR hook, "how to test" document and quality gate |
| `documentSources` | Drive folders and Notion databases the agent may read |
| `pocRepo` | Optionally create a new GitHub repo per POC ticket. Off by default |
| `secrets` | Secret name prefix and the keys for SSH, deploy key and npmrc |
| `tooling` | Pinned tools such as Terraform, tflint, checkov, CDK |
| `creditToUsdFactor` | Credit to USD factor for reporting. Null means no tracking |
| `teardownCommand` | Command run before an agent is terminated. Best effort |
| `defaults` | Whether to auto-start the agent, and the default first prompt |

## Repository (`repos[]`)

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

## Kiro agent (`kiroCli`)

| Field | Meaning |
| - | - |
| `version` | Pinned `kiro-cli` version. Empty means the default |
| `acpEngine` | ACP generation. Default `v3` |
| `agentName` | Agent profile id. Empty uses the CLI default |
| `model`, `effort` | Default model and effort |
| `trustTools` | Exact tool ids the agent trusts |
| `deniedPaths` | Paths the agent is kept out of |
| `steering` | Steering markdown globs staged for the agent |
| `powers` | Powers the project consents to. See [Powers](https://docs.aiml-code-it.automat-it.io/concepts/powers.md) |
| `mcpServers` | MCP servers wired into the agent |
| `hooks` | `stopInBackground` and `preToolUseDenyGuard`, both on by default |
| `sandbox` | `enabled` (default on) and `required` (default off) |
| `aidlc` | AI-DLC pack settings. Off by default |
| `workProfiles`, `layeredRules`, `sensors` | See [Work profiles](https://docs.aiml-code-it.automat-it.io/guides/work-profiles.md) |

## 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.