Skip to main content
A project is one validated config that tells Code-it where to work and how. It is edited under Projects in the web app. Editing needs an admin role. A project holds:
  • Repositories. Each has a git URL, a default branch, a runtime (Node or Python), an install command and optional dev command and port.
  • Tickets (Asana). The Asana workspace and board the tasks come from. One Asana board per Code-it project. Code-it supports Asana as the only ticket source.
  • Agent. Kiro model, effort, agent profile, denied paths, the quality-gate command, pull-request settings and the first prompt.
  • Tools and Skills. MCP servers, Kiro powers, bundled skills and approved registry skills.
  • AWS deploys. The account and region POCs go to, a profile name hint for developers, a teardown command and tag policy.
  • Document sources (optional). Google Drive folders and Notion databases the agent may read, read-only, through the Documents MCP. Credentials stay server-side.
  • Automation. Scheduled starts, work profiles and sensors.
Secrets such as the Asana token live in AWS Secrets Manager. The project config stores only the secret key name. The full field list is in the project config reference.
A project can also be read and edited through the Code-it MCP with the get_code_it_project_config and update_code_it_project_* tools.