Replit Cloud Agents 开放企业代码库贡献，非技术人员可直接提交经测试的 PR

Since we launched the first generally available coding agent in 2024, almost anyone can build an app. But changing your company’s core product is still out of reach for anyone outside engineering, and that bottleneck has only grown as more people build.

The people who know what should change in a product often sit outside engineering. A designer has noticed spacing that has been off for months. A support lead knows which setting confuses customers every week. These are fixes that often go into a ticket and wait for a sprint that never comes.

But when they try to make the change for themselves, it breaks down. They can’t show engineering that the change works. The engineer simply doesn’t have time to teach them, and everyone else in the company, how the team writes code. And getting the app running in the right environment is a project of its own.

Today, anyone on your team can use Replit Cloud Agents to contribute code directly and safely to your core codebase. Cloud Agents test each change in your running app, carry review feedback forward, and share one setup across the team. Engineers stay in control, and the barriers to contributing are lowered for everyone else.

We call this part of the Self-Driving Company, and it’s now available for all Pro & Enterprise customers.

Save a seat to hear directly from our product team in a webinar on November 5

Turn an idea into a reviewed code change with Cloud Agents

Subject matter experts no longer need to know where the code lives, or how the app is built. Anyone can now just describe what should change in plain language. Cloud Agents then find the relevant code, and make a secure change while a live preview of your app updates next to the chat. You can react to what you see, and ask for adjustments before anything goes to engineering.

When it looks right, the agent opens a pull request (PR) in GitHub or a merge request (MR) in GitLab that follows your team’s skills and contribution guidelines. If a review, human or agent, asks for changes, the agent makes them and updates the request. Non-technical experts no longer have to turn review comments into code themselves.

A feature request now arrives as a test change, with video evidence

When subject matter experts try to ship changes today, review quickly becomes a bottleneck that goes back-and-forth. They can’t run the app themselves, so they ask an engineer for a screenshot, spot something off, and ask for a fix. Each round of review takes time and adds busywork.

Now, Cloud Agents can check the change in isolated cloud sandboxes before the pull request reaches anyone. The agent opens your running app in a browser and clicks through the change the way a customer would. If something fails, it fixes the code and tests again. Then, it attaches screenshots and video of the final version to the pull request.

What this means is that a feature request can now arrive as a tested pull request. Anyone can describe the change, close their laptop, and come back to a video of it working. Engineers get pull requests they don’t have to run themselves to understand, arriving in GitHub or GitLab already tested, with the video of the change working, ready to approve or provide feedback.

Review feedback becomes skills engineers approve

More contributors means more pull requests for the same reviewers, and reviewers end up repeating themselves over and over again.

Replit has self-improving workspace memory, turning comments into guidance for Cloud Agents to follow. When review feedback is worth keeping, the agent proposes an update to your team’s skills, the written instructions agents follow in your codebase, or drafts a new one. Engineers approve each update before it takes effect.

After that, the next pull request starts where the last review left off. Cloud Agents start to remove the collaboration burden between teams, enabling both to be more strategic. This feature is in early access.

Broader workspace memory is a key function of Replit, and will be a key element of Self-Driving Companies. Internally at Replit, we’ve used it to reduce token usage by 51%, and cut the time agents take to complete a common data task from 16 minutes to 1 minute, without reducing output quality.

Make better decisions with easy access to code

For many companies, code is one of the ground truths for how services work. There’s so much you can do with a full understanding of your product. With Replit, anyone in your company can now get answers grounded in what’s actually built. A support lead can find out why a customer keeps hitting an error. A product marketer can check that a feature works the way the launch copy says. A sales lead can see which team knows a feature best before proposing a change.

That also gives time back to the engineers and product leads who answer these questions every day.

Replit’s agent on the company codebase was rolled out at the start of March 2026. Access to code is one of the main drivers of increased work at Replit done on Replit in 2026:

Set up the environment once, and everyone can contribute

Getting a company’s app up and running takes the right repos, runtime versions, databases, background services, and credentials. Until now, every new contributor had to repeat that setup, a daunting task for a non-technical user. Deterred, they would build separately, or on outdated code, leaving engineers to reconcile the work, or creating a yawning gap between prototype and reality.

Replit has shared environments. An admin can set it up, and everyone can start from there. It just works. A Cloud Agent explores your codebase and configures an initial virtual machine (VM) that runs your app. The result is a ready-to-use environment with your repos, runtimes, skills, tools, and dependencies that anyone can use. It updates automatically from your main branch, so every new change starts from current code.

Contributors don’t see any of this. They just describe the change they want, and the agent starts from an app that’s already running. For engineers, environments handle what real apps need: dozens of programming languages, microservice architectures with several repos running together, Docker images, databases, queues, and caches. Credentials come from your external secrets managers through a credential broker.

Start changes where your team already collaborates

Most product ideas start in a conversation. A customer reports a bug in a support channel, or a PM suggests a fix in a thread. But someone has to copy that into a ticket, and the context stays behind.

Now, the thread can become the request. Mention or DM @Replit in Slack to investigate an issue or turn a proposal into a pull request. You can follow progress and give feedback in the thread, then continue in Replit when you need to. The result is the same tested pull request, with video, in GitHub or Gitlab.

Microsoft Teams support is coming soon. You can also start a pull request from the Replit mobile app when an idea comes up away from your desk.

What it means for your team

Your codebase shapes how your product works and how customers experience it. With Replit’s Cloud Agents, engineering still decides what ships, but the designers, PMs, support leads, and operators closest to the problem can propose changes as tested pull requests instead of tickets.

Replit Cloud Agents for existing repositories are now available for all Pro & Enterprise customers. Connect a repository at replit.com/code-repos, or talk to the sales team about rolling it out across your organization. Documentation is here.

The Slack integration is available to all customers. To set it up, go to Workspace Settings, link your Replit account, and choose a workspace. Documentation is here.

On November 5, we’re hosting a webinar on getting started with both. [Save a seat].