We use GPTree to manage context across all our chats and coding agents using the graft extension on local machines. This allows us to use several different model families through Claude, cursor and codex without having to copy paste everywhere. It allows all out agents to run on the same context tree and company documents.

I read only a small part of what agents write now, mainly risky chunks after 3 review passes by different model families. Reading everything dosnt scale. I think a lot of it comes down to the confidence you have in the development procedures for the agents, the system architecture of what they are changing and the review procedure.

Make sure to keep the reasons where the agent can see them. Without the reason for a decision the agent can find the old approach in a doc or blog post somewhere and will keep referencing it because nothing told it why it chnaged. I keep all decisions with the reason and the date together and weekly prune as well as adding to the doc.

The thing that didn’t get cheaper for me was conversion. I run a few small products alone with agents doing a lot of the work. We had a big spike of free signups that retained better than I expected. Getting them to pay was still the struggle, mostly with onboarding and people not finding the features. We had to have real conversations with our users to be able to fix that.

Im the author. Foremerge is an MCP coordination protocol for coding agents working in parallel across multiple worktrees on the same source.

Each agent commits its intent and scope prior to changing any file so plans that collide show up as findings before code is changed rather that in merge conflicts later. Like git for before code is written. It's open source and saves a ton of headaches and time resolving conflicts later even if your agents do it for you.

Happy to answer any questions about the stopped agent tests or the migration change.

At least fix the docs that say v3 gets security fixes

If 10 minutes is becoming 2 hours it’s hard to believe that time is being saved using AI but the first question I would ask is what business impact did it have fixing those bugs? I’m guessing probably very little since they were 3 years old.

One trap when you name AI bots specifically is that is that robots.txt groups don’t merge. Crawlers will only follow the most specific group so if GPT bot has its own group named nothing under User-agent: * applies to it anymore so you need to repeat every disallowed line under each group.

The same approach worked for us with agent runs. We gave them fewer tools up front and let the models just pull what they need

Only routine sessions right now since I didn’t want to delete anything where I had replies without a manual review but it could be easily forked and modified for all sessions