What I built in October

A developer shipped Foremerge 0.6.0, a coordination store update that prevents the store from filling up with work left behind by agents that quit mid-task, and released GPTree 1.19.13, which adds the ability to branch any web page into GPTree from its Chrome extension. The developer also published guidance on running multiple Claude Code agents in parallel, arguing that Git worktrees move file collisions to merge time rather than eliminating them.

October was mostly Foremerge and GPTree. Foremerge 0.6.0 went out, which stops a coordination store filling up with work from agents that quit mid-task, and GPTree 1.19.13 added branching any web page into GPTree from the Chrome extension. Here is everything I published last month in one place. Running multiple Claude Code agents in parallel: what worktrees cannot see https://go.foremerge.com/letter-2026-11-personal-substack The setup that works for parallel agents, and the collisions Git merges without a word. Gemini Gems become skills in November and custom GPTs retire on December 11. https://dev.to/naw103/gemini-gems-become-skills-in-november-and-custom-gpts-retire-on-december-11-what-to-copy-out-first-3kf5?utm source=substack&utm medium=social&utm campaign=personal-substack&utm content=letter-2026-11 What to copy out first and what to save from your Gems and custom GPTs before the changes land. What the phrase originally meant, and how to explain it to the person with the budget. Worktrees do not remove the collision. They move it to merge time. https://go.foremerge.com/letter-2026-11-personal-substack-66b4ba Why separate checkouts stop agents overwriting files but not their plans contradicting each other. What the term means, with the replace versus extend example. What happens to a coordination store when agents quit without closing their work, and what 0.6.0 changed. One question for you: if you run more than one coding agent in one repo, what goes wrong first? Reply and tell me.