Every fresh ChatGPT chat starts the same way for most people: you re-explain how you want it to behave, again. Maybe it’s “keep answers short,” maybe it’s “don’t use corporate speak,” maybe it’s a boundary around when you’re supposed to be working versus scrolling. Whatever it is, you type it in, ChatGPT nails it for that one conversation, and then the next morning you’re typing the exact same sentence into a blank chat window like it never happened. Redditor u/Asteristix, posting in r/ChatGPTPromptGenius, skipped that loop entirely and built something that sticks.
The idea is simple. Instead of prompting ChatGPT to act a certain way every single time, you save a rule to Memory once and ask it to check that rule before every reply. The rule covers three things: the condition to check, what happens when it’s met, and what happens when it’s not. A fourth optional piece decides when the rule itself is allowed to change. Think of it less like a prompt and more like a small piece of standing policy that ChatGPT consults before it opens its mouth, the same way a support rep might glance at a script before answering the phone.
Old way vs. new way
The old way: you type your preference into the chat box, ChatGPT follows it for that conversation, then a new thread wipes the slate clean. You’re back to square one every time, retyping the same three sentences you’ve already typed fifty times this month. Multiply that by every device you use ChatGPT on and every time you forget the exact wording you used last time, and the “small” habit of re-explaining yourself quietly eats a chunk of your day.
The new way: you write the rule once, ChatGPT saves it to Memory, and it evaluates that rule before every reply, including in brand-new threads. No re-explaining. The behavior just persists, whether you’re on your phone during a commute or back at your desk hours later. That’s the whole shift. Nothing fancy, no plugins, no API work. Just memory plus a condition checked on a loop.
How to build one yourself
- 🎯 Define the condition. What should ChatGPT check before it answers? Time of day, a topic you want to avoid discussing right now, a mood you stated earlier, or even a project you’re mid-way through that you don’t want interrupted by unrelated requests.
- ✅ Write the normal behavior. What happens when the condition is met. Be specific here. “Answer normally” is fine, but “answer normally and skip the disclaimers” is better if that’s actually what you want.
- Write the alternative behavior. What happens when it’s not met. This is the part people skip, and it’s the part that actually does the work. If ChatGPT has nothing to fall back on, the rule collapses the first time the condition isn’t true.
- 🔒 Set a rule-change condition. Decide when ChatGPT is allowed to weaken or remove the rule, and tell it to refuse changes outside that window. Otherwise a tired version of you at midnight can just talk the rule out of existing.
- 🚪 Add an override, optional. A specific word that lets you bypass the rule for one message without deleting it, so a genuine exception doesn’t get blocked by a rule you built for a normal Tuesday.
- Tell it safety situations always override the experiment, no exceptions. This one is non-negotiable and worth stating explicitly rather than assuming ChatGPT will infer it.
Asteristix uses this for two things right now. First, a daily usage window: ChatGPT checks the local time before replying, answers normally between 7:30am and 4pm, and outside that window it skips the actual question and just reminds you of the window instead. It won’t loosen the rule while you’re outside it either, so you can’t argue your way out at 11pm by explaining why tonight is different. The point isn’t a hard lock. It’s friction between the impulse and the click, with an override word for real exceptions, the kind of speed bump that’s enough to make you pause and ask whether you actually need ChatGPT right now or you’re just bored.
Second, since ChatGPT is already checking the time anyway, it prints a timestamp at the start of every reply. Small, but it means you can ask things like “how long has this conversation actually taken” without tracking it yourself, and you end up with a rough log of when you were actually using the tool across a week without setting up any separate tracking system for it.
Worth being honest about the limits: this is model-followed behavior, not code enforcement. It can fail, you can talk your way around it on a bad day, and it won’t carry into Temporary Chat since that mode doesn’t use Memory at all. If ChatGPT’s memory gets cleared, reset, or simply drifts the way memory sometimes does over long stretches, the rule goes with it, so it’s worth checking back in on occasionally to confirm it’s still holding. For a hard restriction, this isn’t it. For voluntary friction you actually want to be a little bypassable, it works well.
If you’ve been retyping the same instructions into ChatGPT every morning, this pattern is worth five minutes of your time. Write the rule once, save it to Memory, and let the condition check do the repeating for you instead of doing it by hand every single day.
A simple basis for building persistent ChatGPT experiments
by u/Asteristix in ChatGPTPromptGenius