This is something I've been noodling at, splitting a monorepo into a bunch of component projects. I think, unless they have access to something that is wildly outside the scope and scale of current API models, the downside of having a monorepo is the context pollution, and there's no way to escape that.
I'm not fully sold either way yet but I think splitting might actually be critical for moderating the blast radius of agent intervention.
This is something I've been noodling at, splitting a monorepo into a bunch of component projects. I think, unless they have access to something that is wildly outside the scope and scale of current API models, the downside of having a monorepo is the context pollution, and there's no way to escape that.
I'm not fully sold either way yet but I think splitting might actually be critical for moderating the blast radius of agent intervention.