Been using Replit for over a year, and heavily the last three months while building ground-up agentic applications for my businesses. I have a few feature requests that would materially improve the experience:
1) Max Autonomy: real-time cost visibility + budget controls
Max Autonomy can be extremely cost-effective if you spend time up front on a solid PRD and phased plan. In my experience, it can be roughly half the cost of running the Power model.
The problem is there’s no clear visibility into what you’re spending while it’s running. For example, I let it run for ~30 minutes last night and it stopped because it said it completed all tasks. There were still bugs to work through, but that run cost about $4.12—whereas using the Power model would likely have been $15+ for the same work (before any back-and-forth bug fixing, which often costs more than the initial build).
Request:
-
Show an active, near-real-time billing meter while Max Autonomy is coding (running total + rate).
-
Add an optional budget cap so it can:
-
stop when the cap is hit, and
-
produce a wrap-up summary of what it did, what’s left, and the next recommended steps, then pause.
-
2) Billing history by app across multiple months
I can’t easily see what I’ve actually spent on a specific app over a multi-month build. The current Billing/Usage view seems limited to a single billing cycle, and anything longer-term requires manual tracking.
Because I work on multiple Replit projects at once, it’s difficult to attribute costs accurately across apps beyond the monthly rotation.
Request:
- A multi-month billing history view with per-app/project cost breakdowns, so I can see what an app cost over 2–3+ months without manual logging.
3) More built-in connectors / integrations
Many third-party integrations (API keys, webhooks, app setup) require a lot of human work outside Replit. Built-in connectors would reduce friction substantially.
Request examples:
- Integrations for Facebook apps (lead gen, posting, scheduling, etc.) and other common platforms, so these workflows don’t need to be manually built and configured off-platform.
4) Native ability to sell a repo/project on Replit
It would be valuable to sell a repo (or a remix) directly to other Replit users—so they can access it with a Replit account—enabling straightforward distribution of software that can be white-labeled and/or customized.
Request:
- A built-in marketplace/flow to sell a repo/remix, handle access, and keep delivery inside Replit.
Why this matters (retention + workflow)
Without a native “sell a repo” flow, I’d likely move builds to other environments (e.g., Windsurf + Vercel) to distribute to clients. That’s not ideal—I’d rather stay in one environment I understand and can manage for clients, and it also keeps ongoing usage within Replit.