Comment by ayewo
2 days ago
> Set me back 2 weeks of work.
How did this happen?
Did you let the agent loose without first creating its own git worktree?
2 days ago
> Set me back 2 weeks of work.
How did this happen?
Did you let the agent loose without first creating its own git worktree?
What's the benefit of git worktree? I imagine you can just not give the agent access to git and you're in the same spot?
I'll reply to myself since apparently people downvote and move on:
They're useful for allowing agents to work in parallel. I imagine some people give them access to git and tools and sandbox the agents, then let a bunch of them work in separate git worktrees pointed at the same branch, then they come back and investigate/compare and contrast what the agents have done, to accelerate their work.
I think there is value in that but it also feels like a lot of very draining work and I imagine long term you're no longer in control of the code base. Which, I mean, great if you're working on a huge code base since you already don't control that...
Welcome to engineering management.
1 reply →
tfw people are running agents outside containers
Yeah this something I need to get to.
Apologies. I meant branch. I nuked the branch. But set me back a lot of time as I thought it may be few things here and there.
I see! That is annoying. A good reminder to push or fork the branch for backup.
I always set gc.auto=0 for this reason, because it means the reflog will be there if I need it (unless I accidentally delete .git)