Fellow Cursor users and Vibe Coders,
If you rely on Vibe Coding—where you continuously build the AI’s knowledge base via “.mdc” files and let it handle its own test-driven development—you might have noticed that Cursor v0.47.8 broke the ability for the agent to update “.mdc” files. That essentially halts half the Vibe Coding workflow.
Quick Fix:
- In VS Code, open Settings and search for “editorAssociations.”
- Under “Workbench: Editor Associations,” add an entry mapping *.mdc to default.
- Restart VS Code if needed, and updates to .mdc files should work again!
Why This Matters:
- Continuous Knowledge: “.mdc” files store newly learned insights, letting the AI “remember” codebase details well beyond the typical context window.
- Test-Focused Flow: The AI writes, runs, and refines its own tests; if it can’t update “.mdc,” then it can’t incorporate new information.
We published a detailed blog post with more info: Major Lessons for Vibe Coders Using Cursor v0.47.8: Major Lessons for Vibe Coders Using Cursor v0.47.8
We’ve done an in-depth dive into how “.mdc” files work and even created a dedicated “.mdc” to guide the agent through the intricate details of this file type. Incorporating it into your workflow ensures the agent can create and update “.mdc” files more accurately. Check it out here:
If it helps, please consider giving the repo a 
, and feel free to submit a pull request if you can make it better!
At https://justdo.com, we’ve fully embraced Vibe Coding. Our source-available, code-first approach complements AI-driven development. If you want to see this in action—or even become a distributor—reach out - The Project Management Platform for Vibe Coders.
Happy Vibe Coding, everyone! Let’s keep Cursor (and our “.mdc” files) flowing smoothly.