Command lineCommands

Agents

The agents of the projects, their settings and their deletion. The panel does the same on the Agents tab of a project and in the agent wizard.

Who can do it

Any member of the project.

Step 1: List the agents of a project

Name the project by its slug, its name or its id. Without --project the command lists the agents of every project you can see.

$ kcloud agents list --project sandbox

Output

PROJECT  AGENT    STATE    RELEASE  PENDING  ID
sandbox  nightly  stopped  0.12.0   -        0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

Step 2: Show an agent

Name the agent as project/agent, by its slug alone with --project, or by its id. The command shows its state, its Kikimora release, its node, its Claude account, its repositories, its tools and the actions it accepts now.

$ kcloud agents show sandbox/nightly

Output

FIELD           VALUE
name            Nightly
slug            nightly
state           stopped
wanted          stopped
observed        exited
release         0.12.0
claude code     2.1.293
claude account  Claude Max (claude_oauth_token), 1 of 1
node            acme-01 (online)
requires        nothing
timezone        Europe/Warsaw
disk            20 GB
docker          no
browser         no
container       3f9a6c1e8b2d4f70a5c39e1b7d2f6a804c1e9b3d5f7a2c6e8b0d4f1a3c5e7b9d
health          none
pool limit      none: its node holds no pool to a limit
pending         -
actions         start, restart, update, reset
version         45
id              0195a3c4-7e21-7b6d-9f40-3c81a4d2e600

REPOSITORY            PROVIDER  SERVER              DIRECTORY  STATUS
kikimoradev/kikimora  github    https://github.com  kikimora   ok

GIT CREDENTIALS
PROVIDER  SERVER              LABEL
github    https://github.com  GitHub

In a terminal, kcloud agents create --project sandbox asks for everything an agent needs, step by step: its name, node, Kikimora release, repositories, the tokens of their providers, tools and prompts. In a script a JSON file describes the agent; the page Agents and tools from a file describes creating and changing an agent from a file.

A new agent is provisioned first: its node pulls the image and clones the repositories. Only then does kcloud agents start start it; until then the platform answers agent.busy.

Step 3: Delete an agent

The agent goes with its container, its workspace and its history. Without --now the platform waits for its current session to end.

$ kcloud agents delete sandbox/release-notes --now --yes

Output

Deleting sandbox/release-notes now.

Nodes Controlling an agent

Matches the panel at cloud.kikimora.dev.