moshcode 0.67.0 → 0.68.0

package/README.md

@@ -14,28 +14,6 @@ curl -fsSL https://moshcoding.com/install.sh | sh
 Zero-dependency ESM — all it needs is Node.js 18+. Later: `… | sh -s -- update`
 to upgrade, `… | sh -s -- remove` to uninstall.
 
-## What is in this repo
-
-The CLI is the root package — `bin/`, `src/`, `plugins/` — and that is what
-`npm publish` and the installer above ship. Two apps live alongside it:
-
-| path | what it is | deployed as |
-|---|---|---|
-| `apps/pwa` | the Moshpit registry and account app | pit.moshcode.sh, app.moshcode.sh |
-| `apps/qryptchat-web` | QryptChat, the post-quantum messenger | qrypt.chat |
-
-One repo, but **not one dependency tree**. Each app installs itself, with its
-own lockfile, and the root `pnpm install` does not reach into either. That is
-deliberate on both counts and `pnpm-workspace.yaml` says why. The practical
-rule: run `pnpm install` in the directory you are working in, not at the root
-and not the other way round.
-
-The two apps share a feature rather than code — a person can sign in to
-QryptChat by proving they hold a Moshpit name, which `moshcode name link`
-produces the proof for. The shared half of that is still duplicated in both
-trees; see `pnpm-workspace.yaml` for what has to be fixed before it can be
-lifted into `packages/`.
-
 ## Commands
 
 `moshcode help <command>` drills into any of these — flags, examples and all.
@@ -722,6 +700,35 @@ engines, `mcpjam` tells you whether that server is healthy first — health
 checks, OAuth conformance, tool-surface diffing, and structured triage from the
 terminal or CI. Re-running `moshcode install mcpjam` is also its upgrade path.
 
+### ElevenLabs — Eleven Agents, voices, and speech
+
+```sh
+moshcode install elevenlabs       # npm i -g @elevenlabs/cli
+
+moshcode elevenlabs auth login    # PKCE OAuth, stored in the system keyring
+moshcode elevenlabs agents list
+moshcode elevenlabs agents push   # upload local agent configs to the platform
+moshcode elevenlabs text-to-speech convert …
+```
+
+[ElevenLabs](https://elevenlabs.io/docs/eleven-agents/operate/cli)' CLI manages
+**Eleven Agents** — conversational voice agents you define in files and
+`push`/`pull` against their platform, alongside the knowledge bases, tools,
+tests and phone numbers those agents use. The same binary reaches the rest of
+the API: voices, text-to-speech, dubbing, transcription, music, and workspace
+usage.
+
+They are agents in a different sense than the ones under `/agents`: you deploy
+them and callers talk to them, rather than handing your terminal to one. That is
+why it sits here with the workflow CLIs — every subcommand runs one request and
+exits, so it pipes like the rest of the roster. `--format json` (the default
+when stdout is not a TTY) and `--query` (JMESPath) are what a script wants.
+
+The npm package is a small shim over a native binary shipped as an optional
+dependency, so install it without `--omit=optional` or the `elevenlabs` on your
+PATH will refuse to run. Re-running `moshcode install elevenlabs` is its upgrade
+path.
+
 ### Alchemy — onchain data, wallets, and x402
 
 ```sh
@@ -1460,6 +1467,7 @@ chmod +x deploy.mosh
 | `mcpjam(args…)` | drive the MCPJam CLI (test, debug, and validate MCP servers) |
 | `spinifex(args…)` | drive the Spinifex CLI (`spx` — AWS-compatible cloud on your own hardware) |
 | `alchemy(args…)` | drive the Alchemy CLI (onchain data, apps, wallets, x402) |
+| `elevenlabs(args…)` | drive the ElevenLabs CLI (Eleven Agents, voices, TTS, dubbing) |
 | `trade(args…)` | look up tickers, inspect markets, preview/place Alpaca orders |
 | `stocks(args…)` | research tickers via advis0r (`stocksRead` returns the data) |
 | `crypto(args…)` | research crypto pairs via advis0r (`cryptoRead` returns the data) |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "moshcode",
-  "version": "0.67.0",
+  "version": "0.68.0",
   "type": "module",
   "description": "moshcode — a metal wrapper for coding engines and native UGig/CoinPay workflow CLIs, with OpenPRD and moshscript",
   "repository": {
@@ -18,7 +18,7 @@
   "scripts": {
     "start": "node bin/moshcode.mjs",
     "demo": "node bin/moshcode.mjs run examples/alive.mosh",
-    "test": "node --test \"test/**/*.test.mjs\" \"tests/**/*.test.mjs\" \"apps/pwa/test/**/*.test.mjs\""
+    "test": "node --test"
   },
   "files": [
     "bin",

package/src/commands.mjs

@@ -683,6 +683,7 @@ const COMMANDS = [
   cliVerb("mcpjam", "drive the MCPJam CLI (test, debug, and validate MCP servers)"),
   cliVerb("spinifex", "drive the Spinifex CLI (spx — AWS-compatible cloud on your own hardware)"),
   cliVerb("alchemy", "drive the Alchemy CLI (onchain data, apps, wallets, x402)"),
+  cliVerb("elevenlabs", "drive the ElevenLabs CLI (Eleven Agents, voices, TTS, dubbing)"),
   cliVerb("trade", "look up tickers, inspect markets, and preview/place Alpaca orders"),
   cliVerb("pwd", "print the current repo/location"),
 

package/src/tools.mjs

@@ -310,6 +310,32 @@ export const TOOLS = {
     // place to hear it than an install that succeeded.
     install: { cmd: "npm", args: ["install", "-g", "@alchemy/cli"] },
   },
+  elevenlabs: {
+    desc: "ElevenLabs — build, configure and deploy Eleven Agents (plus voices, TTS, dubbing, and the rest of the API)",
+    bin: "elevenlabs",
+    // A workflow tool rather than an engine, despite the name. ElevenLabs calls
+    // these "agents", but they are conversational voice agents you configure and
+    // deploy to their platform: `elevenlabs agents push/pull/list` is an API
+    // client that runs one request and exits. `/agents` promises to hand the
+    // terminal to a live session, and there is no session here to hand it, so
+    // this belongs next to the other workflow CLIs. Docs:
+    // https://elevenlabs.io/docs/eleven-agents/operate/cli
+    //
+    // Authenticate once with `moshcode elevenlabs auth login` — a PKCE OAuth
+    // flow that stores the credential in the system keyring (falling back to a
+    // file under ~/.config), rather than an env var to keep exporting.
+    //
+    // The published package is a tiny Node shim; the real CLI is a native
+    // binary shipped per platform as an OPTIONAL dependency
+    // (@elevenlabs/cli-linux-x64 and friends). That is why the install spec is
+    // the plain global install with no flags: an install run with
+    // `--omit=optional` or `--no-optional` still succeeds and still puts
+    // `elevenlabs` on PATH, but every invocation then dies with "the platform
+    // package is not installed". `npm install -g` is idempotent and the CLI
+    // ships no updater of its own, so this doubles as the upgrade path and
+    // there is deliberately no `upgrade` key.
+    install: { cmd: "npm", args: ["install", "-g", "@elevenlabs/cli"] },
+  },
 };
 
 /** Resolve a name to `[key, tool]`, or null. */