huginnDB: Instructions file for Claude Code

CLAUDE.md

Project context for Claude Code sessions on this repo. Skim this first; reach for README.md / CONTRIBUTING.md / SECURITY.md for the public-facing detail.

Identity

• HuginnDB — desktop database manager, Tauri 2 (Rust backend) + React + TypeScript frontend.
• Targets PostgreSQL, MySQL, SQLite, MongoDB, and Microsoft SQL Server. Inspired by HeidiSQL but minimal-UI / keyboard-first / Monaco-everywhere.
• Public repo: https://github.com/Alexfp28/huginnDB.
• License: MIT. Status: 1.29.x (stable; SemVer applies). MongoDB support landed in 1.1.0; the headless MCP connector (huginndb-mcp) landed across the 1.5–1.9 line (per-connection write policy in 1.9.0); HuginnDB Pulse (live server health/performance monitoring, MySQL + MongoDB) landed in 1.20.0; the AI panel (local-first, read-only, off by default — Settings → AI, assisted actions and agent mode) landed in 1.22.0. Since 1.23.0 every dialog declares one of three anatomies (prompt/panel/workbench) through DialogContent, and window.confirm is retired in favour of the in-app ConfirmHost — do not reintroduce either a hand-written header rail or a native prompt. Since 1.24.0 a database's own actions live on a database node (DatabaseNodeMenu, rendered by both explorers) rather than on the connection, and a shared origin is consumed by slice (tab_state::OriginScope — connections / environments / JSON Schemas, the one per-resource flag that defaults to on; see gotcha #83). Since 1.25.0 the workspace's current connection is derived from the focused tab by src/stores/session/focusFollowsTab.ts — do not add another setSelectedConnectionId call site to approximate it. Since 1.26.0 a VS Code colour theme can be imported (.vsix or a bare *-color-theme.json) or browsed and installed straight from Open VSX (Settings → Appearance's Extensions panel) — the registry URL is read from ThemePrefs inside the backend, never named by the frontend, the same addressing rule the AI panel already followed (see gotchas #87–#88). Since 1.27.0 the timeout on the reads the app issues on its own behalf (listing databases/tables, describing a relation, the liveness ping) is the user's — ConnectionPrefs::operation_timeout_secs globally, overridden by ConnectionProfile::operation_timeout_secs, resolved only through db::pool::operation_timeout — not a constant; a query the user runs stays unbounded. Since 1.28.0 the grid's server-side filter, projection, sort, collation and index hint are edited in one place, the inline query panel (src/components/grid/QueryPanel.tsx) — the advanced-filter dialog is gone, and its Result line and Explain are built by the same backend code the browse runs, so they cannot describe a different statement from the one that executes; do not bring back a second surface that edits the active filters. Since 1.29.0 a managed policy (crate::policy, docs/POLICY.md) can bound both people and their AI: the AI at the one bridge::exec::execute choke point (gotcha #94), people in each #[tauri::command] wrapper — never in the _inner core, which bridge::exec shares — with guard::HUMAN_POLICY classifying every registered command and a test failing on one that is unclassified or never calls the guard (gotcha #95). A new command that touches a database must state what the policy asks of it; the interface's locks are advisory and the backend refuses regardless (gotcha #96).