@kikimoradev/kcloud 0.13.0 → 0.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +17 -12
  2. package/dist/main.js +1323 -463
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,17 +1,20 @@
1
1
  # kcloud
2
2
 
3
- The command line of a Kikimora Cloud instance. What the panel does with a project, this does from a
4
- terminal: projects, credentials, repositories, tools, agents, their tasks, sessions, costs and logs.
3
+ The command line of a Kikimora Cloud instance. What the panel does with an organization and its projects,
4
+ this does from a terminal: members, projects, credentials, repositories, tools, agents, their tasks,
5
+ sessions, costs and logs.
5
6
 
6
7
  ```sh
7
8
  npm install -g @kikimoradev/kcloud
8
- kcloud login --url https://kikimora.example.com
9
+ kcloud login
9
10
  ```
10
11
 
12
+ `kcloud` acts on `https://cloud.kikimora.dev`, and `--url` or `KIKIMORA_CLOUD_URL` names another instance.
11
13
  `login` shows a code, opens the panel and waits until somebody approves the sign-in there. The token it
12
- receives is stored in `~/.kikimora-cloud/cli.json` with mode 0600, one profile per instance.
14
+ receives is stored in `~/.kikimora-cloud/cli.json` with mode 0600, one per instance address.
13
15
 
14
16
  ```sh
17
+ kcloud orgs list
15
18
  kcloud projects list
16
19
  kcloud agents list --project acme
17
20
  kcloud agents start acme/nightly
@@ -19,24 +22,26 @@ kcloud agents tasks add acme/nightly --title "Update the changelog" --descriptio
19
22
  kcloud agents logs acme/nightly --follow
20
23
  ```
21
24
 
22
- An agent is named as `<project>/<agent>`, or alone with `--project`, or by its id. Every command that
23
- reads takes `--json`, the two streams print NDJSON, and warnings go to stderr, so a pipeline can read
24
- stdout as it is. A secret is never taken from a flag: `--secret-file`, `--secret-stdin` or an environment
25
- variable carry it.
25
+ `kcloud` acts in your own organization. A platform admin picks another one with `kcloud orgs use <org>`,
26
+ `--org` or `KIKIMORA_CLOUD_ORG`. An agent is named as `<project>/<agent>`, or alone with `--project`, or by
27
+ its id. Every command that reads takes `--json`, the two streams print NDJSON, and warnings go to stderr,
28
+ so a pipeline can read stdout as it is. A secret is never taken from a flag: `--secret-file`,
29
+ `--secret-stdin` or an environment variable carry it.
26
30
 
27
- In a pipeline, `KIKIMORA_CLOUD_URL` and `KIKIMORA_CLOUD_TOKEN` replace the profile, and a token for that
28
- is created under Access tokens in the panel:
31
+ In a pipeline, `KIKIMORA_CLOUD_TOKEN` replaces the stored token, and a token for that is created under
32
+ Access tokens in the panel:
29
33
 
30
34
  ```sh
31
- export KIKIMORA_CLOUD_URL=https://kikimora.example.com
32
35
  export KIKIMORA_CLOUD_TOKEN=$KCLOUD_TOKEN
33
36
  kcloud agents tasks add acme/nightly --description "Release $GITHUB_REF_NAME" --yes --json
34
37
  ```
35
38
 
36
- `kcloud mcp` serves the same work to an MCP client over stdio, with the profile signed in here:
39
+ `kcloud mcp` serves the same work to an MCP client over stdio, with the instance, token and organization
40
+ `kcloud` itself would use:
37
41
 
38
42
  ```sh
39
43
  claude mcp add kcloud -- kcloud mcp
44
+ claude mcp add kcloud-acme -- kcloud mcp --org acme
40
45
  ```
41
46
 
42
47
  `kcloud <command> -h` describes any command. Exit codes: 0 for success, 1 for a refusal of the instance,