--- title: From Weeks to Hours: Inside Wix’s Autonomous Bug-Fixing... description: Wix Engineering describes the architecture behind Wix Orchestrator, an internal multi-agent system that autonomously investigates support tickets and produces... canonical: https://daily.dev/posts/from-weeks-to-hours-inside-wix-s-autonomous-bug-fixing-system-fekzry59w twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: From Weeks to Hours: Inside Wix’s Autonomous Bug-Fixing System | daily.dev og:description: Wix Engineering describes the architecture behind Wix Orchestrator, an internal multi-agent system that autonomously investigates support tickets and produces... og:url: https://daily.dev/posts/from-weeks-to-hours-inside-wix-s-autonomous-bug-fixing-system-fekzry59w og:image: https://api.daily.dev/og/posts/fekzRy59w.png og:image:alt: From Weeks to Hours: Inside Wix’s Autonomous Bug-Fixing System og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # From Weeks to Hours: Inside Wix’s Autonomous Bug-Fixing System **[Wix Engineering](https://daily.dev/sources/wix_eng)** · 10 min read · 2 upvotes · 0 comments ## Summary Wix Engineering describes the architecture behind Wix Orchestrator, an internal multi-agent system that autonomously investigates support tickets and produces production-ready pull requests. The system uses four specialized agents (Detector, Enricher/Wix Octocode Research, Coder, Reviewer) coordinated by an orchestrator, with a human engineer always reviewing the final fix before it ships. The core insight is that context quality, not model choice, determines fix quality: the Enricher combines static code analysis (OctoCode), database queries (Trino), live logs (Grafana), and documentation into a structured plan for the Coder agent. Schema validation with retries cut inter-agent error rates from roughly 50% to under 1%. Open problems remain around ticket classification and capturing undocumented organizational/institutional knowledge that isn't visible in code or logs. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How did Wix reduce the time to fix production bugs from weeks to hours using AI agents? Wix built a system called Wix Orchestrator made of four specialized agents: a Detector that classifies incoming support tickets, an Enricher (Wix Octocode Research) that gathers static code context and live runtime data using OctoCode, Trino, and Grafana, a Coder that implements fixes in an isolated Docker container and opens a PR, and a Reviewer that independently evaluates the PR before a human approves it for production. _Teams designing similar agent pipelines can follow ongoing architecture writeups like this on daily.dev._ ### How do you reduce error rates when chaining multiple AI agents together in a pipeline? Validating output schema at every handoff between agents and automatically retrying with the original error and context sent back to the same agent dropped the inter-agent error rate from roughly 50% to under 1%. Idempotency checks also prevent duplicate work when a ticket is already resolved or a PR is already in flight. _Engineers building multi-agent pipelines can track practical reliability techniques like this on daily.dev._ ### What is Specification Driven Development in the context of building AI coding agents? Specification Driven Development means producing a detailed Markdown spec describing what is being built, why, and how before any code generation happens, then having an independent agent review that spec before a coding agent touches the repository. The coding agent receives the reviewed spec as its primary input rather than a vague task description, and framing it as the future maintainer improves error handling and logging in its output. _Developers refining agent workflows for code generation can follow techniques like this on daily.dev._ ## Similar posts on daily.dev - [From Co-Pilot to Full Automation: How Wix Is Embedding AI Agents Across an Engineering Org at Scale](https://daily.dev/posts/from-co-pilot-to-full-automation-how-wix-is-embedding-ai-agents-across-an-engineering-org-at-scale-3yjzklvp7) · Wix Engineering · 0 upvotes · 0 comments - [How We Built the Brain Behind Our Self-Healing System: Context Retrieval at Org Scale](https://daily.dev/posts/how-we-built-the-brain-behind-our-self-healing-system-context-retrieval-at-org-scale-fjfsbvo2t) · Wix Engineering · 0 upvotes · 0 comments - [Agentic automation in practice: putting standard engineering work on autopilot](https://daily.dev/posts/agentic-automation-in-practice-putting-standard-engineering-work-on-autopilot-km13vjz8f) · Atlassian · 0 upvotes · 0 comments - [Using AI agents to secure Google infrastructure](https://daily.dev/posts/using-ai-agents-to-secure-google-infrastructure-n2sosodh7) · Google Cloud · 0 upvotes · 0 comments - [How Grab is Using AI Agents to Boost Team Productivity](https://daily.dev/posts/how-grab-is-using-ai-agents-to-boost-team-productivity-fkppsh0tc) · ByteByteGo · 2 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#architecture](https://daily.dev/tags/architecture), [#context-engineering](https://daily.dev/tags/context-engineering) [View this post on daily.dev](https://daily.dev/posts/from-weeks-to-hours-inside-wix-s-autonomous-bug-fixing-system-fekzry59w) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"From Weeks to Hours: Inside Wix’s Autonomous Bug-Fixing System","url":"https://daily.dev/posts/from-weeks-to-hours-inside-wix-s-autonomous-bug-fixing-system-fekzry59w","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/from-weeks-to-hours-inside-wix-s-autonomous-bug-fixing-system-fekzry59w"},"datePublished":"2026-08-19T10:18:13.012Z","dateModified":"2026-09-14T06:05:57.822Z","description":"Wix Engineering describes the architecture behind Wix Orchestrator, an internal multi-agent system that autonomously investigates support tickets and produces...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/94a85601391aa77f9ca53e44053969b2?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/94a85601391aa77f9ca53e44053969b2?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Wix Engineering","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Wix Engineering","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/5a14a3f3d2a14128bcb9a084fb2ebadf","url":"https://daily.dev/sources/wix_eng"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/from-weeks-to-hours-inside-wix-s-autonomous-bug-fixing-system-fekzry59w","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,architecture,context-engineering","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Wix Engineering","item":"https://daily.dev/sources/wix_eng"},{"@type":"ListItem","position":3,"name":"From Weeks to Hours: Inside Wix’s Autonomous Bug-Fixing System"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/from-weeks-to-hours-inside-wix-s-autonomous-bug-fixing-system-fekzry59w#faq","mainEntity":[{"@type":"Question","name":"How did Wix reduce the time to fix production bugs from weeks to hours using AI agents?","acceptedAnswer":{"@type":"Answer","text":"Wix built a system called Wix Orchestrator made of four specialized agents: a Detector that classifies incoming support tickets, an Enricher (Wix Octocode Research) that gathers static code context and live runtime data using OctoCode, Trino, and Grafana, a Coder that implements fixes in an isolated Docker container and opens a PR, and a Reviewer that independently evaluates the PR before a human approves it for production. Teams designing similar agent pipelines can follow ongoing architecture writeups like this on daily.dev."}},{"@type":"Question","name":"How do you reduce error rates when chaining multiple AI agents together in a pipeline?","acceptedAnswer":{"@type":"Answer","text":"Validating output schema at every handoff between agents and automatically retrying with the original error and context sent back to the same agent dropped the inter-agent error rate from roughly 50% to under 1%. Idempotency checks also prevent duplicate work when a ticket is already resolved or a PR is already in flight. Engineers building multi-agent pipelines can track practical reliability techniques like this on daily.dev."}},{"@type":"Question","name":"What is Specification Driven Development in the context of building AI coding agents?","acceptedAnswer":{"@type":"Answer","text":"Specification Driven Development means producing a detailed Markdown spec describing what is being built, why, and how before any code generation happens, then having an independent agent review that spec before a coding agent touches the repository. The coding agent receives the reviewed spec as its primary input rather than a vague task description, and framing it as the future maintainer improves error handling and logging in its output. Developers refining agent workflows for code generation can follow techniques like this on daily.dev."}}]} ```