WeCue CLI

WeCue is the internal tool for browsing, playing, and recording production content. The public npm package contains only the cross-platform bootstrap, Google login, access check, and secure updater. It does not contain the WeCue Web, simulator, recorder, or other product implementation.

After login, an authorized account receives a short-lived signed download URL for the private product bundle. An unauthorized account never receives the manifest or a product download URL.

Install

Install on macOS, Linux, or Windows with Node.js 22 or newer:

npm install -g wecue

Product data is stored in ~/.wecue on macOS/Linux and %LOCALAPPDATA%\WeCue on Windows.

Commands

wecue login
wecue open
wecue --help
wecue --version

wecue login opens the independent WeCue Google login entry and checks WeCue access before requesting a product release. A new account may finish login in the waiting state until a WeCue administrator grants access; in that state no product bundle is downloaded.

wecue open starts a loopback-only local service, opens the Web interface, and keeps running until interrupted. It intentionally accepts no content ID. --port N selects a local port and --no-open suppresses browser launch.

Only --help and --version work offline. Every business command authenticates online and checks effective WeCue access before the API can issue the private manifest and five-minute product download URL. An available update is downloaded, SHA-256 and Ed25519 verified, safely extracted, atomically activated, and then the original command runs. After retries are exhausted, an authentication, authorization, update, or network failure stops the command; the launcher never falls back to an older installed bundle.

Agent output

Pass --json or set WECUE_OUTPUT=json for stable JSON Lines. Every line has schemaVersion: 1 and an event field. Terminal errors are written to stderr with:

{"schemaVersion":1,"event":"error","ok":false,"code":"E_NETWORK","message":"...","nextAction":"check_network"}

The useful terminal events are:

• auth.complete: login finished; inspect status and nextAction.
• access.waiting: login succeeded but an administrator must grant access.
• server.ready: the local Web is ready; use url and keep the process alive.
• error: the command stopped; inspect code and nextAction.

Recording

Browsing works in modern browsers. Recording is supported in current Chrome and Edge and uses the browser's system capture picker. WeCue records the selected tab's content audio, not the microphone. Takes remain only in the local browser profile and can be previewed, compared, downloaded, or deleted.

Web client

The private product bundle contains a precompiled React, TypeScript, and Vite client from app/client. Release builds archive only the local service and compiled public/ output; client source files, node_modules, and build tooling are not shipped.

The phone preview consumes the same device specifications and display-scale resolver as waku simulator at build time. Vite embeds those modules in the static client, so an installed WeCue bundle remains standalone.

Release maintainers

The release artifact embeds the compiled simulator kernel pinned by kernel.lock.json. Build it only through scripts/prepare_kernel.mjs, which uses a clean detached worktree at the locked commit.

WECUE_MANIFEST_PRIVATE_KEY=/secure/path/manifest-ed25519-private.pem \
WECUE_RELEASE_REVISION=2 \
  bash scripts/release_wecue_cli.sh --dry-run

The release script publishes to a dedicated GCS bucket with uniform access, public access prevention, and object versioning. The manifest private key and private product artifacts are never part of this repository or the npm package.