Language issues in replies

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The replies to my prompts are mixed language and I absolutely loathe it, especially when it sneaks into files I use for documentation. I want it to speak “norsk bokmål” (official Norwegian) to me, and it mixes in danish, new norwegian, and swedish even (I suspect). I’ve also seen it not respect the Norwegian vowels (æ, ø, å).

I have made a rule for it and it still ignores this, claiming it will not do it anymore, yet does it in the very next reply. Sigh. “Serentity, now!”

ea6d12d6-8248-4528-99a1-2a2acbb8259c

Steps to Reproduce

I don’t know, just talk to it as long as I have in Norwegian?

Expected Behavior

To reply in the proper language spesified.

Operating System

Windows 10/11

Version Information

Version: 3.2.16 (system setup)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 2

For AI issues: add Request ID with privacy disabled

ea6d12d6-8248-4528-99a1-2a2acbb8259c

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This looks mostly like model behavior, but let’s also confirm the rule is actually being applied.

Closely related Scandinavian languages. Bokmål, Nynorsk, Danish, and Swedish often get mixed together. Training data for these languages is heavily blended, so LLMs tend to mix vocabulary and grammar from neighboring languages, especially in longer contexts. Dropping æ, ø, å is the same kind of generation artifact. This isn’t specific to Cursor or Composer 2. Even specialized language ID classifiers often confuse the Scandinavian languages.

Is the rule reaching the model. In 3.2.16 you’re already on a version where the fix for alwaysApply: true rules should be included, but it’s still worth verifying. Simple test: in a fresh chat, ask repeat the content of my language rule. If the model can’t reproduce the text, the rule isn’t reaching it. Then it’s worth checking the structure. This matches reports like `alwaysApply: true` rules are being completely ignored now and AGENTS.md not automatically injected.

What you can try right now:

  • Make the rule as strict as possible: Reply only in Norwegian Bokmål. Never use Danish, Nynorsk, or Swedish vocabulary or grammar. Always preserve æ, ø, å. The stricter it is, the more stable the model tends to follow it.
  • Duplicate the language instruction in AGENTS.md at the project root as an extra channel.
  • For critical docs, add a one-line language instruction directly in the prompt (in Norwegian or English) so it’s in the fresh context, not only in the system section.
  • If you run long sessions, language drift gets worse as context grows. It can help to start a new chat periodically.

If the issue still happens after tightening the rule and adding AGENTS.md, share a short example input plus output and we can dig deeper.