Menu

1 / 4

Submodules, LFS, Codegen: 7 Things a New Agent Worktree Doesn't Have Yet

DEV Community: docker·Gabriel Anhaia·11 days ago
#XdWWRgvJ
#devtodocker#devto#dev#worktree#compose
Reading 0:00
15s threshold

Book: Database Playbook

Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go

My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools

Me: xgabriel.com | GitHub

An agent's first test run in its new worktree fails on an import from src/generated/ . The folder exists. It lives in your main checkout, where prisma generate wrote it weeks ago, and git ignores it.

Most people running agents in worktrees learn about .env , node_modules and port 3000 on day one. Past those, git worktree add leaves seven more gaps, and each has a check and a one-line fix.

Two commands show most of the gap

A new worktree gets the tracked files of its branch. Anything git ignores, or has never seen, stays where it was.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.