Desktop enables os-keyring and provisions the data-encryption key in the OS keychain during the data security upgrade, but dbx-mcp/dbx-cli package builds compiled without any keyring backend (the feature became opt-in for the Linux cross builds), so every desktop-migrated profile made the MCP fail with DATA_MIGRATION_REQUIRED forever - the error even pointed users back at a migration they had already completed. - dbx-mcp gains an os-keyring forwarding feature; the native macOS and Windows MCP and CLI legs of the packages release build with it, Linux zigbuild legs keep the managed .dbx/secret.key fallback - LocalBackend::open now separates 'key unreadable in this process' (SECRET_KEY_UNAVAILABLE with the DBX_SECRET_KEY_FILE/DBX_SECRET_KEY escape hatch) from genuinely pending legacy data, keeping the DATA_MIGRATION_REQUIRED contract for the latter (test covered)
Crates
Rust crates for DBX live here.
Directories
dbx-core/- application orchestration: connections, queries, schema operations, data workflows, AI tools, administration, persistence, safety, and host services.dbx-types/- shared connection, query, metadata, and serialization contracts; generated database identities.dbx-sql/- SQL parsing, dialects, analysis, risk classification, DDL/DML generation, and schema diff planning.dbx-drivers/- native database adapters, database Agents, tunnels, execution budgets, and driver lifecycle.dbx-formats/- data formatting and file encoders, independent of database connections.dbx-ai-provider/- AI provider clients, CLI adapters, streaming, and token usage.dbx-plugin-runtime/- plugin packages, signatures, marketplace, subprocess sessions, and host requests.dbx-platform/- shared process, path, proxy, download, version, and host-prompt primitives.dbx-web/- the Docker/web backend service binary published asdbx-web.dbx-cli/- the command-line application.dbx-mcp/- the MCP service library and binary.dbx-sqlite-worker/- the isolated SQLite file-host worker and protocol.
The workspace root is defined in the repository-level Cargo.toml.
See ARCHITECTURE.md for dependency rules, compatibility exports, feature selection, and validation commands.