Google Labs announced Stitch Loop on November 18, an experiment connecting a codebase with product logs, usage and feedback to propose improvements after launch. Its waitlist is open globally, with eligible Google AI Ultra users given priority. Google announcement
The big change
- Google describes an agent that stays with a shipped product, using operational evidence to propose changes and observe results. Its job is intended to run from identifying a useful change through checking the result.
- A pull request gives a person a specific change to examine. Reviewers can discuss the implementation, approve it or request revisions, while repository rules determine which approvals are required before merging.
- Judging an improvement requires a defined measure and evidence about cause. A comparison group can help a team evaluate whether a release changed customer behaviour, informing which idea it should pursue next.
From a product signal to a reviewed change
Google describes four stages. Loop surfaces suggestions from product evidence, then offers solutions with scope and trade-offs. Once a user chooses a direction, it writes code in an isolated cloud workspace and opens a GitHub pull request. Google says the user reviews the request before anything merges. Loop then monitors live data, uses positive and negative results to inform later suggestions, and continues watching after a goal is met. Checkout conversion is one of Google's examples of a custom loop. Google announcement
Which shoppers enter the comparison?
Consider a hypothetical shop where many people start checkout but relatively few complete a purchase. The team might investigate shipping charges or a broken button, two possible explanations in Google's Analytics guidance. A proposed button repair is a hypothesis about what could help customers finish. Purchase journey documentation
Google Analytics' Purchase journey report traces users through events including product views, adding to a cart, beginning checkout and purchasing. Its default closed funnel counts users who follow each step in the specified sequence. An open funnel allows entry at later stages. Switching between them changes who appears in the later counts. Purchase journey documentation
For the hypothetical shop, a completion measure therefore needs a consistent group of checkout starters and a matching count of purchases. Keeping the same event definitions and funnel conditions makes the comparison interpretable when assessing a later release. Purchase journey documentation
Review applies to the actual edit
GitHub's review documentation describes three decisions, comment, approve and request changes. A reviewer can discuss specific lines and suggest a correction. For a proposed checkout repair, that gives a person a place to examine what the code changes and ask the author to address a concern. GitHub review documentation
GitHub also documents configurable rules requiring a specified number of approvals. Repository administrators can require an approval after the most recent reviewable push or dismiss an earlier approval when the changes differ. That connects review to the current edit as more code arrives during discussion. These are repository controls a team can configure around its development process. GitHub rules documentation
The metric's movement still needs an explanation
Microsoft researchers' Online Experimentation at Microsoft describes randomly assigning users to a control or changed version. With an appropriately designed experiment, the groups provide a way to test whether the change caused a difference in behaviour. The paper explains why effects outside a release can overwhelm a comparison made only across successive periods. Original research
For a team deciding what to build next, the useful question is how the changed experience performed against a comparable unchanged experience. The experiment's design and statistical evidence determine the conclusion. Original research
BIG CHANGE reviewed the announcement and documentation. We have not tested Loop.



