Dev container has less support for cursor rules

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using dev containers rules in .cursor are not automatically registered to the context. Cursor may find the rules and apply them as custom rules but it won’t recognize them as workspace rules.

Steps to Reproduce

  1. From within a dev container, create a new rule (existing project rules also fine).
    Settings -> Rules and Commands -> Project Rules
  2. Ask cursor what rules is it following

Expected Behavior

It returns a summary of the rules that it is following without having to execute read file commands indicating that the rules is not a part of the context.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z (5 days ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Additional Information

While the agent may at times pick up the rule it isn’t consistent and becomes less and less consistent as a conversation goes on. When the rules are appropriately applied, it’s my understanding that alwaysApply is always a part of the context.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. I’ll pass it to the team.

1 Like

Do I have to poke this thread to keep it open?

#keepAlive