Command lineGetting started
The organization in use
kcloud acts in one organization at a time. Without any setting it is the organization of your account, so most people never pick one.
Step 1: List the organizations
The command lists the organizations you can see. A star next to the slug marks the one kcloud acts in.
$ kcloud orgs listOutput
SLUG NAME ID acme * Acme 0195a3c4-7e21-7b6d-9f40-3c81a4d2e600
Step 2: Pick an organization
The command remembers the organization for this address of the platform. Name the organization by its slug, its name or its id.
$ kcloud orgs use acmeOutput
kcloud acts in Acme (acme) on https://cloud.kikimora.dev from now on.
Step 3: Show the organization
Without an argument the command shows the organization in use: its name, slug, color, logo and the switch threshold of its Claude accounts.
$ kcloud orgs showOutput
FIELD VALUE name Acme slug acme color #7c86ff logo - switch threshold 90% created 2026-03-14T09:30:00.000Z id 0195a3c4-7e21-7b6d-9f40-3c81a4d2e600
Step 4: Pick the organization for one command
The option --org works with every command and remembers nothing.
$ kcloud --org acme projects listOutput
SLUG NAME MEMBERS DOCKER ID sandbox Sandbox 1 allowed 0195a3c4-7e21-7b6d-9f40-3c81a4d2e600
The variable KIKIMORA_CLOUD_ORG does the same for every command of the shell, as in KIKIMORA_CLOUD_ORG=acme kcloud agents list. --org wins over the variable, and the variable wins over the choice of kcloud orgs use.
Step 5: Go back to your own organization
With --clear kcloud forgets the choice and acts in the organization of your account again.
$ kcloud orgs use --clearOutput
kcloud acts in your own organization on https://cloud.kikimora.dev again.
kcloud orgs use keeps the choice next to the token, so it refuses a token from the variable KIKIMORA_CLOUD_TOKEN. In a CI pipeline use --org or KIKIMORA_CLOUD_ORG.
Matches the panel at cloud.kikimora.dev.