@controllerai/cli 0.2.3 → 0.2.4

package/README.md

@@ -157,24 +157,16 @@ different contents that claim an existing version.
 
 ## Configuration
 
-Environment overrides:
+`cai connect` stores everything the CLI needs. Two settings are worth knowing:
 
-- `CAI_API_URL`
-- `CAI_APP_URL`
-- `CAI_TOKEN`
-- `CAI_WORKFLOW`
-- `CAI_CONFIG`
+- `CAI_TOKEN` — pass a credential through the environment instead of the config
+  file. Useful in CI, scripts, and sandboxes.
+- `CAI_CONFIG` — use an alternate config file path, for example to keep a second
+  account separate.
 
-`CAI_API_URL`, `CAI_APP_URL`, and `--api-url` are transient process overrides. Authentication,
-workflow creation, and `cai use` do not copy them into the saved config. Pass the
-override again when needed; `cai doctor --api-url <url>` verifies that backend.
-
-The CLI derives product links when the API host has the `https://api.<host>`
-shape. For local or custom deployments, set `CAI_APP_URL` or add an `appUrl`
-field to the config file; when no safe app base is known, link fields are omitted.
-
-For local manifest integration tests only, `CAI_SKILLS_MANIFEST_URL` can point
-to HTTPS or a loopback HTTP URL. Hosted file URLs must share its origin.
+`cai use <workflowId>` pins your working workflow. Inside a project directory
+the pin is saved to `.cai.json` there, so parallel sessions in different
+directories never interfere.
 
 Run `cai doctor` to verify Node.js, authentication, API access, installed skills,
 and credential-file permissions.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@controllerai/cli",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Build and operate Controller AI workflows and agents from any AI coding agent",
   "type": "module",
   "bin": {