@codeforces_live_botFree
76 / 100
Score
The parts of learning to code that a messenger does well: your friends' standings during a contest, the daily problem on time, and a group that notices when you skip a week. These Telegram bots work next to Codeforces and LeetCode, not instead of them.
| # | Bot | Price | Languages | Inline | Groups | Score |
|---|---|---|---|---|---|---|
| 1 | @codeforces_live_bot | Free | EN | no | yes | 76 |
| 2 | @MyLeetCodeDailybot | Free | EN | no | no | 72 |
| 3 | @CodingQuestionsBot | Free | EN | no | yes | 70 |
| 4 | @leetcode_daily_reminder_bot | Free | EN | no | no | 67 |
| 5 | @codeforces_bot | Free | EN | no | yes | 60 |
| 6 | @StackOverflowBot | Free | EN | no | no | 56 |
| 7 | @RegexpBot | Free | EN | no | no | 54 |
We did not start these bots by hand; the assessment rests on what their owners publish. For each one we opened its t.me page to confirm a live bot, then read the repository README and source code or the author's announcement on the Codeforces blog to see what it actually does, and noted the date of the last commit, because a bot built on a platform's API breaks when that API changes. We checked whether it works in groups and whether it is an official product of the platform it names. Bots with no source from their owner beyond their own description rank lowest.
Writing code happens in an editor, and practice happens on a platform with a judge. What a messenger adds is the part people fail at: keeping going. A group tracker where everyone logs their solved problems turns a private intention into a visible record, and that alone gets more people through a month of preparation than any set of lessons.
Each kind of practice has its own bot. On Codeforces, Codeforces Live Bot (@codeforces_live_bot) shows a live scoreboard of just your friends during a round, with predicted rating changes, and tells you when your solution passes or fails system tests; you add friends by handle or import them with an API key. For LeetCode's daily problem, Leetcode daily question reminder (@MyLeetCodeDailybot) sends the full statement at an hour you pick and keeps hints, difficulty and topics behind buttons, while LeetCode Daily Reminder (@leetcode_daily_reminder_bot) keeps nudging twice a day until you send /done. Both set hours in UTC, and neither sees your LeetCode account. For interview prep with friends, Coding Questions Tracker (@CodingQuestionsBot) counts each member's solved problems against a weekly target of seven and pairs people for mock interviews, though it has no automatic reminders yet.
This category is full of bots named after a platform they have nothing to do with. We found no official Telegram bot from LeetCode, HackerRank, Codewars, freeCodeCamp, Sololearn, Codecademy or Hyperskill, and the Codeforces, LeetCode and Stack Overflow bots on this list were all built by users, not by the platforms. That is not automatically bad - a fan project over public data can be useful - but it changes what you should expect: no support, no guarantee, and a service that can stop when its author loses interest. Nothing has been published about the bot simply called Codeforces (@codeforces_bot) since 2015. Prefer a bot with a public repository or a clear author, and keep the platform itself as the source of truth for anything that matters, like when a contest starts.
Not on its own. Use a course or a problem platform for the learning, and a bot for the daily problem, contest reminders and keeping your study group accountable.
Yes, two unofficial ones. Leetcode daily question reminder (@MyLeetCodeDailybot) sends the full statement at an hour you pick, with hints behind buttons, and LeetCode Daily Reminder (@leetcode_daily_reminder_bot) reminds you twice a day until you mark the day done. Both use UTC hours, and neither connects to your LeetCode account.
Not the ones on this list. The Codeforces and LeetCode bots are built by users of those platforms, and the Stack Overflow bot credits an individual developer; check for a public repository or an author's contact, and never rely on such a bot for a contest start time without confirming on the site.
