Update a legacy Telegram bot and refactor an app
The author used Replit Agent to update a Telegram bot to a newer API, which only worked after some iterations, and to refactor a card-collection app including a database schema change.
What they did
For the Telegram bot, the author found the Agent needed a project created first, so they spent $0.25 on a fresh bot and then added their legacy code. They asked it to copy the new API's functionality. For the card app, they had it do non-trivial refactors, including a database schema change so cards could belong to multiple collections.
How it went
The card-app refactor went fairly smoothly. The Telegram update was a disappointment: even a basic bot took several iterations, and the legacy-code update did not work well. The author calls it a disaster.
Worth knowing
The whole month of experiments used the $25 plan plus about $4 of extra credit. Adding unit tests to the card app disrupted its Workflows, so the tests ended up unused.
Labels
The author used Replit Agent to update a Telegram bot to a newer API, which only worked after some iterations, and to refactor a card-collection app including a database schema change.
For the card app, they had it do non-trivial refactors, including a database schema change so cards could belong to multiple collections.
For the card app, they had it do non-trivial refactors, including a database schema change so cards could belong to multiple collections.
The author used Replit Agent to update a Telegram bot to a newer API, which only worked after some iterations, and to refactor a card-collection app including a database schema change.
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Replit Agent
- Source
- blog
- Source date
- undated
- Accounts
- 1
- In registry since
- Oct 14, 2026