From d3bb4f92803cf0b9afbb8851de1ca5538b20fc47 Mon Sep 17 00:00:00 2001 From: Alex Gold Date: Thu, 2 Apr 2026 08:55:49 -0400 Subject: [PATCH] Revise CLI organization selection instructions Updated instructions for interactive CLI usage and clarified organization selection process. --- .../pages/code-with-ai/platforms/cli.md | 20 +++---------------- 1 file changed, 3 insertions(+), 17 deletions(-) diff --git a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md index 826a1837af2..be5b191c2bb 100644 --- a/packages/kilo-docs/pages/code-with-ai/platforms/cli.md +++ b/packages/kilo-docs/pages/code-with-ai/platforms/cli.md @@ -474,28 +474,14 @@ If you belong to a Kilo organization (Team or Enterprise), you can route CLI req ### Interactive Usage -In an interactive CLI session, use the `/teams` command to see a list of all organizations you can switch into. Select an organization from the list to switch into it. Your selection is persisted locally so it carries over to future sessions. +In an interactive CLI session, use the `/teams` command to select an organization from your membership list. -The process is the same when switching into a Team or Enterprise organization. +Your selection is persisted locally so it carries over to future sessions. ### Non-Interactive Usage (`kilo run`) There is no `--org` or `--team` flag on `kilo run`. Instead, the organization is determined from the following sources, in order of priority (highest first): -1. **`KILO_ORG_ID` environment variable** — Best for non-interactive and CI environments. Set it alongside your API key: - - ```bash - KILO_ORG_ID= kilo run "your message" - ``` - - In CI (e.g., GitHub Actions), set it as a repository secret: - - ```yaml - env: - KILO_API_KEY: ${{ secrets.KILO_API_KEY }} - KILO_ORG_ID: ${{ secrets.KILO_ORG_ID }} - ``` +1. **`KILO_ORG_ID` environment variable** — Best for non-interactive and CI environments. 2. **Persisted selection from the last `/teams` pick** — If you've run an interactive session and selected an organization via `/teams`, that selection is stored in the CLI's local state file and reused automatically. - -3. **Default organization on your account** — If your account belongs to only one organization, it is used automatically without any additional configuration.