Agent constantly tries to migrate me to Radix

Hey Cursor,

I don’t know if this preference is in Claude or if it’s something to do with your own multi-LLM infrastructure but it is… irritating.


EVERY TIME

I’m writing an edge-first debugger tool with a runtime component and it utilizes Shadcn with tree shaking for bundle size reduction. Every time I go to add features and use Cursor to speed the process it tries to replace Shadcn with Radix (Shadcn is Radix based so I can see how this happens).

Just curious whose end that’s on and whether future Cursor agent dev can put guardrails around things like “hey we’re going to replace your entire UI with a different design system while adding a minor feature, hope you don’t mind”

1 Like

hey, have you tried specifying in the rules or .md file in your project so the chatbot doesn’t try to reconfigure this?

The new cursorrules setup is pretty solid. I actually abandoned shadcn because it’s thin shell over Radix with some Tanstack approach was absolutely confounding the LLM. Choice was use Shadcn as a manual option or just use Radix or Headless naked. LLM was completely unable to handle what Shad is doing.