Original Summary

when I started using coding agents heavily, they began creating tons of Git worktrees. different tools like Codex, Claude Code, T3 Code, Orca, Superset, and others all put their worktrees in different directories, which made them pretty hard to find.<p>I know you can just ask an agent to find them, and a lot of people do exactly that. but I wanted a deterministic solution that wouldn&#x27;t depend on an agent getting things right or waste extra tokens.<p>so.. I built Lopper!<p>it&#x27;s a tool that searches for git repositories and worktrees across different directories on your machine and shows them all in one place in a TUI, where you can inspect them and remove the ones you no longer need. it also has a CLI for scripts and agents, so they can manage worktrees more reliably.<p>would you use something like this? what am I missing compared to just asking an agent to handle it?

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Hacker News 新项目
  • 发布时间：2026/10/16 05:03:38