{"slug": "bugdr", "title": "BugDr", "summary": "BugDr launched a free tier and a paid €0/month entry plan for its browser-based debugging practice platform, which gives developers failing codebases to diagnose with an in-browser editor, terminal and Claude Haiku AI assistant, capped at 150,000 tokens per day. The platform scores sessions on prompts, token usage and test runs against a comparison group, and plans to add more cases at launch on October 21. BugDr states that \"Get a job\" is a stage label, not an employment guarantee, and that fewer tokens alone do not mean a better fix.", "body_md": "### Free\n\n€0/month\n\n- All difficulty levels.\n- 150,000 tokens / day.\n- AI assistant: Claude Haiku.\n- Efficiency scoring.\n- Public leaderboard.\n\n[Start now](https://app.bugdr.app)\n\nAI can write your code. challenges you to understand it, find what broke, and prove your fix works.\n\nThe belief\n\nSomething broke. A customer is waiting. Your first fix looks convincing.\n\nDoes it actually work?\n\ngives you practice codebases built around failures you could face at work. Read the report. Follow the evidence. Use AI. Test your changes.\n\nYou own the fix.\n\nWhy\n\nCoding puzzles ask you to solve a defined problem. asks you to investigate what went wrong in an existing codebase.\n\n| Aspect | Coding puzzle |  | \n|---|---|---|\n| The task | Solve a standalone problem. | Investigate a failure in existing code. | \n| AI | Rules depend on the assessment. | Available in the workspace. | \n| The work | Build a solution from the prompt. | Read, diagnose, change, and test. | \n| The checks | Does the solution produce the expected output? | Is the failure fixed without breaking the rest? | \n| What you show | Your solution. | Your fix and the investigation behind it. | \n\nHow it works\n\nStart with the bug report and explore the codebase. Learn what should happen and what happens instead. The cause is yours to find.\n\nThe timer starts when you start the case.\n\nThe editor, terminal, and AI assistant run in your browser.\n\nTrace the failure. Ask questions. Try a focused change. Run the code.\n\nYour prompts, token usage, and test runs are recorded during the session.\n\nRun the acceptance checks. Solve the reported problem and keep the rest working.\n\nYour first successful result is saved. Replaying the case won't replace it with a higher score.\n\nExample case\n\nA retry isn't a fix if it charges someone twice.\n\nIllustrative case and acceptance checks.\n\nSession feedback\n\nAfter a solve, your session debrief looks at your prompts, tokens, and test runs. Compare your approach with other participants on that case and find something useful to try next time.\n\nA working fix matters. So does learning a process you can repeat.\n\nExample debrief\n\n| Measure | You | Comparison group | \n|---|---|---|\n| Prompts | 12 | 4 | \n| Tokens | 3,840 | 1,200 | \n| First-run pass | No | 68% | \n\nEight test runs before the first pass. Next time, inspect the logs before asking AI for another change.\n\nOn your next case\n\nRead the full stack trace. Identify the likely failure point. Ask for one targeted change. Test the hypothesis.\n\nIllustrative feedback and benchmark data. Fewer tokens alone do not mean a better fix.\n\nCareer paths\n\nChoose a target role and follow a structured path through relevant cases. Start with focused bugs, then take on failures that require a deeper investigation.\n\n“Get a job” is a stage label, not an employment guarantee.\n\nStage 01\n\nSmall bugs. Better instincts.\n\nTrace the failure. Make a focused change. Check the result. Pass the acceptance checks and meet the path's efficiency benchmark to move forward.\n\nIllustrative cases\n\nRoles\n\nThe connection pool runs out under load. Find out why.\n\nThe page keeps rendering. The browser keeps slowing down.\n\nTwo users. One slot. Somehow both booked it.\n\nThe dashboard is slow. The queries tell the story.\n\nThe summarizer sends more context than the model can handle.\n\nThe service keeps running out of memory. Restarting it isn't the investigation.\n\nProblem library\n\nDuplicate charges. Slow queries. Failed deployments.\n\nBrowse by role, topic, and difficulty. Every case gives you a brief and acceptance checks, so you know what the fix needs to achieve.\n\nMore cases coming at launch, October 21.\n\nContests and dashboard\n\nDaily, weekly, and monthly contests put participants on the same case. Bring your own approach and see how it compares.\n\nYour dashboard keeps your next case and progress in view.\n\nHackathons\n\nOn special occasions, runs hackathons: every participant gets the same case at the same time. Your fix, your approach, your efficiency — measured against everyone else's.\n\nPrizes for the top solvers.\n\nProgression\n\nProgress through 's practice ranks as you complete cases.\n\nA rank reflects your progress on the platform. It does not certify your job level or overall engineering ability.\n\nFind your footing in unfamiliar code.\n\nBuild a reliable investigation habit.\n\nWork through more demanding failures.\n\nPractice cases with deeper interactions.\n\nLook beyond the symptom to the system.\n\nTake on the platform's toughest cases.\n\nOne verified fix at a time.\n\nPricing\n\n€29.99/month\n\nor €239/year\n\n~€19.92/month when billed annually. Save 33%.\n\n€199/month\n\nEvery Claude model, one daily budget.\n\n€12.99/month\n\nFor engineers who run their own AI stack.\n\nTokens measure how much of the codebase the AI reads. Better engineers use fewer.\n\nPayments open after launch.\n\nWaitlist\n\nopens October 21, 2026.\n\nLeave your email for a reminder the night before and a link when it's live.\n\nFAQ\n\nYes. Use the workspace assistant to explore code, ask questions, and work on a fix. You still need to understand the changes and check that they work. Use AI. Own the code.\n\nThey're practice codebases built around failures you could encounter at work. You get incident context and room to investigate without touching a live customer system.\n\nThe listed library stacks include Node.js, TypeScript, Python, Go, React, Next.js, PostgreSQL, Redis, JWT, and WebSockets. Check the individual case before starting.\n\nNo. The editor, terminal, AI assistant, and tests run in your browser.\n\nA working, reliable fix matters most. Scoring also considers code quality, testing, time, and AI usage. Fewer tokens or fewer lines do not automatically mean better engineering.\n\nYour first successful result is final. Take the lesson into your next case.\n\nCareer paths, AI feedback after each solve, a higher daily token limit, and the listed Pro model options. €29.99 monthly or €239 yearly.\n\nA path gives you relevant practice and benchmarks. It cannot promise employment. Hiring decisions belong to employers.", "url": "https://wpnews.pro/news/bugdr", "canonical_source": "https://www.bugdr.app/", "published_at": "2026-11-01 17:01:43+00:00", "updated_at": "2026-11-01 17:20:09.295429+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-products", "artificial-intelligence"], "entities": ["BugDr", "Claude Haiku", "Anthropic"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/bugdr", "markdown": "https://wpnews.pro/news/bugdr.md", "text": "https://wpnews.pro/news/bugdr.txt", "jsonld": "https://wpnews.pro/news/bugdr.jsonld"}}