Replit announced on October 27, 2026 that its Cloud Agents can help designers, product managers and support staff propose changes to existing company software. The company says its agents can check a running development version in a browser and attach screenshots and video to a proposed code change on GitHub or GitLab.
That could let a support lead show engineering a proposed fix for a confusing setting, rather than only describe the problem. The engineering team still decides whether the change should be accepted.
Replit names Pro and Enterprise customers in its announcement. However, its current repository guide still calls the workflow early access and says availability and setup can vary by workspace. Teams should confirm access in their own workspace before planning a rollout.
A proposal, not a release
In the documented workflow, a contributor describes a change in chat, the agent edits a development copy, and the contributor checks a live preview. The agent can then open a pull request on GitHub or a merge request on GitLab: a proposal for the team to review, not an automatic change to the live product.
Contributors need authorized access to the repository, where the project’s code is stored. Connecting an account does not grant new permissions. Existing review requirements and branch rules still apply; merging accepts the code, while deployment follows the team’s release process. Some teams deploy automatically after a merge.
Replit also says agents can propose reusable guidance from review feedback, with engineers approving each update before it takes effect. That learning feature remains in early access. For the separate decision about automating follow-up edits, see when to let Qwen Code fix a pull request.
What the browser evidence establishes
A video can help a requester and reviewer discuss the same visible result. It does not establish that every requirement has been checked. Replit’s contribution guide tells users to read the final results, including anything the agent could not verify; its security guidance says passing tests do not replace code review.
A useful first trial would be a clearer error message or a repaired link. Define both what should change and what must stay the same. For a wording change, for example, check that the new text appears in the intended situation and that the surrounding interaction still works.
Team access is not unlimited usage
The published entry price for Pro is US$90 a month when billed annually, with US$100 in monthly credits; taxes may apply. Enterprise pricing is custom. Pro supports up to 15 builders sharing pooled credits without per-user fees, so adding contributors does not multiply the included credit allowance.
Replit’s billing guide says paid Agent work is charged according to the effort involved. Paid planning can incur charges without changing code, and credits also cover other cloud services. Free Mode has an allowance, but the sources do not establish that this entire repository workflow is free or give a fixed cost per accepted change.
For a small team, a sensible pilot is one focused request with a named engineering reviewer. Judge it by the accepted change, the review effort and the actual usage charge—not simply by how many proposals the agent produces.