Quick answer
The local whoburnedmore CLI command is npx whoburnedmore --local. Decline its optional publish offer to keep the report local. The standard command signs in and submits daily aggregates. Neither mode submits prompts, source code, or filenames.
What this guide answers
The reader wants to understand what Replit credits mean for agentic app building.
Best for
Replit users building apps with Agent and teams comparing app builders to local coding agents.
Key facts, checked November 8, 2026
- Replit Agent uses effort-based pricing billed per checkpoint, and each request produces one checkpoint. Plan Mode can bill for reasoning even when it changes no code. source
- Replit's current plans are Starter (free), Core ($20/month, or $18/month billed annually), Pro (from $100/month, or $90/month billed annually) and Enterprise. Teams is retired and has been folding into Pro since March 3, 2026. source
- Third-party AI used inside your app (Claude, ChatGPT, Gemini) is charged at the provider's public API rate from your Replit credits. The usage dashboard can lag by up to 30 minutes. source
- Replit credit packs for Core and Pro are $100 for $100, $300 for $290, $500 for $480 and $1,000 for $950. They expire after 6 months, with optional auto-reload. source
Credits follow build ambition
A small prototype and a production app do not consume the same budget. Estimate credits by phase so you know when a build is drifting.
- Prototype
- Auth and data
- UI polish
- Deployment
Separate platform spend from coding-agent spend
Replit credits may cover platform-specific work, while local agents like Claude Code and Codex burn elsewhere. Both belong in your AI coding budget.
- Platform credits
- Local tokens
- Deployment cost
- External APIs
Use a stop rule
When an app builder loops on the same bug, stop and inspect manually. Repeated regenerate prompts can burn credits without improving the code.
- Stop after two failed repairs.
- Read logs.
- Patch narrowly.
Compare tools by artifact
The output matters more than the tool. Compare Replit Agent, Lovable, Bolt, v0, and local agents by whether they produce maintainable code for the task.
- Working app
- Readable code
- Deploy path
- Ongoing cost
What actually draws down Replit credits
Agent work is only one meter. Replit's usage-based billing docs list several other things that charge the same balance. Autoscale deployments bill compute units: 1 RAM-second is 2 units and 1 CPU-second is 18 units. Production PostgreSQL bills for compute hours and storage, and suspends after 5 idle minutes. Outbound data transfer past the plan allowance also bills (Core includes 100 GiB). Development databases are free. If your balance drops between Agent sessions, check deployments and databases before you blame Agent.
- Agent checkpoints and Plan Mode reasoning
- AI integrations called by your app, at provider API rates
- Autoscale compute units and requests
- Production database compute and storage
- Outbound data transfer
Set a hard ceiling before a long build
Replit's spend controls are blunt but they work. When a usage limit is hit, services are suspended until you raise the limit or the next cycle starts. Organization budgets are set in $500 steps, and per-user limits are Enterprise-only. Replit also says it asks for confirmation before a paid Agent action starts, so read those prompts during a repair loop instead of clicking through. For a planned build, write the expected checkpoint count per phase next to the limit you set. Every subscriber gets some free Agent checkpoints once, so the first build is not a good guide to steady-state cost.
- Set the usage limit before prototyping, not after the invoice.
- Use Replit's cost estimator at agent-pricing.replit.app to sanity-check a plan.
- Watch a suspended production app if a limit trips mid-month.
Keep local agent spend in the same review
whoburnedmore does not read Replit usage. Replit Agent runs in Replit's cloud, so its credits only show in Replit's own usage dashboard. If you also use Claude Code, Codex or Cursor locally on the exported repo, npx whoburnedmore reports those token totals. Put both numbers in the same weekly budget line.
Common questions
How are Replit Agent credits charged?
Per checkpoint, using effort-based pricing. Larger or more complex requests cost more, and Plan Mode can charge for reasoning even when no code changes.
Do Replit credits roll over?
Replit's Pro docs say Pro credits roll over for two months (the launch blog said one month). Rollover on Core is not documented, so assume it does not.
What happens when I hit my Replit usage limit?
Services are suspended until you raise the limit or the next billing cycle starts. Deployed apps are included, so set limits with production in mind.
Can whoburnedmore track Replit Agent?
No. Replit usage stays in Replit's dashboard. whoburnedmore covers local coding agents such as Claude Code, Codex and Cursor.