@voltade/volty 0.1.16 → 0.1.18

package/dist/volty.js

@@ -354,9 +354,9 @@ function parseFlagTokens(props, rest, UsageError) {
       throw new UsageError(`unknown flag --${raw0}`);
     let raw = match[2];
     const next = rest[i + 1];
-    if (raw === undefined && valueBranch(prop).type !== "boolean" && next !== undefined && !next.startsWith("--")) {
+    const takes = valueBranch(prop).type === "boolean" ? next === "true" || next === "false" : !next?.startsWith("--");
+    if (raw === undefined && next !== undefined && takes)
       raw = rest[++i];
-    }
     if (prop.type === "array") {
       const list = input[flag] ?? [];
       list.push(...arrayItems(flag, raw, prop, UsageError));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@voltade/volty",
-  "version": "0.1.16",
+  "version": "0.1.18",
   "description": "Remote CLI for the Volty platform — run operations, trigger real agent wakes, and inspect LLM I/O over an API key.",
   "license": "UNLICENSED",
   "type": "module",

package/skill/volty-cli-ops/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: volty-cli-ops
-description: "Drive Volty's agent with the `volty` CLI: run a real agent turn in one command on either lane (a contact message or a staff session) and read what the model saw and did. Use whenever you need to exercise the live agent end to end: does an inbound trigger the right reply, learning or proposal, can Volty read or operate a connected system (CRM, MCP server, drive, channel), why did a tool call come back wrong. Reproducing a reported behaviour costs one command, so reach for it before theorising. Triggers: 'test the agent', 'trigger a wake', 'wake-sync', 'session-sync', 'ask Volty on prod', 'what did the agent do with X', 'run a real LLM turn', 'reproduce this inbound', 'can Volty see X?'."
+description: "Drive Volty's agent with the `volty` CLI: run a real agent turn in one command on either lane (a contact message or a staff session) and read what the model saw and did. Use whenever you need to exercise the live agent end to end: does an inbound trigger the right reply, learning or proposal, can Volty read or operate a connected system (CRM, MCP server, drive, channel), why did a tool call come back wrong. Reproducing a reported behaviour costs one command, so reach for it before theorising. Also use it to create or configure a web chat channel from Claude Code. Triggers: 'set up a web chat', 'change the web chat settings', 'test the agent', 'trigger a wake', 'wake-sync', 'session-sync', 'ask Volty on prod', 'what did the agent do with X', 'run a real LLM turn', 'reproduce this inbound', 'can Volty see X?'."
 ---
 
 # volty CLI
@@ -16,8 +16,11 @@ This skill says which lane to use and what to keep to on prod. The commands and
 ## Pick the lane
 
 - `debug wake-sync` sends a synthetic contact message into the org's sandbox: the contact lane.
+- `debug wake-sync --web-chat <channel id>` writes as a website visitor on a web chat channel, without the form's captcha: the contact lane on web chat. The chat is filed in the Sandbox inbox, where only testers see it, and Volty follows the web chat inbox's instructions, so you test that channel's setup without its staff seeing the test. You must be in the web chat channel's inbox.
 - `debug session-sync` runs a turn on the internal Volty chat as you: the staff lane.
 
+To create or change a web chat (its look, websites, the visitor's phone and email settings, the logo), use the `widgets` ops: `volty docs` has a "Setting up a web chat" section with the order to run them in. Read the settings back with `widgets get` after a change, and test the chat with `debug wake-sync --web-chat` before saying it works.
+
 Use the lane the behaviour was reported on. On the contact lane Volty declines to list internal records to a contact, as it should, so "can Volty read our CRM or MCP server" belongs on the staff lane; asked on the contact lane, that refusal looks like a broken feature.
 
 ## On prod