Cursor for SQL — Introducing Agent Mode in Dolt Workbench¶
Source: DoltHub Blog
Author: DoltHub team
Date: 2026-02-09
Ingested: 2026-06-03
Summary¶
DoltHub officially introduces agent mode in the Dolt Workbench — a Cursor-like agentic chat interface that allows users to safely interact with Dolt, MySQL, and Postgres databases. The article demonstrates the feature side-by-side: first with MySQL (no version control, dangerous writes), then with Dolt (version-controlled, safe writes with visual diff and commit confirmation).
Key Concepts¶
Agent Mode for SQL Databases¶
The agent chat panel is accessible from anywhere in the workbench. Users give natural language instructions, and the agent executes SQL queries (via Bash tool calls for MySQL, or the Dolt MCP Server for Dolt databases). Each tool call is expandable to see exactly what actions were taken.
MySQL vs Dolt Comparison¶
- MySQL: Agent executes INSERT statements with no way to verify changes before they happen. No diff view, no rollback. User can only query for new data after the fact. "Dangerous" — no mechanism to see or verify agent changes.
- Dolt: Agent writes trigger visual changes immediately. Table names highlighted in yellow. "Show Changed Rows Only" view. "Uncommitted changes" button shows full diff. Agent holds commit until user confirms.
Visual Diff in Data Apps¶
A new UX pattern for version-controlled data applications:
- Modified table names highlighted in yellow in the sidebar
- "Show Changed Rows Only" checkbox to filter to working set rows
- "Uncommitted changes" button for complete diff breakdown
- Diff review before commit — the core safety mechanism
Commit Confirmation Pattern¶
The agent holds off on making a Dolt commit until the user grants explicit confirmation. This makes it impossible for the agent to break the database. User reviews the diff, then hits confirm. This is the key safety pattern that differentiates Dolt from plain MySQL for agentic writes.
Dolt MCP Server¶
The agent uses the Dolt MCP Server for all Dolt-specific operations, separating tool calls from generic Bash/SQL. This separation enables important features related to permissions and approvals — each MCP tool call is auditable.
Rollback to Any Commit¶
Even after accidental changes, Dolt allows immediate reset to any prior commit. The article demonstrates having the agent rollback to the original state after testing.
Connection to Cursor for Everything¶
This article is the concrete implementation of the Cursor for Everything pattern applied specifically to SQL databases. The 5-step recipe (chat panel → LLM → tools → Dolt DB → version control) is now a working product.
Downloads¶
Related¶
- cursor-for-everything — Parent pattern this article concretely implements for SQL
- commit-confirmation-pattern — Agent holds off on commit until user confirms
- branch-aware-llm-writes — Agent writes on working set, user reviews, then commits
- dolt-as-agentic-database — Dolt's version control for AI agent SQL writes
- mcp-model-context-protocol — Dolt MCP Server separates tool calls from Bash/SQL
- mysql-vs-version-controlled-db-for-agents — MySQL vs Dolt safety comparison
- visual-diff-data-apps — Yellow table highlights, changed-rows view, uncommitted diff