Skip to main content
Run code-it-runner doctor. If it reports a problem, run code-it-runner repair. If it says the token is rejected, run code-it-runner login --api https://api.aiml-code-it.automat-it.io. See runner troubleshooting.
The owner’s runner is not connected. Start or repair it on the owner’s laptop. The agent launches when the runner connects.
The runner clones with your gh login. Run gh auth status, then gh auth login for the right org, and retry.
Run aws sso login --profile <aws-profile>. The next turn picks it up.
Set a profile for the project: code-it-runner aws-profile <project-slug> <profile>.
That is current behaviour. The LaunchAgent install is macOS only.
No. The runner uses your named profile through the aws CLI and never reads credentials in-process. The platform does not receive them.
Your own Kiro plan, since the agent runs on your Kiro login.
Metrics pages read live platform data and some depend on repositories and Asana boards being configured on the project. Check the project’s Tickets and Repositories settings first, then tell the platform admin.
Check the runner is connected and that the agent is running. Run code-it-runner logs --follow while sending a prompt.
No. terraform apply, cdk deploy, cloudformation deploy and sam deploy go through the code-it-apply gate and wait for your approval.

Still stuck

Open an issue in the repository or ask the platform admin.