--- title: Should Dolt Have Worktrees? # | daily.dev description: Git worktrees — a feature that lets multiple branches be checked out simultaneously from a single clone — have become popular with coding agents that run... canonical: https://daily.dev/posts/should-dolt-have-worktrees--ajjz6ryq9 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Should Dolt Have Worktrees? # | daily.dev og:description: Git worktrees — a feature that lets multiple branches be checked out simultaneously from a single clone — have become popular with coding agents that run... og:url: https://daily.dev/posts/should-dolt-have-worktrees--ajjz6ryq9 og:image: https://api.daily.dev/og/posts/AjjZ6ryq9.png og:image:alt: Should Dolt Have Worktrees? # og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Should Dolt Have Worktrees? # **[DoltHub Blog](https://daily.dev/sources/dolthub-blog)** · 8 min read · 0 upvotes · 0 comments ## Summary Git worktrees — a feature that lets multiple branches be checked out simultaneously from a single clone — have become popular with coding agents that run parallel sub-agents. Each sub-agent gets an isolated working directory without the cost of a full re-clone. Dolt, the version-controlled SQL database, already solves this problem natively: every database connection can operate on a different branch simultaneously, giving each agent its own isolated working set by default. The post concludes that Dolt worktrees are unnecessary for the SQL server use case, and unlikely to be implemented for the CLI either due to database size concerns. Agents wanting worktree-like behavior with Dolt should simply connect to a Dolt SQL Server on separate branches. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why do AI coding agents use Git worktrees instead of just switching branches? Coding agents use Git worktrees so multiple sub-agents can edit files in parallel without colliding, since a single working tree can only be checked out to one branch at a time. Each worktree gets its own directory, branch, and uncommitted changes, but all worktrees share the same underlying .git object store, avoiding the cost of cloning the repository multiple times. _daily.dev surfaces practical breakdowns like this for developers wiring up multi-agent coding workflows._ ### Does Dolt support Git-style worktrees for running agents on multiple branches at once? No, Dolt does not have worktrees and its creator argues it does not need them. Running a Dolt SQL Server already lets every client connection check out a different branch simultaneously in its own session, giving the same isolation worktrees provide in Git without any extra setup or duplicated storage. _Developers comparing database version-control approaches can track takes like this on daily.dev._ ### When did Git add support for worktrees? Git added multiple worktree support in version 2.5, released in 2015. The feature lets a single clone have several working directories attached to it, each checked out to a different branch while sharing one .git object store, though it went largely unnoticed by many Git users for years until coding agents started using it. _daily.dev helps developers catch overlooked Git features like this before they trip up a workflow._ ## Similar posts on daily.dev - [AI Agents Need Their Own Desk, and Git Worktrees Give Them One](https://daily.dev/posts/ai-agents-need-their-own-desk-and-git-worktrees-give-them-one-8wfs2jfmk) · Towards Data Science · 1 upvotes · 0 comments - [Git Worktrees](https://daily.dev/posts/git-worktrees-04mllgbwk) · Flavio Copes · 3 upvotes · 0 comments - [What are git worktrees, and why should I use them?](https://daily.dev/posts/what-are-git-worktrees-and-why-should-i-use-them--cgprqx6wz) · GitHub Blog · 8 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#backend](https://daily.dev/tags/backend), [#version-control](https://daily.dev/tags/version-control) [View this post on daily.dev](https://daily.dev/posts/should-dolt-have-worktrees--ajjz6ryq9) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Should Dolt Have Worktrees? #","url":"https://daily.dev/posts/should-dolt-have-worktrees--ajjz6ryq9","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/should-dolt-have-worktrees--ajjz6ryq9"},"datePublished":"2026-07-23T19:29:02.424Z","dateModified":"2026-09-14T08:03:26.690Z","description":"Git worktrees — a feature that lets multiple branches be checked out simultaneously from a single clone — have become popular with coding agents that run...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ef32887a12f2b3ea34f0f4cf73517587?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ef32887a12f2b3ea34f0f4cf73517587?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DoltHub Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DoltHub Blog","logo":"https://media.daily.dev/image/upload/s--LXDlvjS4--/f_auto,q_auto/v1780213587/logos/dolthub-blog?_a=BAMAMiWQ0","url":"https://daily.dev/sources/dolthub-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/should-dolt-have-worktrees--ajjz6ryq9","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,backend,version-control","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DoltHub Blog","item":"https://daily.dev/sources/dolthub-blog"},{"@type":"ListItem","position":3,"name":"Should Dolt Have Worktrees? #"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/should-dolt-have-worktrees--ajjz6ryq9#faq","mainEntity":[{"@type":"Question","name":"Why do AI coding agents use Git worktrees instead of just switching branches?","acceptedAnswer":{"@type":"Answer","text":"Coding agents use Git worktrees so multiple sub-agents can edit files in parallel without colliding, since a single working tree can only be checked out to one branch at a time. Each worktree gets its own directory, branch, and uncommitted changes, but all worktrees share the same underlying .git object store, avoiding the cost of cloning the repository multiple times. daily.dev surfaces practical breakdowns like this for developers wiring up multi-agent coding workflows."}},{"@type":"Question","name":"Does Dolt support Git-style worktrees for running agents on multiple branches at once?","acceptedAnswer":{"@type":"Answer","text":"No, Dolt does not have worktrees and its creator argues it does not need them. Running a Dolt SQL Server already lets every client connection check out a different branch simultaneously in its own session, giving the same isolation worktrees provide in Git without any extra setup or duplicated storage. Developers comparing database version-control approaches can track takes like this on daily.dev."}},{"@type":"Question","name":"When did Git add support for worktrees?","acceptedAnswer":{"@type":"Answer","text":"Git added multiple worktree support in version 2.5, released in 2015. The feature lets a single clone have several working directories attached to it, each checked out to a different branch while sharing one .git object store, though it went largely unnoticed by many Git users for years until coding agents started using it. daily.dev helps developers catch overlooked Git features like this before they trip up a workflow."}}]} ```