lazydb

Project status: LazyDB is currently in beta. The core database workspace, connection management, SQL execution, and coding-agent interfaces are usable, but LazyDB is not yet a production-ready replacement for DataGrip.

Quickstart

Press F2 anywhere in the workspace to open the global Omni Bar for commands, connections, consoles, tables, and navigation. F1 or ? opens contextual help; F6 opens the console manager; F7 opens SQL execution history; F8 opens notification history; and F9 opens the Update Center. See the Omni Bar guide and the complete keyboard reference.

SQL consoles can be opened without configuring or connecting a database. You can write, format, save, and reopen SQL while offline. Binding a target does not connect automatically; running SQL establishes the selected connection and continues the execution.

Installing and running LazyDB

For a ready-to-use MariaDB instance with broad test data-type coverage, see the MariaDB test database guide.

Run the following on Mac or Linux to install LazyDB

curl -fsSL https://lazydb.yelog.org/install.sh | sh

Run the following on Windows to install LazyDB:

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "irm https://lazydb.yelog.org/install.ps1.txt -ErrorAction Stop | iex"

After an interactive installation, the installer can open the LazyDB MCP setup wizard. It supports user-level and project-level configuration and shows the target file before writing it. To defer this step, run lazydb mcp setup later, or use --mcp-setup skip with the Unix installer.

The Windows installer supports 64-bit Windows (MSVC), downloads the release metadata and ZIP archive over HTTPS, verifies the SHA-256 checksum, and adds %LOCALAPPDATA%\LazyDB\bin to the user PATH. No administrator privileges are required. Open a new terminal after installation. To install the beta channel, set $env:LAZYDB_CHANNEL = "beta" before running the command.

The command downloads and executes a script from the LazyDB site. The .txt endpoint is generated from the same installer source, but served as text for PowerShell compatibility. Review the installer source if needed, or download the Windows ZIP from the latest GitHub Release.

For troubleshooting or environments where piping scripts to Invoke-Expression is unsuitable, run the following in PowerShell. This also executes downloaded code; saving it to a file does not authenticate the installer.

& {
    $ErrorActionPreference = 'Stop'
    $installer = Join-Path ([IO.Path]::GetTempPath()) (
        [IO.Path]::GetRandomFileName() + '.ps1'
    )
    try {
        Invoke-WebRequest -Uri 'https://lazydb.yelog.org/install.ps1' `
            -UseBasicParsing -OutFile $installer
        if ((Get-Item -LiteralPath $installer).Length -eq 0) {
            throw 'Downloaded installer is empty.'
        }
        powershell.exe -NoProfile -ExecutionPolicy Bypass -File $installer
        if ($LASTEXITCODE -ne 0) {
            throw "LazyDB installer failed with exit code $LASTEXITCODE."
        }
    } finally {
        Remove-Item -LiteralPath $installer -Force -ErrorAction SilentlyContinue
    }
}

After installation, configure database access for Claude Code, Codex, or OpenCode from the target project:

lazydb mcp setup

Uninstalling LazyDB

Native installations can be inspected without changes and then removed with the CLI:

lazydb uninstall --dry-run
lazydb uninstall

The default uninstall removes the LazyDB launcher, native releases, current release link, installation metadata, and the PATH block managed by the LazyDB installer. It preserves connection profiles, encrypted credential material, settings, workspace files, SQL files, and unknown files. Use --yes for a non-interactive uninstall. Use --json with --dry-run or --yes for a machine-readable report.

--purge additionally removes the allowlisted LazyDB data files after profile and credential checks. It may remove saved connection definitions, local credential keys, settings, workspace state, and update-check state. Unknown files and database files are preserved. System keyring entries are removed only when they are referenced by valid LazyDB profiles and the native secret store is available:

lazydb uninstall --purge --dry-run
lazydb uninstall --purge

Uninstall does not modify project MCP configuration. Remove the lazydb entry from .mcp.json, .codex/config.toml, or opencode.json[c] in each project before or after uninstall. Homebrew, Cargo, and system-package installations must be removed through their original package manager. Windows uninstall is not provided by the native POSIX command yet. If installation metadata is missing or paths no longer match the recorded native installation, uninstall stops without deleting anything and reports the paths that need manual review.

The setup command uses a project-scoped MCP configuration and denies database writes by default. It does not install a coding agent or copy credentials. Native script installers may offer an opt-in reminder on an interactive first install. Use --mcp-setup skip or LAZYDB_MCP_SETUP=skip for unattended runs; the prompt never changes configuration automatically because the installer does not know which project should receive the MCP entry.

LazyDB can also be installed via Homebrew, Cargo, or by building from source. See

# install using Homebrew
brew install yelog/tap/lazydb

Each GitHub Release contains many executables, but in practice, you likely want one of these:

• macOS
  • Apple Silicon/arm64: lazydb_xxx_aarch64-apple-darwin.tar.xz
  • x86_64 (older Mac hardware): lazydb_xxx_x86_64-apple-darwin.tar.xz
• Linux
  • x86_64: lazydb_xxx_x86_64-unknown-linux-gnu.tar.xz
  • arm64: lazydb_xxx_aarch64-unknown-linux-gnu.tar.xz

For example, on Apple silicon macOS with v0.1.0-beta.2:

tar -xJf lazydb_0.1.0-beta.2_aarch64-apple-darwin.tar.xz
mkdir -p "$HOME/.local/bin"
cp lazydb_0.1.0-beta.2_aarch64-apple-darwin/lazydb "$HOME/.local/bin/lazydb"
chmod +x "$HOME/.local/bin/lazydb"
lazydb version

Ensure $HOME/.local/bin is in PATH. To upgrade a manually installed binary offline, download and verify the new archive, extract it, and repeat the cp step with the new versioned directory. Native script installations should use lazydb update when network access is available; package-manager installations must be upgraded by their owning package manager.

Features

• Database Explorer: Browse databases, schemas, tables, views, indexes, foreign keys, triggers, routines, sequences, and types where supported by the driver. Redis uses a dedicated key-space browser rather than a SQL catalog.
• Users & Roles: Relational connections end their first explorer level with a Users & Roles group listing database users and roles with distinct icons and colours across the Nerd Font, Unicode, and ASCII icon modes. Pressing Enter opens a dedicated, read-only DDL tab titled name@connection that has no Data/DDL selector and reuses the relation DDL editor, so syntax highlighting, scrollbars, mouse selection, and Vim bindings behave identically. PostgreSQL lists cluster roles from pg_roles; MySQL and MariaDB list server accounts with their host; SQL Server lists the bound database's users and roles; Oracle lists the connection's service users and roles. SQLite shows an explicit "not supported" notice, Redis has no such group, and passwords or password hashes are never reproduced.
• Capability-aware catalog editor: Explorer a creates supported children and e edits directly selected objects. PostgreSQL exposes the broadest catalog editor (schema, table, column, index, constraints, views, materialized views, sequences, databases, and roles); Oracle, MySQL, MariaDB, SQL Server, and SQLite expose their currently imple