Hi I started a project, currently hosted at llambda.net, for landing patches from web agents. It reflects up the compile error to the site so that the web agent can access it via a link. The underlying mechanism has two interesting components. 1. Wires, an extension to cabal projects, including an idempotency layer which can save time when agents trigger recompilations. There is also a proper extension called Gizmos, where cabal project folders are handled by a secondary checker which ensures dependencies between such bundles are solvable. There is some accompanied codegen which produces cabal.project and .cabal files in an algorithmic way, and seperates off "cog" tests, so that all of the "go-is" style main options have string tests that they can pass. "gears" percolate through the code and culminate in cog tests, which agents find very useful and can be counted to ensure large scale bypassing or "mocks" can be noticed. 2. The "forks" based lanes for landing. These are parallel lanes in which agents can operate on a moving target codebase as commits from various lanes arrive. the semantics of this are unfortunately a myriad of slop from the agents I used to cobble it together, but they pushed through all the bugs and it seems stable. It is a new style of versioning and commitment software that I would love for some support from the community in maintaining. Currently the source ships as a library in a microsoft installer so I can keep the codebase closed source. This is not the intension moving forwards, but since the project was just completed, I opted for this approach for now. Please contact me at guystorey88@hotmail.com and I can provide the source until I have a link to a permanent repo. Because of the unique layout it does not ship perfectly through hackage or I would have done that. I would like in the long run to see Gizmos have its own repository / package manager. Peace Guy