Missions

Achieve ambitious outcomes on controlled budgets with Replit Missions.

Subscription growth · $500 shared limit

Where paid conversion drops
Pricing auditCheckout funnelSignup testsPerformance trace
Finding
Reduce checkout friction
Research spend
$42 included in $312 spent
Measured p95
380ms · below 400ms target

Subscription growth · $500 shared limit

Pricing → signup → checkout
Goal
Improve paid conversion
Scope
Pricing and checkout updates
Budget
$500 across all agents
Approval
Required before publishing

Subscription growth · $500 shared limit

Grow paid subscriptions
Goal
Improve paid conversion
Scope
Pricing and checkout updates
Budget
$500 across all agents
Approval
Required before publishing

Subscription growth · $500 shared limit

1Research2Build3Test4Review
Research
$42 spent
Build
$186 spent
Test
$64 spent
Review
$20 spent

One shared budget · $188 remaining

Subscription growth · $500 shared limit

Outcome
Grow paid subscriptions
Deliverables
Pricing + checkout improvements
Total limit
$500
Available
$188 of the original limit
Success checks
Billing, signup, p95 < 400ms
Boundary
Approve before publishing

Subscription growth · $500 shared limit

Evidence for the growth mission
Pricing auditCheckout funnelSignup testsPerformance trace
Finding
Reduce checkout friction
Research spend
$42 included in $312 spent
Measured p95
380ms · below 400ms target
My mission: Grow paid subscriptions.$500 budget

Paying customers

128K

Monthly revenue

$256K

Performance

380ms
$312 spent$188 remainingApproval before release

Subscription growth · $500 shared limit

Reviewed the conversion funnelUpdated pricing and checkoutValidating subscription flowsWaiting for release approval
Spent / limit
$312 / $500
Remaining
$188

Subscription growth · $500 shared limit

$312 of $500

$188 remaining 62.4% used

Research
$42
Build
$186
Test
$64
Review
$20

Ask before increasing the $500 limit.

Subscription growth · $500 shared limit

checkout.spec · passedbilling.spec · passedsignup.spec · passedperf.p95 · 380ms
Testing spend
$64 included in $312 spent
Budget remaining
$188
Release
Final review in progress

Subscription growth · $500 shared limit

Approve subscription changes?
Changes
Pricing, signup, and checkout
Total budget
$500 · unchanged
Spent
$312
Remaining
$188
Next step
Publish after your review
ReviewApprove

Subscription growth · $500 shared limit

checkout.spec · passedbilling.spec · passedsignup.spec · passedperf.p95 · 380ms
Testing spend
$64 included in $312 spent
Budget remaining
$188
Release
Awaiting your approval

Subscription growth · $500 shared limit

Pricing and checkout changesTest evidence attachedBudget summary attachedPublish after your approval
Spent / limit
$312 / $500
Remaining
$188

Set the budget. Stay in control.

Set a spending limit for each mission and track usage as agents work. Review any increase before it goes ahead.

See spend as it happens

Each step shows what it used and what remains of the limit.

Mission budget$50.00 limit
$31.70
$31.70spent63.4%
$18.30left36.6%
Spend by step4 steps
  • Plan and scope$6.40
  • Build checkout flow$18.25
  • Run test suite$4.90
  • Judge review$2.15

Run multiple missions at once

Move different projects forward in parallel. See which missions are done, running, or waiting on you.

My missions
Checkout flowDone
Payment testsRunning
!Fraud rulesNeeds approval

Approve any change to the limit

Review the reason for a higher budget, then decide whether to approve it or keep the current limit.

From plan to outcome.

Set the outcome, review the plan,
and follow progress as agents get to work.

Start a mission

Mission templates

  • Performance

    API latency

    Benchmark and iterate toward an agreed response-time target.

    • GitHub
    • Linear
  • AI quality

    Support assistant

    Improve answers against a rubric and held-out test set.

    • GitHub
    • Google Drive
    • Notion
  • Customer growth

    Campaign conversion

    Improve landing pages and lead capture against a conversion baseline.

    • HubSpot
    • Figma
    • GitHub
  • Complex builds

    Rust rewrite

    Rewrite a component and verify parity with the original.

    • GitHub
    • Linear
  • Rebuild software

    Booking experience

    Recreate availability, reservations, rescheduling, and cancellations.

    • GitHub
    • Figma
  • Customer growth

    SEO/AEO

    Audit and improve your site for search engines and AI answers, then measure visibility and qualified traffic.

    • GitHub
    • Airtable
  • AI quality

    Evaluation harness

    Improve judging consistency against reviewed examples.

    • GitHub
    • Google Drive
  • Performance

    App load speed

    Find bottlenecks and measure improvements under consistent conditions.

    • GitHub
    • Figma
  • Rebuild software

    Agreement workflow

    Recreate drafting, approvals, signature handoff, and status tracking.

    • GitHub
    • Google Drive
    • Notion

Bigger outcomes, without managing every step

  1. Aim for bigger outcomes

    Pursue important work you haven’t had the time or capacity to tackle. Define success, then let Missions plan and coordinate the work.

  2. Spend less time managing the work

    Agents build, test, and iterate together. An independent AI judge checks results against your criteria, while progress updates help you see where things stand.

How a mission works.
From setup to finished work.

RESULTSEVALUATIONAGENT EXECUTIONMISSION AGREEMENT

Observe your agent swarm coordinate, share updates, and discuss its work.

123

Parser batching

3 agents · example thread

  1. 1

    Agent 1

    Agent 2, test token batching. Agent 3, check buffer reuse. Keep partial Markdown rendering as it streams.

  2. 2

    Agent 2

    Batching preserves partial updates and the final syntax tree.

  3. 3

    Agent 3

    Both patches are isolated and ready for verification.

Eval judge

Work gets checked, then improved.

Agents do the work. A separate AI reviewer checks it against the goals you agreed on and sends back specific feedback when something needs fixing.

Eval judge
Needs changesAI reviewer checks itagainst your agreed goalsAgents do the workYou review the result
Example

The proposal is missing its data retention terms.

In this example, the agreed goal requires the proposal to explain how long customer data is kept and when it is deleted. The reviewer finds that neither is covered and sends the draft back. The agents add the missing terms, and the reviewer checks the revised proposal before it reaches you.

MissionActive···

Build a repeatable evaluation pilot to detect improvements and regressions in your customer-support assistant.

Overview
  • Evaluation goals agreed

    Success criteria and scope confirmed.

  • Policy-grounded test suite

    Identify the assistant and policy sources —

    Assistant and policy sources have not yet been provided.

  • Calibrated scoring

    Awaiting source-grounded cases before scorer calibration.

Progress updates

Know where the work stands. Without asking.

As the mission runs, your agent writes short updates so you can follow progress and respond when your input is needed.

  1. 01What changedThe work finished since the last update.
  2. 02What’s nextThe step the agent is taking now.
  3. 03Blockers and questionsWhere it is waiting on a decision from you.
  4. 04Evidence to reviewLinks to the drafts and files behind each update.

All your missions, in one view.

Starts from a conversation

Type /mission, accept a suggestion from your agent, or start from the overview. The mission stays where the idea began.

Works with your connected knowledge

Connect the tools you already use so the agent works inside your docs, tickets, and repos with the permissions you set.

Built for engineering control

Changes arrive as pull requests and reviewable files. Anything outside the agreed boundaries waits for a person.

Frequently asked questions.

What is Replit Missions?

Replit Missions uses agent swarms to turn ambitious goals into outcomes across complex builds, optimization, and business growth. It is designed for entrepreneurs, SMBs, and enterprise teams with work that takes multiple steps and iterations to complete.

How are Missions different from Routines?

A mission works toward a defined outcome, such as improving signup conversion. A routine runs on a schedule, such as sending a weekly signup report.

How do I start?

Describe the outcome you want to achieve. Work through the approach, success criteria, and boundaries, then review the mission agreement before execution. A useful starting goal names both the work and how you will judge the result, such as rebuilding a workflow against a feature checklist.

What is an agent swarm?

An agent swarm is a group of agents coordinating work toward a shared goal, with parallel work where appropriate. For a software build, that work can include implementation, testing, and evaluation, with results informing the next iteration.

How do I evaluate the result?

Each mission has a judge that evaluates the work against the success criteria you agree on at the start. The mission keeps working until those criteria are met, its budget runs out, or it needs your input.

What does it cost, and which plans include it?

Set a maximum budget for your mission upfront. Work performed during the mission counts toward that budget.

What controls are available?

You can set a maximum budget, decide which decisions require your input, and choose which connectors the mission can access. You agree on the goal and success criteria before work begins, and you can exit mission mode at any time. Messages you send while the mission is active count toward its budget.

Build your self-driving company.
Start with a mission.