Remix.run Logo
▲ JohnMakin 4 hours ago

> As our monorepo grows, it increasingly doesn’t fit that design space. The history of our main branch alone is almost 100 GB, and a compressed working copy is over 25 GB.

This is absurd, and I expect is a cause of the fact that they seem to use git history as a message queue source of truth between agents. They can do whatever works for them, fine, but I've noticed this has leaked into their training somehow, my agent, despite very strict rules on how to use my git workflow, will do absolutely nonsensical and weird (from a human who has used git for a long time perspective) stuff with git that can only be a byproduct of how they use it.

Hopefully this fixes that, get your weird workflow out of mine.

▲nickg-anthropic 2 hours ago | parent [-]

We generally don't allow agents to use source control for coordination in that way. There really is tremendous growth in actual software and code being written that necessitated Scion.

▲JohnMakin an hour ago | parent | next [-]

Well, mine constantly tries to do this, so I made the assumption. Otherwise I can't really understand how you are generating hundreds of millions of commits, either.

▲svieira 2 hours ago | parent | prev [-]

> don't allow

Is this "allow" or "encourage"? If "allow", how do you do that deterministically or at least fail-closed?