Command lineCommands

Projects

The projects of the organization, their members and the queue of Claude accounts the agents of a project work on. The panel does the same on the Projects tab of the organization and the Members and Settings tabs of a project.

Who can do it

Any member of a project can list and show it. Only an organization admin creates and deletes projects. A project admin or an organization admin changes a project, its members and its queue of accounts.

Step 1: List the projects

The command shows the projects you can see, with the number of members and whether their agents may use Docker.

$ kcloud projects list

Output

SLUG     NAME     MEMBERS  DOCKER   ID
sandbox  Sandbox        1  allowed  0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 2: Show a project

Name the project by its slug, its name or its id. The command shows its settings and its members.

$ kcloud projects show sandbox

Output

FIELD        VALUE
name         Sandbox
slug         sandbox
description  -
color        #6366f1
logo         -
docker       allowed
members      1
created      2026-03-14T09:30:00.000Z
id           0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 3: Create a project

The slug comes from the name unless --slug sets it. --color sets the color of the project in the panel.

$ kcloud projects create "Mobile app" --description "The iOS and Android app." --color "#0ea5e9"

Output

Created Mobile app (mobile-app) in acme as 0195a3c4-7e21-7b6d-9f40-3c81a4d2e600.

Step 4: Change a project

The command changes the name, slug, description, color or logo of a project. An option left out keeps its value.

$ kcloud projects update mobile-app --description "The iOS and Android app, released every two weeks."

Output

Changed Mobile app (mobile-app).

Step 5: Delete a project

The platform deletes only a project without agents, credentials, repositories and tools. --yes skips the question that confirms it.

$ kcloud projects delete mobile-app --yes

Output

Deleted the project Mobile app.

Step 6: List the members of a project

The admins of the organization see every project and need not be its members.

$ kcloud projects members list sandbox

Output

EMAIL                   ROLE   STATUS  ADDED                     ID
anna.nowak@example.com  admin  active  2026-03-14T09:30:00.000Z  0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 7: Add a member or change their role

The person has to belong to the organization. The role admin lets them manage the project, and member lets them work with its agents.

$ kcloud projects members set sandbox piotr.kowalski@example.com --role member

Output

piotr.kowalski@example.com is a member of the project sandbox now.

Step 8: Take a member off a project

The person stays in the organization and loses access to the project.

$ kcloud projects members remove sandbox piotr.kowalski@example.com --yes

Output

Removed piotr.kowalski@example.com from the project sandbox.

The agents of a project work on the Claude accounts of the organization in the order of the queue of the project: on the first account that can work. Name an account by its label or its id.

Step 9: Show the queue of accounts

The STATE column says whether an account works (in use), can take over (available), reached its limit (exhausted until), has no credits (no credits) or failed its verification (invalid).

$ kcloud projects accounts list --project sandbox

Output

#  LABEL       KIND                STATE   USAGE    AGENTS  ID
1  Claude Max  claude_oauth_token  in use  no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 10: Add an account at the end of the queue

The account has to belong to the organization already; kcloud claude-accounts add adds it.

$ kcloud projects accounts add "Claude Backup" --project sandbox

Output

#  LABEL          KIND                STATE      USAGE    AGENTS  ID
1  Claude Max     claude_oauth_token  in use     no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e600
2  Claude Backup  claude_oauth_token  available  no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e601

Step 11: Move an account in the queue

--to names the new place of the account, counted from 1.

$ kcloud projects accounts move "Claude Backup" --to 1 --project sandbox

Output

#  LABEL          KIND                STATE      USAGE    AGENTS  ID
1  Claude Backup  claude_oauth_token  in use     no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e600
2  Claude Max     claude_oauth_token  available  no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e601

Step 12: Take an account out of the queue

The account stays in the organization and in the queues of other projects.

$ kcloud projects accounts remove "Claude Backup" --project sandbox

Output

#  LABEL       KIND                STATE   USAGE    AGENTS  ID
1  Claude Max  claude_oauth_token  in use  no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 13: Set the whole queue

The command replaces the queue with the accounts named, first one first. Without an account it empties the queue, and then the agents of the project cannot work.

$ kcloud projects accounts set "Claude Max" "Claude Backup" --project sandbox

Output

#  LABEL          KIND                STATE      USAGE    AGENTS  ID
1  Claude Max     claude_oauth_token  in use     no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e600
2  Claude Backup  claude_oauth_token  available  no data       0  0195a3c4-7e21-7b6d-9f40-3c81a4d2e601

Settings and people of the organization Claude accounts

Matches the panel at cloud.kikimora.dev.