@runtypelabs/cli 2.25.2 → 2.28.1

package/README.md

@@ -27,6 +27,26 @@ Or run without installing:
 npx @runtypelabs/cli@latest <command>
 ```
 
+### Automatic updates
+
+Global installations check npm for a new stable release once per hour. When one is available,
+the CLI installs the exact version in the user-owned `~/.runtype/cli/versions/` cache, verifies
+that it starts and reports the expected version, and activates it atomically for the next
+invocation. It never rewrites your npm, pnpm, or yarn global prefix while a command is running.
+
+```bash
+runtype update             # Check and install now
+runtype update --check     # Check without installing
+runtype update --rollback  # Return to the previous healthy version
+```
+
+Automatic installation is disabled for CI, source checkouts, project-local installations, and
+`npx`/`pnpm dlx` runs so pinned and ephemeral executions remain reproducible. Set
+`RUNTYPE_DISABLE_AUTO_UPDATE=true` to keep using the package-manager-installed version (including
+an intentionally pinned global version), or
+`RUNTYPE_DISABLE_UPDATE_CHECK=true` to keep the active managed version without checking for more
+updates.
+
 ## Start Here
 
 The easiest way to try Runtype starting at the CLI is to run a Marathon task. If you are not logged in yet, the CLI will guide you through login or signup first.
@@ -66,7 +86,54 @@ runtype login
 runtype login --api-key <key>
 ```
 
-### 2. Work With Agents, Flows, and Records
+### 2. Connect Your Coding Agent to Runtype MCP
+
+Use the CLI in this first session, then install the durable hosted MCP connection for your current
+coding agent:
+
+```bash
+runtype install-mcp
+```
+
+The command detects Claude Code, Codex, Cursor, Gemini CLI, OpenCode, or VS Code; installs the
+matching Runtype agent skill; configures the user-level hosted MCP server; and starts client-owned
+browser OAuth when the client supports it. Follow its final instruction to restart or reload the
+coding agent. After restart, prefer Runtype MCP and use the CLI as a fallback rather than as the
+primary integration.
+
+If several coding agents are installed and the current one cannot be identified from its
+environment, select one explicitly (for example, `runtype install-mcp --agent codex`). Use
+`--dry-run` to inspect the plan and `--force` only to replace a conflicting server already named
+`runtype`.
+
+You can also discover and call either hosted MCP server directly from the shell without registering
+individual tool commands:
+
+```bash
+# Primary MCP (default)
+runtype mcp tools
+runtype mcp inspect create_flow
+runtype mcp call list_flows -F limit=20
+
+# Complete JSON input from a file or stdin
+runtype mcp call create_flow --input arguments.json --json
+cat arguments.json | runtype mcp call create_flow --input - --json
+
+# Code Mode MCP
+runtype mcp tools --server code
+runtype mcp call execute --server code -F code=@query.js --json
+```
+
+`-f key=value` always sends a string. `-F key=value` parses JSON scalar, array, and object values;
+prefix the value with `@` to read it from a file or use `@-` for stdin. Use `--json-body` for an
+inline complete arguments object. The `call` command sends the provided name directly to MCP, so
+new server tools work without a CLI release. Tool calls wait up to 930 seconds by default so
+long-running flows can complete; use `--timeout <ms>` to choose a different deadline. The separate
+`runtype tools` command manages saved runtime tools. Run `runtype auth login` first or set
+`RUNTYPE_API_KEY` before using `--input -` or `-F key=@-`; the CLI will not put an interactive login
+prompt on a stream that contains tool arguments.
+
+### 3. Work With Agents, Flows, and Records
 
 ```bash
 # List available agents
@@ -88,7 +155,7 @@ runtype dispatch --flow <flow-id> --variable customerName=Alyss --variable prior
 runtype records create --name "My Record" --type "document"
 ```
 
-### 3. Run Multi-Session Agent Tasks
+### 4. Run Multi-Session Agent Tasks
 
 Use `runtype marathon` to run long-running tasks with real-time streaming output. If you want to try it without installing first, use `npx @runtypelabs/cli@latest marathon ...`. Swap the agent, model, tools, and execution environment depending on whether you want to research, edit code, or build and ship something end-to-end.
 
@@ -682,6 +749,38 @@ View analytics and execution results.
 | `analytics stats`   | Show account statistics                                              |
 | `analytics results` | List execution results (`--flow`, `--record`, `--status`, `--limit`) |
 
+### `runtype update`
+
+Manage CLI updates.
+
+| Command             | Description                                   |
+| ------------------- | --------------------------------------------- |
+| `update`            | Check npm and install the latest stable CLI   |
+| `update --check`    | Check for a newer version without installing  |
+| `update --rollback` | Activate the previous healthy managed version |
+
+### `runtype install-mcp`
+
+Install the current coding agent's Runtype skills and user-level hosted OAuth MCP
+connection. Use `--agent <id>` when detection is ambiguous, `--dry-run` to inspect the
+plan, and `--force` only to replace a conflicting user-level server named `runtype`.
+Follow the final OAuth and restart instructions before expecting MCP tools in the running
+agent session.
+
+### `runtype mcp`
+
+Use the hosted MCP servers directly from scripts and terminals. `mcp tools` lists the live catalog,
+`mcp inspect <name>` shows the current input/output schemas, and `mcp call <name>` invokes any tool
+name without local registration. The standard MCP is the default; pass `--server code` for Code
+Mode. `--json` preserves the complete MCP result for piping into tools such as `jq`.
+
+The command follows `--api-url` for the standard endpoint and selects the matching production,
+staging, or local Code Mode host. Local development can override endpoint inference with
+`RUNTYPE_MCP_URL` and `RUNTYPE_CODE_MCP_URL`.
+
+Tool calls default to a 930-second client timeout, slightly above Runtype's maximum flow runtime.
+Pass `--timeout <ms>` to use a different positive millisecond deadline.
+
 ## Configuration
 
 ```bash