Introducing Replit Missions
Introducing Replit Missions
Today, we’re launching Replit Missions to help your teams take on the complex work they haven't had time or capacity for: winning more enterprise customers, improving product performance, or replacing legacy software. You define the outcome, and Replit coordinates a swarm of agents to plan, build, test, and iterate toward it within the budget and boundaries you set.
At Replit, we wanted to explore bringing application monitoring in-house to reduce costs and gain more control. We gave Missions the goal of building DataCat, a platform we could customize and run on our own infrastructure. In two days, within a $3,000 budget, a swarm of agents built dashboards, alerts, and application tracing, then tested the platform against measurable performance and reliability goals.
DataCat is one example of the work Missions makes possible. Missions brings the same approach to your team’s goals, without requiring you to build and maintain the complex infrastructure necessary to coordinate an agent swarm.
Start with complex work you don’t have the capacity for
You can start with a mission like “win our first 10 paying enterprise customers.” You don’t need to decide upfront which industries to target, which buyers to reach, or which customer problem to solve first. Finding and evaluating those approaches is part of the work you delegate.
During setup, Missions asks questions to define success. What counts as an enterprise customer for your business? Do paid pilots count toward the first 10, or does success mean signed annual contracts above a minimum value? Your answers shape which accounts the mission prioritizes and how it measures results.

Stay in control of the budget and boundaries
Your Missions agreement sets the spending limit and which actions require your permission. You also agree on acceptable tradeoffs, such as offering paid pilots or discounts on annual contracts.
For example, you can cap the mission's spending at $1,000 and require approval before the Agent contacts prospects, shares a proposal, changes customer-facing sales materials, or makes product commitments. These limits and approval requirements remain in place as the approach evolves.

Let agents plan, build, and iterate
For your enterprise sales mission, agents might research target accounts, build tailored demos, and prepare outreach for your approval. Swarms let them work in parallel, with one agent researching buyers while another develops a demo. After approved outreach is sent, the mission can return to review which accounts and messages are generating qualified conversations.
Those responses guide the next round of work. The agents might focus on an industry showing stronger interest, refine a demo around a recurring buyer question, or revise messaging that gets few responses.

Figure shows agent swarms working on improving Replit Slides
Why agent swarms make Missions more powerful

Chart shows NumPy benchmark speedups by agent count using Auto (Max) and Auto (Power).
Agent swarms give Missions the capacity to explore multiple solutions at once, share insights, and build on each other’s discoveries. For a problem like performance optimization, agents test different implementations in parallel, use shared findings to refine their approaches, and work together to validate correctness as they identify faster solutions.
We put this to the test across 13 representative benchmark tasks using NumPy. Agents explored alternative implementations, optimized memory access patterns, and validated correctness automatically. With Auto (Max), a single agent achieved speedups of up to 4×. A 16-agent swarm reached 17×, and a 32-agent swarm reached 19×. Auto (Power) showed the same pattern: 2×, 7×, and 9×, respectively.
The striking result is how much further the swarms got. Exploring more approaches in parallel helped Missions find substantially faster implementations, showing the potential of agent swarms for complex optimization work.
See progress and know how results are checked
During planning, you choose what you want to hear about, including blockers, progress updates, and general status, and how often: immediately, in a daily digest, or weekly. You can close your laptop and let the cloud agents work. Missions sends updates according to your preferences and reaches out when it needs your input.
An independent AI judge checks results against your agreed success criteria, and agents use its feedback to refine their work. A mission is marked complete when those criteria are met. If the budget runs out first, work stops with the outcome still unresolved.
Whenever you want a closer look, you can see completed work, active tasks, and next steps, including anything awaiting your approval.
Building DataCat: our own application monitoring platform with Missions
We used Missions to build DataCat, an application monitoring platform we can run and customize ourselves. In 2 days, with a $3,000 budget, Missions built a working platform with dashboards, alerts, and application tracing from goals our team set in the Mission Contract, then tested it against measurable performance and reliability goals.
Missions also built DataCat’s own agent, which collects monitoring data from each server, and its tracing libraries. DataCat can run independently of the original platform’s agent and libraries.
To test whether DataCat could help diagnose a failure, we deliberately introduced a database bug. DataCat raised an alert in 38 seconds, beating our 60-second target, and traced the failure to the exact database query and its logs.
The mission also built sample applications for a three-hour load test. DataCat stored 26 million records of application activity and 4.4 million log entries with no data lost, while searches and alerts kept running. All 36 data-correctness checks and 15 alert-reliability checks passed.
The mission compared its monitoring code with the original platform’s tracing library and agent. In matched Node.js tests, the application handled more requests with less monitoring-related processor overhead. DataCat’s agent also used less memory and made logs searchable sooner.
We then compared DataCat with a monitoring platform built with the same initial prompt using /goal in Claude Code. DataCat accepted all data types from the original platform’s agent (logs, metrics, host data and traces), while the Claude Code build accepted logs only. DataCat passed more API compatibility checks and took in traces and metrics faster. The Claude Code build covered more product areas and took in logs faster. The table below summarizes the results.
| What we tested | Results with DataCat |
|---|---|
| Build time and budget | 2 days, within a $3,000 capped budget |
| Detecting a deliberately introduced database bug | 38 seconds, against a 60-second goal |
| Handling sustained activity | 26 million activity records + 4.4 million log entries over 3 hours, with zero data loss |
| Data accuracy and alert reliability | 51 of 51 checks passed |
| Monitoring efficiency in Node.js tests | 39% more requests handled with 51% less monitoring-related processor overhead |
| API compatibility (separate test suite) | 51 of 56 checks passed on each DataCat storage engine, versus 45 of 56 for the Claude Code build |
| Application trace intake | 49,000 traces/second with DataCat (Postgres), versus 9,800 for the Claude Code build: 5× faster |
| Metric intake | 405,100 metric points/second with DataCat (Postgres), versus 224,600 for the Claude Code build: nearly 2× faster |
| Agent memory under load | 82–108 MB for DataCat’s agent, versus 319 MB for the original platform’s agent (240-second average) |
| Time until logs are searchable | 0.5 seconds with DataCat’s agent, versus 4.2 seconds with the original platform’s agent (median) |
| Storage engines | 2 (Postgres and ClickHouse), versus 1 (SQLite) for the Claude Code build |
Notes: These controlled tests do not establish performance against the original platform’s hosted service or on Replit’s production systems. The Node.js comparison used matched workloads and monitoring work.
The build comparison used one run per setup on identical cloud machines, scored only shared product areas, and used the original platform’s agent version 7.56.2 to send data. API compatibility was a separate test suite from data correctness and alert reliability.
The agent comparison used repeated runs of the same workload, one agent at a time, both sending to the same Radar server. The reference was the original platform’s agent version 7.56.2.
DataCat gives us a working foundation we can inspect, customize, and run on our own infrastructure.
We’re open-sourcing a self-hostable version of DataCat today for broader use.

Preview of DataCat, our own application monitoring platform built with Missions
Put your ambition to work
Missions continues to impress us with the range of goals it can take on. On E-Commerce Bench, an agent starts with ¥100,000 and runs online stores for a simulated year, choosing suppliers, avoiding scams, and setting prices. In a single run, Missions grew that to ¥4.82 million, roughly 48 times the starting money, a state-of-the-art result more than three times the best on the public leaderboard.
We believe Missions is a practical step toward the Self-Driving Company: people set direction, make consequential decisions, and remain accountable while agents carry the execution and coordination.
That changes what a small team can consider taking on. The product launch you keep postponing. The refactor that takes an entire group of tenured engineers. The off-the-shelf software you want to build in-house but don’t have bandwidth for.
We’re excited to bring Missions to the world and see what you’ll take on with it.
Click “New” in the sidebar, select “Mission,” and describe your most ambitious goal.
Learn more: replit.com/missions or talk to our sales team about bringing Missions to your organization.
Source: Replit Blog · replit.com