dsh-storage-mysql

The default JSON-file storage in DeepSeek Harness hits its limits under multi-process loads, containerized rollouts, or production uptime requirements: file locks become a bottleneck, crash recovery is best-effort at best, and data is invisible to other processes. dsh-storage-mysql replaces that backend with a contract-equivalent MySQL/InnoDB implementation. Every write is a single atomic SQL statement—once resolved the row is durable, survives crashes and reopens, and is immediately visible across processes.

The plugin exposes the same KV surface as dsh-storage-json: loadAll returns a transactional snapshot, putRecord performs an upsert, deleteRecord is idempotent, setGlobal updates unit-level metadata, and close releases the handle. Connection settings are read entirely from environment variables or a .env file; independent STORAGE_ keys take priority and fall back to shared MYSQL_ keys so the plugin can coexist with dsh-credentials-mysql and dsh-session-persistence-mysql on a single connection. On startup it runs idempotent CREATE TABLE IF NOT EXISTS and validates the schema version, failing closed on any downgrade rather than silently migrating.

If you run DeepSeek Harness as multiple instances or in containers, already operate a MySQL estate, or simply want to move the storage layer from local JSON files to an ACID-guaranteed relational database without touching business code, this plugin is a drop-in backend switch.