How to test and debug a Replit app with an AI agent

You built your Replit app in an afternoon of vibe coding. Then comes the work around the build: clicking through every screen, tracing a bug to its cause, collecting payment keys, filling in store forms.
Replit builds the app. An AI agent in Aside does the work around it, in your own browser, on the sites you are already signed in to. This guide follows Minsang Daniel Kim (@msdkim on X), a Replit ambassador in South Korea, from an interview on November 18, 2026. We ran the testing and debugging steps ourselves on a small app we built with Replit Agent, and the mobile, payment, store and merge conflict steps are as Daniel described them to us.
What can an AI agent in Aside do for a Replit app?#
It works next to Replit Agent: Replit builds, and Aside tests the result and handles what sits outside the project. Aside's agent can click through your app like a new user, trace a failing screen to the code, collect keys from other services, and operate the Replit interface.
Daniel makes web and mobile apps on Replit and uses the two side by side. "I'm not like a developer," he told us.
He said Replit Agent has more tools because it is native to the workspace: built-in integrations, MCP support with other services, and Replit-only features. He uses it for those. The rest: "for just general like coding and updates, I use the Aside Agent."
"I don't use Codex or Claude Code anymore," he said. He also has Aside research his questions and manage his subscriptions and email. "Aside is like literally my main tool these days."
He has said as much in public. In a November 2026 post on X, he wrote: "Apart from Replit, which is my fixed main tool, I've been using @AsideAI more than any other apps recently for my tasks, just because it can do anything."
Replit Agent tests its own work too. Replit's App Testing docs say Agent tests the app in an actual browser, decides for itself when to test, and keeps App Testing off in Free Mode.
To set up, open the Replit project page in Aside and open the side panel, which attaches the page to the task.
How do you test a Replit app's UI on web and mobile?#
Open the app in Aside and ask the agent to go through it as a first-time user with a test account. Name each flow and ask for every failure with its steps. For a mobile app, have it click through a simulator.
Start with this prompt.
This is the Replit app I'm building. Sign up with my test account, then click through onboarding, checkout in test mode, and settings. List everything that breaks, with the steps to reproduce it. Do not change any code.
We tried it on Streaks, a small habit tracker Replit Agent built for us in Free mode. Aside went through all four flows. Sign up, check-ins, the test checkout and saving settings worked, and it came back with six things to fix, each with steps to reproduce it.
These were the first three.
- Onboarding skips step 3 and saves an 08:00 reminder the user never chose.
- The dashboard shows the date as raw text: 2026-11-18T00:00:00.000Z.
- Settings and checkout open before onboarding is finished, then fail with a vague "Please try again" message.
Here is that answer.
Aside's answer to the UI test prompt on our Replit app: what to fix, each with steps to reproduce it
A non-developer on Replit's community forum, with an iPhone app approved by Apple, was checking it by hand. On October 20, 2026, they wrote: "I will be testing over 480 listings later to make sure the basis of the app works."
Daniel said Replit can open the web, iOS and Android simulators, "but then the agent can't click through everything." So: "I just make Aside go through all of that whenever I make an update." His verdict: "that usually works out very well."
Replit lists App Testing for two kinds of web app, so a Replit mobile app is where this matters most. He turns on the iOS simulator on his own computer and has Aside go through it with Computer Use.
Computer Use lets a task read and control apps on your Mac or Windows computer. It is off by default, and you turn it on in Settings > Agents.
Computer Use in Settings > Agents
How do you debug a Replit app when the same bug keeps coming back?#
Ask for the cause before the fix. Have Aside open the project files and get the file, the function and the reason for each bug. Then ask for the smallest change and rerun the same failing steps with your test account.
Building and testing feed each other. Replit Agent builds, Aside reports what to fix, and the fix goes back into the Replit project.
Here is that loop from our test.
How Replit Agent and Aside worked on the same app in our test
For Daniel, "the most useful case was debugging," which he described as going into the codebase and finding the bugs.
Paste the failure list from the UI test under this prompt.
For each bug on the list, open the project files and tell me the file, the function and what is wrong. Do not change any code.
We ran this step in Aside Code, an experimental, Mac-only coding agent you turn on under Settings > Experimental. It works in a folder on your Mac, so download the project from Replit first.
It named a file and line numbers for each bug. For the skipped step: the Continue button turns into the Finish setup button in the same spot, so the click that should open step 3 also submits the form. We opened those lines and they match.
Here is that diagnosis.
Aside Code naming the file and lines behind each bug
We stopped there. We have not applied the fixes or rerun the test.
This next prompt is the step we have not run.
Make the smallest fix for each bug. Then run the same steps again with my test account and tell me which still fail. Do not publish the app.
You can also paste the diagnosis into Replit Agent, which then has the file, the function and the reason.
A fix counts when the failed steps pass.
If Replit Agent keeps looping, Replit's help page says to stop it, restart compute, and open a new chat with one goal per message.
When a merge conflict happens, Daniel doesn't want to go through it: "I just ask Aside to do it."
Start from this prompt.
There is a merge conflict in this project. Keep both changes where they do not overlap, and list every place where you chose one side. Do not publish until I have read the list.
How do you connect a payment provider Replit has no integration for?#
Give Aside the provider's name and let it do the browser work: sign in with your saved login, find the test-mode keys, and add them to the project. You step in when the provider asks for a check only you can pass.
Hooking up logins and payment systems is what made him realize Aside could be his main vibe coding tool. "Stripe doesn't work in Korea," he said, and South Korea is not on Stripe's list of countries where a business can open an account. "I can't get a payout."
So he used Korean payment systems, which he called a pain. He asked Aside to go into those providers' websites, get all the credentials and hook them up to his service. He said it did that perfectly.
This is the part he had not found another way to hand off: go somewhere, apply for something, get the credentials and put them on your platform.
Aside Vault signs in through autofill, so the agent uses the login without receiving the raw password. API keys are different: the agent reads a key off the page to place it, so say where it goes.
Use this prompt with your provider's name.
I need to accept payments with [provider]. Sign in to their developer dashboard with my saved login and get the test-mode keys this project needs. Put them in the project's Secrets, not in the code. Stop before submitting any business verification or switching to live mode.
"I had to take care of the logins and stuff in the middle," he said. When a site asks for MFA, a passkey approval or identity verification, you complete that step and the task continues.
How do you handle Replit settings, builds and app store submissions?#
Ask Aside to do them on the page, the way you would by hand. It can change a setting in the Replit interface, start a build, and fill in a store listing form while you keep the final click for yourself.
He said Replit now has so many features that he built a Discord bot to manage all of his Replit projects. Aside on his Mac mini drives it: "it's like using Aside in Discord."
Aside can be reached from Discord, Slack and Telegram.
The Replit MCP server docs say any MCP client can create, update and publish Replit Apps. For what Replit MCP does not expose, such as choosing the model, he has Aside click it in the Replit interface.
His bot uses EAS and submits to the Play Store and App Store for him. For iOS, Replit's native mobile docs say a release goes from Publish to TestFlight to App Store Connect.
Reddit user Adventurous-Win-1489 wrote in r/replit on February 21, 2026, about a first app: "Building the app took less than a week." And: "Getting it approved took a month."
This prompt covers the build and the form.
Start the EAS build for this project. Then fill in the store submission form from my listing doc, using the test build. Stop before submitting for review.
What does it cost to debug a Replit app this way?#
It depends on what you connect. Aside's Free plan includes 500 credits per month, and you can connect an AI subscription you already pay for and run the debugging on that. Replit builders say debugging is the costly part of a build.
Reddit user 2FDots wrote in r/replit on August 9, 2026: "The debugging always costs significantly more than the task builds."
Replit's support account explained in the same thread on August 11, 2026: "a debugging prompt reads more context and can touch more of the app, so it will use more compute."
Reddit user Groovy_Cabbage wrote in r/replit on September 19, 2026, that they do their planning and debugging on a subscription they already had, and "built a TON of new features on the Claude subscription I was already paying for."
In Aside, you connect a subscription under Settings > Models > Providers. The provider's own limits still apply. Our Aside Code task ran on a connected ChatGPT subscription, not on Aside credits.
What should stay under your control?#
Anything that spends money, publishes, or touches real customer data. Use a test account, keep live payment keys out of test runs, and end every prompt with a line saying where to stop. A test pass covers only the flows you named.
New Aside tasks start in Guard mode, which asks before working in folders outside the approved ones. That covers files and folders, not web actions or purchases, so the stop line in your prompt does that job.
Settings > Passwords > Access policy for AI agents sets when agents may use saved logins: Always allow, While unlocked, or Never.
What questions do Replit builders ask?#
Four questions are still left: whether you need to be a developer, why an Aside chat can come detached from its tab, whether this works for an app built outside Replit, and how to repeat one test every time you ship.
Do I need to be a developer to use this?#
No. Daniel is a teacher, not a developer by trade, and the prompts in this guide are plain sentences, like the ones you already write when vibe coding.
Why did my Aside chat come detached when I switched tabs?#
Daniel hit this after switching to other tabs and coming back, and thought it was a bug. It is intentional: Aside automatically closes tabs it used for tasks. You control it under Settings > Agents > Clean up agent tabs, which can be set to After 2 hours.
Does this work for a vibe coded app that isn't on Replit?#
Yes. For a project on your own computer, the Aside CLI starts a browser agent session from the terminal: aside "Open localhost:3000 and run a smoke test".
Can I run the same test every time I ship?#
Yes. Write the procedure once as a skill: which flows to cover, which test account, and what counts as a failure. A routine then starts a new task on a schedule while your computer is awake and Aside is running.
Next, read how developers use Aside. Then download Aside and run the UI test prompt on one flow.