Bounded reads and one shared setup action

Human command surface#

echo-cli exposes twenty public commands. Each command has its own reference page in the CLI tree. The echo-mcp method names are a separate machine surface and are not CLI commands.

Every operational query is an explicit SELECT over a named column list. seed-profile is different by design: it sends the Weles account UUID and product fields to Echo Web's authenticated setup operation. Sensitive account, contact, campaign-message, prompt, and event-identity fields are never returned.

echo-cli capabilities
echo-cli seed-profile --account <uuid> --name <product> [--description <text>] [--niche <text>] [--platforms <comma-list>]
echo-cli analytics [days]
echo-cli chat-latency [days]
echo-cli experiments
echo-cli onboarding [--reset] [seed flags]
echo-cli onboarding-report
echo-cli blogs
echo-cli generations
echo-cli assets
echo-cli products
echo-cli product <id>
echo-cli personas [product_id]
echo-cli characters
echo-cli social-accounts
echo-cli outreach
echo-cli paid-ads
echo-cli market
echo-cli reliability [days]
echo-cli operations [days]

Configuration#

Read commands use the Supabase bindings below. seed-profile uses ECHO_WEB_BASE_URL and ECHO_INTERNAL_BEARER instead; the bearer value is the target Echo Web deployment's CRON_SECRET and stays in the Authorization header. Onboarding needs the Echo Web bindings only when seed flags are supplied.

NEXT_PUBLIC_SUPABASE_URL=
SUPABASE_SERVICE_ROLE_KEY=
ECHO_WEB_BASE_URL=https://echo.example.com
ECHO_INTERNAL_BEARER=

Output and state#

Successful reads and accepted adoption results serialize as indented JSON on stdout and exit 0. A refused adoption reports conflicting or rejected fields and exits 1. Only seed-profile and onboarding with seed flags can write, and both call Echo Web's single deterministic product operation. They never publish, message, advertise, synchronize a platform profile, or call a paid provider.