Mirror_Repos/Kilo-Org_kilo
2
0
Fork 0
Code Issues Pull Requests Actions 84 Packages Projects Releases Wiki Activity

Merge pull request #476 from Olusammytee/docs/5619-clarify-cloud-setup-script-behavior

Browse Source 
docs(cloud-agent): clarify Setup Commands vs .kilocode/setup-script
This commit is contained in:
Brendan O'Leary
2026-02-21 06:32:10 -05:00
committed by GitHub
parent 6b610bb9a2 764a642a2e
commit 772b8689b2
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md
+9
View File
@@ -85,6 +85,15 @@ You can customize each Cloud Agent session by also defining env vars and startup
- Bootstrapping tooling - Bootstrapping tooling
- Running setup scripts - Running setup scripts
### Setup Commands vs `.kilocode/setup-script`
- Cloud Agent executes **Setup Commands** configured in the Cloud UI/profile.
- Cloud Agent does **not** automatically discover or run `.kilocode/setup-script`.
- If you want to use `.kilocode/setup-script` in Cloud Agent, call it explicitly from Setup Commands, for example: `bash .kilocode/setup-script`.
- If both are present, execution order is:
1. Setup Commands (in the order you define them)
2. Anything those commands invoke (such as `.kilocode/setup-script`)
## Skills ## Skills
Cloud Agents support project-level [skills](/docs/code-with-ai/platforms/cli#skills) stored in your repository. When your repo is cloned, any skills in `.kilocode/skills/` are automatically available. Cloud Agents support project-level [skills](/docs/code-with-ai/platforms/cli#skills) stored in your repository. When your repo is cloned, any skills in `.kilocode/skills/` are automatically available.