QueryFolio

SQL client desktop app built with Tauri 2 + SvelteKit. A lightweight alternative to JetBrains DataGrip.

Features

• MySQL / PostgreSQL / SQLite support (via sqlx)
• SSH tunnel with known_hosts verification
• Connection config in YAML, compatible with the sql-agent-mcp-server format
  • Secrets can stay in 1Password: the config YAML is fetched lazily via a getter command like op read "op://..."
• Query files per connection, auto-saved (~/.config/queryfolio/sqlfiles/<connection>/*.sql)
• CodeMirror 6 SQL editor with per-engine dialect, statement highlighting, Cmd+Enter to run the statement under the cursor, and schema-based autocompletion (table / column names)
• SQL formatting for SELECT statements (conservative: unsupported or unparsable statements are left untouched)
• Schema browser (TABLES pane) with lazy-loaded columns
• Results in tabs with pinning, a cell inspector, and CSV / TSV / JSON copy (formula-injection safe)
• Query cancellation while running
• Per-connection query history (searchable, stored locally with restrictive file permissions)
• psql-style meta commands (\l \dt \dv \dn \du \d [table]) translated to catalog queries, with MySQL / SQLite equivalents where possible
• readonly: true per connection rejects write statements (INSERT / UPDATE / DELETE / DDL, including CTE-wrapped DML) as a safety guard
• Auto LIMIT for SELECTs without one (default_limit, default 500)
• AI features (OpenAI): SQL generation from natural language, Fix with AI on query errors, EXPLAIN plan analysis with index suggestions, and explanation of selected SQL. Generated SQL is inserted into the editor, never auto-executed. Only the schema (table / column names), engine dialect, statements, and plans are sent — never query results
• Resizable panes: drag the dividers between the sidebars, editor, and results; sizes are persisted across restarts
• Window size / position restored across restarts

Setup

pnpm install
pnpm tauri dev

Configuration

Everything lives in one file: ~/.config/queryfolio/config.yml (see config.example.yaml). The sql_servers key accepts either the server list itself, or a source declaration pointing to where the list comes from:

# Inline (sql-agent-mcp-server compatible)
sql_servers:
  - name: dev-postgres
    engine: postgres
    host: localhost
    readonly: true   # optional: reject write statements on this connection
    ...

# Or fetch from 1Password (exactly one of command / env / file)
# sql_servers:
#   command: op read "op://development/queryfolio/config-yaml"

# Or from a file / an environment variable
# sql_servers:
#   file: ~/secrets/sql-servers.yaml
# sql_servers:
#   env: QUERYFOLIO_CONNECTIONS_YAML

# Optional
sqlfiles_dir: ~/queries
default_limit: 500   # auto-appended to SELECTs without LIMIT (0 = disabled)

# Optional: AI SQL generation (OpenAI)
ai:
  provider: openai   # only openai is supported for now
  api_key: sk-your-api-key
  model: gpt-5.1     # optional (default: gpt-5.1)
  base_url: https://api.openai.com/v1  # optional (for OpenAI-compatible APIs)

The ai: section can live at the top level of the local config file, or at the top level of the connection YAML fetched via a source declaration. When both exist, the fetched YAML wins — so the API key can stay in 1Password together with the connection secrets.

The QUERYFOLIO_CONFIG_YAML environment variable overrides the whole config file (for development; GUI apps launched from Finder do not inherit shell env vars).

Development

pnpm check                   # svelte-check
cd src-tauri && cargo test   # Rust unit tests
pnpm tauri build             # release build (macOS: signed with Developer ID via the tauri script; not notarized)

See AGENTS.md for architecture details.

License

MIT