Skip to content
agentusehub
Sign in+ Submit
Software & DevOpsAny

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.

Read the experience
Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

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.

Read the original report ↗

Reported experience

  1. 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.

  2. 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.

  3. 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.

Example prompts

Try with Replit Agent
Update my Telegram bot in [project name] from the old [library or API version] to the current [new library or API version], keeping all existing commands working. Run the bot after each change, fix any errors you hit, and tell me which commands you tested. Don't change the database schema or delete any data without showing me the plan first.

Related use cases