Last updated: November 1, 2026
Replit Cloud Agents let anyone on a team describe a change to an existing GitHub or GitLab codebase in plain language. The agent finds the code, edits a development copy, tests it in a cloud sandbox and opens a pull request with screenshots and video. Engineers still review and merge. It is available to Pro and Enterprise customers.
Contents
- What’s new in Replit Cloud Agents
- How Replit Cloud Agents work
- Plans, pricing and availability
- How to use Replit Cloud Agents
- Shared environments, skills and parallel agents
- Replit Cloud Agents vs the old ticket workflow
- Workflows, security and limitations
- Frequently asked questions
What’s new in Replit Cloud Agents
Replit announced the feature on October 27, 2026 in Anyone can now bring their ideas into the company codebase, and listed it in its October 30, 2026 product update. Replit says its agent on the company codebase was rolled out internally at the start of March 2026.
The launch includes:
| Feature | What it does | Status |
|---|---|---|
| Cloud Agents for existing repositories | Turn a plain-language request into a tested GitHub pull request or GitLab merge request | Pro and Enterprise |
| Browser testing with evidence | The agent clicks through the running app, fixes failures and attaches screenshots and video | Part of Cloud Agents |
| Shared environments | An admin sets up one VM with repos, runtimes, skills, tools and dependencies; it updates from the main branch | Part of Cloud Agents |
| Self-improving workspace memory | Review feedback becomes proposed skill updates that engineers approve | Early access |
| @Replit in Slack | Start an investigation or a pull request from a Slack thread | All customers; Teams coming soon |
| Agent messaging | Agent can send a message to another chat or create a new chat | Pro and Enterprise |
The same update added GPT-6.1 Terra to the model selector when building with Agent in Power Mode.
How Replit Cloud Agents work
According to How coding with Replit works, Replit runs your code in a sandbox, an isolated cloud development environment inside a microVM. Your production app stays hosted where it is.
The flow has five stages:
- Access and preview: Replit clones the repository into a sandbox using the permissions you authorize, installs dependencies and starts a development preview.
- Changes in a development copy: edits do not touch the shared repository right away. Replit can test the app in a browser and run repository checks.
- A team of agents: one main chat can hand independent tasks to worker agents in separate chats and collect the results.
- A draft pull request: Replit creates a branch, commits, pushes and opens a draft pull request (a draft merge request in GitLab).
- Review and revisions: Replit can address feedback, push to the same branch and reply to comments. Your branch rules still apply.
Replit reads relevant code and guidance instead of loading the whole repository into the chat.
Plans, pricing and availability
The announcement says Cloud Agents for existing repositories are available to all Pro and Enterprise customers. The October 30 update files the feature under Enterprise, and the Code with Replit docs call repository-based development an early-access workflow whose availability can differ by workspace.
Replit’s pricing page lists these plans. Replit does not list a separate charge for Cloud Agents.
| Plan | Monthly price | Cloud Agents | Notes |
|---|---|---|---|
| Core | $20 ($18 billed annually) | Not listed | $20 toward more powerful models |
| Pro | $100 ($90 billed annually) | Yes | $100 credits, up to 15 collaborators, premium support |
| Enterprise | Custom | Yes | SSO, SCIM, audit logs, single-tenant and private networking options |
How to use Replit Cloud Agents
These steps follow Replit’s Get started guides for repository work:
- Open Repositories at replit.com/repos, choose GitHub or GitLab and connect your account. Review the requested access before approving.
- Find your repository and select Use in chat. Ask Replit to run the app so it prepares the sandbox and starts a preview.
- Describe one focused change, for example a new heading or a fixed link, and check the updated preview.
- Ask Replit to test the change on desktop and mobile and to run the relevant checks. Read the final report to see what passed and what it could not verify.
- Add any API keys through Secrets, not in chat.
- Ask Replit to push the change to a new branch and open a pull request that summarizes what changed and how it was tested. For GitLab, ask for a merge request.
- Review the diff in GitHub or GitLab, leave comments, and let Replit update the same request.
Shared environments, skills and parallel agents
Shared environments. The blog says a Cloud Agent explores your codebase and configures an initial VM that runs your app. Environments support many languages, multi-repo microservices, Docker images, databases, queues and caches. Credentials come from external secrets managers through a credential broker.
Repository guidance. AGENTS.md and CLAUDE.md files travel with the code, and Replit discovers SKILL.md skills under .agents/skills and .claude/skills.
Workspace memory. When review feedback is worth keeping, the agent proposes an update to a skill or drafts a new one, and engineers approve it first. Replit says broader workspace memory cut its internal token usage by 51% and a common data task from 16 minutes to 1 minute.
Parallel work. Ask Replit to run independent tasks in separate chats. Keep dependent tasks, or tasks that change the same files, in order.
Replit Cloud Agents vs the old ticket workflow
Replit positions Cloud Agents against the way non-engineers have usually proposed product changes.
| Step | Ticket workflow | Replit Cloud Agents |
|---|---|---|
| Who writes the change | An engineer, after the ticket is scheduled | Anyone who can describe it; the agent edits the code |
| Running the app | Each contributor repeats setup | Starts from a shared environment that is already running |
| Proof it works | Screenshots requested from an engineer | Browser tests with screenshots and video on the pull request |
| Review feedback | Contributor turns comments into code | Agent updates the same request |
| Who merges | Engineering | Engineering |
Other vendors offer similar cloud agents. Compare our guides to GitHub Copilot Automations, Cline cloud agents and Devin Desktop 3.11.
Workflows, security and limitations
- Support fixes: share recurring customer feedback, ask Replit to trace the cause and propose a tested fix.
- Code questions without edits: ask how a feature works or where it is implemented. You can stop after the explanation.
Security: connecting an account does not grant permissions you do not already have. Sandbox isolation does not remove the permissions of credentials you provide, so give development credentials only the access they need.
Limitations: a preview is not production; a passing test does not replace code review; updating a saved environment does not change a sandbox already running; workspace memory is early access; and Microsoft Teams support is still listed as coming soon.
For other agent tools, see our Kiro Auto Approve guide and our Claude Code power-user guide.
Frequently asked questions
What are Replit Cloud Agents?
They are Replit agents that work on an existing GitHub or GitLab repository. You describe a change in plain language, and the agent edits a development copy, tests it in a cloud sandbox and can open a pull request or merge request for your team to review.
Which Replit plans include Cloud Agents?
Replit’s October 27, 2026 announcement says Cloud Agents for existing repositories are available to all Pro and Enterprise customers. Replit’s docs add that repository-based development is early access and availability can differ by workspace.
How much does Replit Pro cost?
Replit’s pricing page lists Pro at $100 per month, or $90 per month billed annually, with $100 in credits. Enterprise pricing is custom. Replit does not list a separate price for Cloud Agents.
Do Replit Cloud Agents merge or deploy code?
No. Opening a pull request does not merge or deploy it. You or an authorized teammate merges after the required reviews and checks, and deployment follows your team’s existing release process.
Can I start a Replit Cloud Agent from Slack?
Yes. You can mention or message @Replit in Slack to investigate an issue or turn a proposal into a pull request. Replit says the Slack integration is available to all customers and Microsoft Teams support is coming soon.
Does Replit read AGENTS.md and CLAUDE.md files?
Yes. Replit uses AGENTS.md and CLAUDE.md guidance within its directory scope, and discovers enabled SKILL.md skills under .agents/skills and .claude/skills, reading relevant ones when needed.
Sources
- Replit blog: Anyone can now bring their ideas into the company codebase (October 27, 2026)
- Replit Docs: October 30, 2026 updates
- Replit Docs: Code with Replit
- Replit Docs: How coding with Replit works
- Replit: Pricing and plans
Image: Replit logo, public domain (simple geometric mark; trademark of Replit, Inc.), via Wikimedia Commons. Rendered on a white background. FreeAnswers is not affiliated with Replit.
