What's new in clickhousectl v0.3.0

Summary

clickhousectl v0.3.0 adds improvements aimed at agentic workflows, additional installation methods, OAuth for Cloud service queries, and custom configuration files for local servers. It detects coding-agent environments and defaults to JSON on stdout, uses gh-style exit codes, reads CLICKHOUSE_ credentials from a working-directory .env file, and hides deprecated API fields from CLI output. Cloud service queries can authenticate with OAuth without provisioning a Query Endpoint; idled services wake automatically, while stopped services fail with a start hint. For local development, selected versions resolve from installed binaries before network lookup, local use can put ClickHouse on PATH, and named XML, YAML, or YML files overlay built-in defaults. The release also adds Python installation options and extends local init with a postgres/ tree alongside clickhouse/.

Takeaways

1. 1

   Agent-oriented exit codes distinguish success, general errors, cancellation, and authentication requirements; JSON becomes the default stdout format when clickhousectl detects a coding-agent environment.

2. 2

   OAuth lets cloud service query run SQL without first provisioning a Query Endpoint. Queries wake an idled service automatically, but a stopped service fails and suggests running cloud service start.

3. 3

   Local server configuration files in ~/.clickhouse/configs/ may be XML, YAML, or YML and are overlaid on built-in defaults, so they only need to define changed settings.