@vatio-ai/cli 0.47.0 → 0.47.1

package/README.md

@@ -1,44 +1,86 @@
 # @vatio-ai/cli
 
-The CLI for [Vatio](https://vatio.ai) — deploy and manage AI agent workspaces.
+The CLI for [Vatio](https://vatio.ai) — a production runtime for
+customer-facing AI agents. Describe an agent in one `vatio.yml` and deploy it to
+web chat, WhatsApp and Instagram; Vatio runs the conversation, the contacts, the
+identity, the safeguards and the handoff to a human.
 
 ```bash
 npx @vatio-ai/cli init my-agent
 npx @vatio-ai/cli push
 ```
 
-No runtime to install first: if you have Node, you have this.
+No runtime to install first: if you have Node 20 or newer, you have this.
 
 The package is `@vatio-ai/cli`; the command it installs is `vatio`. So
 `npm install -g @vatio-ai/cli` gives you `vatio push`, and `npx @vatio-ai/cli push`
 is the same thing without installing anything.
 
+## If you are a coding agent
+
+```bash
+vatio mcp     # MCP over stdio
+vatio docs    # the whole developer contract as markdown, live from Vatio
+```
+
+`vatio mcp` is the short path: it hands you the contract and the deploy commands
+over MCP, with no browser step. Failing that, `vatio docs` prints the same
+contract that [docs.vatio.ai/docs.md](https://docs.vatio.ai/docs.md) serves, and
+`vatio docs --save` writes it next to the workspace.
+
+Don't guess `vatio.yml` keys. Unknown root keys fail validation, and the rules
+that judge a workspace live on the server — so the printed contract is the
+current one by construction.
+
 ## What a workspace is
 
-A directory with a `vatio.yml` in it. That file says which Vatio workspace the
-directory deploys to, what the agent does, and how the widget looks; `tools/`,
-`lib/` and `auth/` next to it are plain JavaScript the agent runs.
+A directory with a `vatio.yml` in it:
+
+```text
+support-agent/
+  vatio.yml          # required: the agent, its tools, its knowledge
+  tools/*.yml        # one HTTP request each, described in YAML
+  identity.pub       # public key that verifies the JWT saying who a visitor is
+```
 
-Nothing constrains where that directory lives — an agent can sit inside the
-repository of the backend it calls, and every command except `init` finds it by
-walking up from the current directory. There is no `--workspace` flag.
+Only create the files you need. Nothing constrains where that directory lives —
+an agent can sit inside the repository of the backend it calls, and every
+command except `init` finds it by walking up from the current directory. There
+is no `--workspace` flag.
 
 ## Commands
 
 ```
-init [SLUG] [--name NAME]   Create vatio.yml here, and the remote to match
-login [--base-url URL]      Authorize this machine in a browser
+init [SLUG]                 Create vatio.yml here, and the remote to match
+login | logout              Authorize this machine in a browser, or forget it
+doctor                      Node, config, workspace and token status
+
 push [--env NAME]           Validate the workspace, then update a preview
 publish [--env NAME]        Promote a preview to live
 diff [--env NAME]           What this directory would change
 status                      Preview and live deployment state
 rollback                    Restore the previous live deployment
 tools check                 Validate the workspace against Vatio's contracts
-secrets list|set|rm         Credentials your tools read as ctx.env
-tokens list|create|revoke   Publishable tokens for the widget and the SDK
-widget [--env NAME]         What the platform enforces, and the tokens there are
-config show|set|unset       base_url and token, per developer
-doctor                      Node, config, workspace and token status
+
+chat "message" [--env NAME] Talk to your own agent; the token is the identity
+chat transcript|debug|reset|destroy
+
+kb list|show|create|rm       Knowledge bases
+kb write|cat|rm-entry        Entries, from a file or stdin
+kb follow|unfollow|refresh   Read a site into a base, nightly
+
+secrets list|set|rm          Credentials your tools read
+tokens list|create|revoke    Publishable tokens for the widget and the SDK
+widget [--env NAME]          What the platform enforces, and the tokens there are
+auth --new-key               Keypair that signs the visitor's JWT
+
+whatsapp ...                 Shared preview number, or your own business number
+instagram ...                Shared sandbox, or your own account
+
+docs [--save [PATH]]         The whole developer contract
+mcp                          Speak MCP over stdio, for a coding agent
+issue "what should change"   Send a change request, workspace attached
+config show|set|unset        base_url and token, per developer
 ```
 
 `--env NAME` targets a deployment: `live`, `preview`, or a named preview like

package/package.json

@@ -1,8 +1,14 @@
 {
   "name": "@vatio-ai/cli",
-  "version": "0.47.0",
+  "version": "0.47.1",
   "description": "Vatio CLI — deploy and manage Vatio agent workspaces",
-  "keywords": ["vatio", "agent", "ai", "cli", "deploy"],
+  "keywords": [
+    "vatio",
+    "agent",
+    "ai",
+    "cli",
+    "deploy"
+  ],
   "homepage": "https://vatio.ai",
   "bugs": "https://docs.vatio.ai",
   "license": "SEE LICENSE IN LICENSE.txt",