Install harlequin with Homebrew, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• harlequin

Project history

The public repository started in May 2023 with early commits for a working CLI, schema sidebar, query editor, and data viewer. The 0.0.x changelog shows a fast iteration cycle: query execution became asynchronous, SQL files could be opened and saved from the editor, DuckDB extension support landed, multiple editor buffers and multiple result tabs appeared, and database-file workflows gained read-only and export features.

Version 1.0.0, tagged in September 2023, marked the point where the core terminal database-client experience had settled enough for a named milestone. Subsequent development broadened Harlequin from a DuckDB-first SQL TUI into a general database client: the official docs describe adapter plug-ins as the generic interface to databases and list core and community adapters beyond the built-in DuckDB and SQLite support.

Adoption history

Harlequin's adoption path follows the DuckDB and terminal-UI communities: it is installable with Python tooling, documented as having a Homebrew formula, and packaged in Homebrew and Nix in the supplied package-manager facts. Its README also notes that the Homebrew formula bundles several adapter packages, which made the formula attractive for users who wanted a single terminal SQL client with more than DuckDB support.

The project attracted package-manager attention because it sits at the intersection of several popular command-line trends: local analytical databases, terminal user interfaces, Python application packaging, and pluggable database adapters.

How it is used

Harlequin is run as a command-line application, commonly with no arguments for an in-memory DuckDB session or with database paths/connection strings for concrete databases. Users can pass adapter options from the shell, keep profiles in TOML config files, edit and execute SQL in a terminal editor, browse catalogs, and export result data.

The adapter model is central to everyday use. The official adapter docs describe DuckDB as the default, SQLite as built in, and additional adapters as Python packages discovered at runtime, so package installs often matter as much as the core executable.

Why package nerds care

Harlequin is interesting to package nerds because it packages a rich, stateful terminal application rather than a small single-purpose CLI. Formula maintainers have to care about Python runtime behavior, optional adapters, database client dependencies, and config discovery.

It also illustrates a newer class of Homebrew formula: a Python TUI that competes with native database CLIs by bundling editor, catalog, and result-viewer behavior into one command while still remaining scriptable enough to live in terminal workflows.

Timeline

• 2023-05: Public repository history begins with a working CLI, schema sidebar, query editor, and data viewer.
• 2023-06: Early 0.0.x releases add multi-database catalog behavior, read-only database opening, MotherDuck support, and terminal key-binding improvements.
• 2023-09: Version 1.0.0 is tagged after rapid 0.0.x iteration.
• 2025-01: Version 2.0.0 is tagged, continuing the project after the initial SQL TUI became a broader adapter-based database client.
• 2026-03: Version 2.5.2 is tagged in the upstream repository.

Related projects

• DuckDB is the default database target and part of Harlequin's early identity.
• Textual is the Python terminal UI framework behind Harlequin's interactive interface.
• Adapter packages such as harlequin-postgres, harlequin-mysql, and harlequin-odbc extend the core client to additional database systems.

Sources

• Official Harlequin documentation for installation, configuration, database adapters, and DuckDB usage.
• Official Harlequin repository and release/changelog history.