Vibe Coding is all about seamlessly integrating new knowledge into your codebase and ensuring you maintain a robust test-feedback loop. Unfortunately, Cursor v0.47.8 introduced a bug that disrupted this workflow. Here's what happened, how to fix it, and why JustDo is the perfect companion for your Vibe Coding journey.
A Growing Body of Knowledge: Vibe Coders keep a knowledge base about their codeâdespite limited context windowsâso the AI agent can "remember" and build upon crucial lessons.
Test-Driven Feedback Loop: The AI itself writes and executes tests, iterates, and eliminates errors until the code is rock-solid.
Cursor v0.47.8 failed to update its own .mdc knowledge files. This issue, though likely short-lived, was a showstopper for many. Without file updates, the agent couldn't "learn" new lessonsâobliterating half the magic of Vibe Coding.
From the Cursor Forums:
"Guys I think I've found a workaround: In VS Code Settings, search for editorAssociations, and in 'Workbench: Editor Associations', add *.mdc with the value default. This bypasses Cursor's custom editor behavior."
See the full thread here.We've created a documentation file with everything we currently know about .mdc structure and usage. Feel free to check it out: https://github.com/justdoinc/justdo/blob/master/.cursor/rules/999-mdc-format.mdc If you find it useful, please â our repo. Contribute improvements via pull requests!
Here at JustDo.com, we've fully embraced Vibe Coding. We've seen first-hand how it helps teams iterate faster and achieve more predictable code quality. If you're interested in distributing JustDo, we want to hear from you! Shoot us a message and let's push the boundaries of Vibe Coding together.