Wix Engineering

Every developer building with AI agents eventually hits the same wall. You write a masterpiece of a system prompt, loaded with rules, edge cases, and brand guidelines. It works perfectly... until you add one more rule. Suddenly, the agent gets "context fatigue," ignores half your instructions, and hallucinates a creative but entirely broken solution. We need to stop trying to make agents perfect on the first try. Instead, we suggest a new architectural approach: organizing agentic workflows...

Ask a naive agent to find a bug in a codebase with thousands of repositories, and it will find the first textual match and stop. It won't ask why. It won't check whether what it found is actually relevant. It won't explore related services. It'll just return something and call it done. We, at Wix, discovered this the hard way. And it's what pushed us to build something more deliberate: a research engine that doesn't just search, but reasons about what it's looking for and why. The Problem:...

When you have over 2,500 microservices and thousands of engineers working across a massive multi-product platform, "just use AI coding tools" is not a strategy. It's a starting point - and not a particularly useful one. The question we kept coming back to at Wix wasn't whether to adopt AI in our engineering workflow. That ship had sailed. The question was: what does agentic coding actually look like when you have strong domain boundaries between services, a monorepo with years of...