I have a rule in my .rules file(s) that tells Cursor to run the date command (which I have given permission to be run without interruption) so it always knows what day it is.
I then have documentation templates that add lines like “Modified” to my header, with the date.
Cursor is an idiot. It rarely runs the command, and even when it does, it picks a nonsensical date. Right now, it thinks it’s 2025-06.08 (June 8, a handful of weeks in the future).
This is because the Rules are subject to the Agent discretion on whether to apply them, so you can only modify the description of the rule to make the Agent usage more explicit.
Alternatively, you can be more forceful and write it directly into the system prompt, which will make the Agent unable to ignore it.
In Cursor, you have two ways to do this:
In the Cursor Settings, under the Rules tab, there is a “User Rules” section where you can input your rules.
Use the Custom Model feature and enter the rules in the input box under Advanced options.
Here are the prompt settings I configured in the Custom Model. Everything seems to be working fine in my tests.
you can give it a try.
Serious warning: For any information that requires date and time, you must use the command line date command to check the current time before you can continue with subsequent actions.