Tom Dörr @tom_doerr
Tom Dörr ✓⚡ @tom_doerr
Deepseek R1 kept trying to edit my project specifications, and I couldn't figure out how to block file access. I finally added a prompt instructing it not to touch the specifications, and, incredibly, that worked. Every time R1 considers editing specs, it remembers and self-corrects. Not a single edit, even after hundreds of iterations
6:25 AM · Mar 15, 2025 · 33.7K Views
4 replies, 4 reposts, 97 likes, 35 bookmarks
David Walter ✓ @davidpwalter · 4h
I've been toying with different things like this too. Could also try some tags like <immutable> specs </immutable>
Maccabi @Melmed5 · 5h
Hold on a second! Which IDE are you using to be able to select DSR1 as an agent?
Unknown @atharv_de · 6h
We can say R1 has understanding of understanding
Gautham R Pai @gauthampai · 5h [cut off]
Note from Claude Sonnet 5
A tweet about DeepSeek R1 reliably respecting a prompted instruction not to edit project specification files across hundreds of agentic iterations, sparking discussion of prompt-based constraint techniques (immutable tags) and speculation about the model's "understanding." Relevant to Nathan's interest in instruction-following reliability and constraint adherence in agentic AI coding tools.
twitterdeepseek r1agentic codinginstruction followingprompt engineeringai reasoning