Introducing clickhousectl: the CLI for ClickHouse local and cloud (beta)

Al BrownApr 9, 2026

Source: Clickhouse
Published: Apr 9, 2026
Added to Yomu: Aug 28, 2026

Summary

ClickHouse released the beta version of clickhousectl, an official command-line interface designed to unify local operations and cloud infrastructure management for both humans and AI agents. The tool acts as a version manager that stores reusable binaries globally in ~/.clickhouse/versions/ while offering optional project directory scaffolding for SQL files. Developers and agents can run multiple isolated local server instances concurrently with automatic free-port detection and dedicated data directories. For ClickHouse Cloud, the CLI provides complete management coverage with structured JSON output, using read-only OAuth or scoped API key authentication to safeguard modifying operations. Additionally, the tool can install ClickHouse Agent Skills directly into supported coding agents to facilitate automated local and cloud interactions.

Context

The rise of agentic development requires infrastructure platforms to adapt to AI agents acting on behalf of users, expanding developer experience to include streamlined and predictable interfaces for LLMs across local development and cloud production environments.

Approach / What changed

ClickHouse launched clickhousectl for macOS and Linux, featuring version management, SQL project scaffolding, isolated multi-instance local server execution, ClickHouse Cloud management with JSON output, skill installation for coding agents, and separated OAuth and API key permissions.

Takeaways

clickhousectl operates as a version manager storing binaries in ~/.clickhouse/versions/ and can run multiple isolated local instances with automatic port detection.
All ClickHouse Cloud management commands support JSON output via the --json flag to facilitate programmatic parsing by scripts and AI agents.
Browser-based OAuth credentials provide read-only access for cloud inspection, while modifying and destructive operations require organization-scoped API keys.

Deployment Developer Experience LLMs Open Source

Read original post

Introducing clickhousectl: the CLI for ClickHouse local and cloud (beta)

Al BrownApr 9, 2026

Source: Clickhouse
Published: Apr 9, 2026
Added to Yomu: Aug 28, 2026

Summary

Context

Approach / What changed

Takeaways

clickhousectl operates as a version manager storing binaries in ~/.clickhouse/versions/ and can run multiple isolated local instances with automatic port detection.
All ClickHouse Cloud management commands support JSON output via the --json flag to facilitate programmatic parsing by scripts and AI agents.
Browser-based OAuth credentials provide read-only access for cloud inspection, while modifying and destructive operations require organization-scoped API keys.

Deployment Developer Experience LLMs Open Source

Read original post

Related reading

Clickhouse · Apr 16, 2026
April 2026 newsletter
ClickHouse 26.3 LTS introduces experimental materialized common table expressions, WebAssembly user-defined functions, and enables asynchronous inserts by default. Alongside the release, Alasdair Brown launched clickhousectl to manage local installations and cloud deployments with built-in agentic development features and authentication safeguards. User case studies show Goldsky accelerating historical blockchain backfills by twelve times through direct ClickHouse reads using Apache Arrow, replacing their prior Kafka and Avro architecture. Additionally, the engineering team redesigned the full-text search index with front-coding compression, a sparse lookup index, and adaptive posting lists to handle expensive random reads on object storage. ClickHouse also previewed community architecture patterns for lightweight SIEM setups using Clickdetect and Wazuh log collection.
Mark Needham
Clickhouse · Mar 27, 2026
How we’re building a data platform for a new user: agents
AI agents are emerging as autonomous database users that generate SQL, execute queries, and iterate in seconds. Because traditional analytics workflows built for human analysts cannot keep up with these rapid loops, ClickHouse is adapting its platform for agentic workloads. The proposed Agentic Data Stack combines LibreChat for conversational interfaces, ClickHouse with Model Context Protocol servers for the data layer, and Langfuse for observability. Supporting developer tooling includes chDB 4 with a Pandas-like API, IDE integrations, and ClickHouse Agent Skills to enforce database design best practices. Platforms like Anthropic and Character.AI already leverage ClickHouse's high-concurrency aggregation and real-time ingestion capabilities to handle massive data scales required by modern AI applications.
Al Brown
Clickhouse · Apr 16, 2026
Getting started with clickhousectl: the ClickHouse CLI for local and cloud
ClickHouse developers often face friction managing local versions, isolated instances, project scaffolding, and Cloud operations without relying on complex shell scripts. The open-source command-line tool clickhousectl addresses this by unifying local environment management and ClickHouse Cloud workflows. Locally, it downloads shared binaries, initializes standardized directory structures, and spins up named, isolated servers with automatic port assignments to facilitate upgrade testing. For cloud workflows, the CLI enforces a split authentication model where browser OAuth provides read-only access and API keys permit state mutations like service creation and scaling. Furthermore, the tool includes Claude Code agent skills covering best practices and deployment workflows, alongside support for CI/CD pipeline automation via environment variables and JSON output.
Al Brown
Clickhouse · Apr 29, 2026
Comparing ClickHouse versions with clickhousectl
Evaluating query performance differences across ClickHouse versions previously required managing Docker containers or manually downloading historical binaries from GitHub releases. The clickhousectl command-line interface simplifies this process by downloading specific ClickHouse binaries, running multiple background server instances concurrently with automatic port assignment, and executing queries across local environments. Users can copy table schemas between local instances by piping raw output from SHOW CREATE TABLE queries and replicate datasets using ClickHouse's remote table function. In a benchmark comparing ClickHouse 25.12 and 26.3 on an S3-backed Parquet dataset, version 26.3 introduced a Parquet metadata cache that reduced repeat query times from roughly 9 seconds to 1–2 seconds. System tables like system.server_settings and system.metrics enable operators to inspect cache configurations, eviction policies, and memory consumption directly.
Mark Needham