@inworld/cli
v1.4.0
Published
Inworld CLI: auth, workspace, TTS, and MCP server entry point.
Readme
Inworld CLI
The inworld command-line interface: authentication, workspaces, TTS, and the inworld mcp server entry point.
Installation
Global Installation (Recommended)
npm install -g @inworld/cliAfter installation, you can use the CLI from anywhere in your system:
inworld --helpAudiobook performance
audiobook generate --concurrency N runs at most N chapter sessions (CLI limit
20, not an account quota). Check your account's effective quota and other TTS
traffic before increasing it. Chapters start longest-first but retain their
original output order; segments within a chapter share one sequential context.
Retries restart the whole chapter and can repeat paid synthesis. Completed
chapter MP3s are published atomically so failed encoding cannot create a
resumable partial file.
PCM is written after each segment rather than held for the whole chapter. A segment is capped at 32 MiB of decoded audio (concatenation can temporarily double that buffer), with an 8 MiB WebSocket frame limit. Connections/context creation time out after 30 seconds, synthesis after 120 seconds without audio or 10 minutes total per segment. A failed session is terminated before retry; voice/model, segment size, encoding and chapter-context semantics are unchanged.
When launched as a Node child with IPC, the CLI emits best-effort
audiobook-diagnostic version 1 events: fixed phase/outcome/error categories and
numeric duration, chapter/segment index, attempt and audio bytes. No book text,
credentials or server message is included. Diagnostics drop under IPC backlog
(at most 32 pending); they never block or fail a render. Normal CLI invocation
needs no IPC. A consumer must whitelist fields before logging them.
Offline verification (no credentials or paid synthesis):
npm run build
npm test -w @inworld/cli -- tests/commands/audiobook tests/services/tts_websocket.test.tsThe generation tests use a fake TTS session and encoder, including 13 chapters at concurrency 8. They verify scheduling, original assembly order, bounded concurrency and failed-output cleanup, not production throughput or audio quality.
