Major Lessons for Vibe Coders Using Cursor v0.47.8

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 and how to fix it.

The Vibe Coding Principles

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.

The Breaking Bug in Cursor v0.47.8

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.

The Workaround You Need

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.

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.