CLI status
Why the hand-written CLI is not a supported launch interface and what to use instead.
The hand-maintained CLI is not a launch interface. Use POST /v1/sql, MCP, or the generated
TypeScript and Python SDKs; all use the same grant resolution, SQL validation, query isolation, and
receipt path.
This page remains as an explicit scope decision so catalogue breadth is not mistaken for a shipped command-line experience. A future CLI should wrap the public API and generated SDK rather than add a broader credential or data path.
For shell automation, use curl --fail-with-body with COMBINED_API_URL, COMBINED_TOKEN, and an
explicit Account UUID. The installed Agent Skill includes a small
context.sh helper for documentation, catalogue, and query calls; it is a transparent HTTP helper,
not an independent privileged client.