From 4fd19a1cd7a160f52dce1256dfd20eba643afe07 Mon Sep 17 00:00:00 2001 From: Olusammytee Date: Thu, 19 Feb 2026 09:32:03 -0500 Subject: [PATCH] docs(cloud-agent): clarify Setup Commands vs .kilocode/setup-script --- .../pages/code-with-ai/platforms/cloud-agent.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md index 708e51e81..967ec9816 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/cloud-agent.md @@ -85,6 +85,15 @@ You can customize each Cloud Agent session by also defining env vars and startup - Bootstrapping tooling - 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 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.