Refactor an app and try a Telegram API upgrade

One developer used Replit Agent to refactor a card app and to attempt a Telegram bot update, with mixed results.

Done with Replit Agentยท Advanced

What they did
They first had Replit Agent work on a card-collection app, including a database change so one card could appear in more than one collection. The same agent was then used on a legacy Telegram bot: they had to start by creating a new project, add the old code, and ask for the newer API behavior to be copied over.
How it went
The card app changes mostly went well. The Telegram bot work did not: even a simple bot took several rounds, and the legacy upgrade never behaved properly. Over a month, they spent the $25 plan plus about $4 in extra credit, and the Telegram effort was described as a disaster.
Tips
If you want to test a bot upgrade, begin with a clean project and expect to iterate. Be careful with adding unit tests in Replit Workflows, since they can interfere with the workflow setup.

Try it yourself with Replit Agent

Update my [project name] in Replit from [old API or library] to [new API or library]. Keep the current commands and behavior working where possible, and after each change, run the app and report any errors you find. If a database change is needed, propose the schema update first and wait for my approval before altering or deleting any data. Before you send, publish, or otherwise make anything irreversible, pause and ask me to confirm. Then list the commands or features you tested and what still needs attention.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on aiartisan.substack.com โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.