DoltHub

The Dolt Workbench got upgrades. Agent gets stuck? Send a message, and it stops. Or cancel one tool call without killing the response. Model swap mid-session. Session history on disk. Cursor for SQL. ow.ly/tHOh50Yx3qR #CursorForSQL #GitForData

Thanks for the feature! We are #GitForData, the #DatabaseForAI

Dolt now supports SSH remotes. Push/pull over SSH — on-prem, bastion-friendly, no DoltHub required. Neil Macneale IV built dolt transfer: gRPC + HTTP over stdin/stdout via SMUX. Same protocol. Different transport. What would you build? dolthub.com/blog/2026-03-1…

lazydolt is a terminal UI for Dolt built entirely by coding agents in an afternoon. Think lazygit, but for a version-controlled SQL database. Zach tested it. His read: "shockingly good prototype for the human time invested." dolthub.com/blog/2026-03-1… #DoltDB #GitForData

@sababisha_SSL If you haven't tried Dolt Workbench, look no further!

Sababisha Solutions got you when it comes to building an AI that talks to your database in plain English.

One change got Gas Town from 4 concurrent agents to 160: switching the persistence layer to Dolt. Multi-agent needs SQL query power + Git-style versioning. No other tool gives you both. All roads lead to Dolt: dolthub.com/blog/2026-03-1… #MultiAgentSystems #GitForData

Chicago, this is suspect. $231.7M billed to Medicaid for ambulances in 2024 against an $82M EMS budget. 8.5x the national average. Dolt Workbench agent mode found 3 other cities running the same play. dolthub.com/blog/2026-03-1…

@scottshapiro__ @gregisenberg Thats where we can help

Biggest thing I’ve learned building in this space: the agent roster is the easy part. The hard part is orchestration who decides what gets worked on next, how do agents hand off, and what happens when one fails mid-task. We solved it with a heartbeat system every agent wakes on a cycle, reads context, takes one action, learns, sleeps. Coordination without chaos. Would love to compare notes with anyone else going deep on this.

i found a github repo that lets you spin up an ai agency with ai employees engineers, designers, growth marketers, product managers each role runs as its own agent and they coordinate to ship ideas 10k+ stars in under 7 days 1. engineering (7 agents) frontend, backend, mobile, ai, devops, prototyping, senior development 2. design (7) ui/ux, research, architecture, branding, visual storytelling, image generation 3. marketing (8) growth hacking, content, twitter, tiktok, instagram, reddit, app store 4. product (3) sprint prioritization, trend research, feedback synthesis 5. project management (5) production, coordination, operations, experimentation 6. testing (7) qa, performance analysis, api testing, quality verification 7. support (6) customer service, analytics, finance, legal, executive reporting 8. spatial computing (6) xr, visionos, webxr, metal, vision pro 9. specialized (6) multi agent orchestration, data analytics, sales, distribution what i like about this approach is the framing instead of one big ai agent trying to do everything, you structure it more like a company. specialized agents, clear responsibilities, workflows between them im curious to see what this actually feels like in practice and if its any good (do your own research) github.com/msitarzewski/a… but as always will share what i learn in public and on @startupideaspod one thing is for certain and it reminds me the future belongs to those who tinker with software like this

Coding agents + shared databases = chaos. @Signadot fixed that with Dolt. Fresh DB branch per sandbox, auto-deleted when done. No shared state. No dirty data. No surprises. #DatabaseForAI

@signadot Love seeing this in the wild. Exactly what Dolt was built for. Great work @Signadot 🤝

🚀 New Tutorial: Database Isolation with Dolt Coding agents working in complex cloud-native systems need isolated environments that give them the feedback signals they need to validate their code against reality. We just launched a native integration with @DoltHub to give Dolt users seamless data isolation inside Signadot sandboxes. 🧵

When you add an agent to an app, it can't touch the UI. We fixed that. In-process tools that fire the same events as a button click. dolthub.com/blog/2026-03-0… #MCPTools #AgentDevelopment

Dolt Workbench's Agent Mode analyzed Medicaid claims (2018–2024), defined 5 fraud signals, and flagged providers with 2+ All queryable, version-controlled, and diffable. We built a fraud detector. What will you detect? dolthub.com/blog/2026-03-0…

Branches, Diffs, and SQL: How Dolt Powers Agentic Workflows @timsehn on @DataEngPodcastwith @TobiasMacey — Prolly Trees, branch-based agent writes, RAG versioning, and when NOT to use Dolt. 🎧@Podhomefm dataengineeringpodcast.com/dolt-version-c… #DataEngineering #DatabaseVersionControl #GitforData

We take user issues at DoltHub very seriously. We have a pledge to fix bugs within 24 hours. But sometimes, what looked like a short diversion can become an entire journey. Nick writes about one of those times ow.ly/vWg050YocXp #QueryOptimization #SQL #OpenSource

AI agents detect $100M+ fraud in Medicaid data using Claude & Dolt Workbench. Public data, free tool. What's hiding in your data? dolthub.com/blog/2026-02-2… #DataEngineering #DatabaseAgents #FraudAnalysis

@patrickdevivo Onward and upward! 🚀

@DoltHub 🚀

We hit 20,000 GitHub stars! 🌟 Thanks for supporting the first version-controlled database. #GitForData Next stop: 100,000 stars! Haven't starred us? Now's the time 👉 github.com/dolthub/dolt dolthub.com/blog/2026-02-2…

Simon Späti from MotherDuck dropped a top Git-for-data comparison. LakeFS, Nessie, Neon, Bauplan, DuckLake, Dolt under the microscope. Dolt Highlights? fastest PR merges (~30 min), ~20K stars, 490 open issues vs Neon's 3,040. Read👉 motherduck.com/blog/git-for-d… #GitForData #OpenSource

Push, pull, and clone Dolt databases directly to Azure blob storage. No new infrastructure needed. See the full setup here 👉 dolthub.com/blog/2026-02-2… #AzureRemotes #DatabaseVersionControl #GitforData