Pretty much everyone saying worktrees but I lean heavily on hot-reloading of both backend and frontend (to actually see what I'm doing) so it's too annoying to deal with dependencies and ports when things are isolated. Instead I keep everything on the main branch and just make sure to keep tasks pretty separate in scope, e.g. add this API route vs. fix this layout issue, so they don't step on each other. When I consider something done I have the agent commit what it worked on and start a new one.
It seems like everyone commenting here is already part of the hivemind. So maybe someone can answer an important question that I'm not getting at all from the docs: what does this actually do?
I printed the casing just to see - it actually does fit in my levi pockets (front and back), but looks and feels a bit ridiculous to actually walk around with
I wish there as much detail on the escapement as on the springs. The bouncy sliders are a fun way to draw in the attention but springs are already intuitive... I'd like to see that kind of visualisation effort applied to the harder concepts.