11 karma · joined May 7, 2026
I was experimenting a bit how I could block these using an ingress path. GitHub /softcane/hamza
There are other similar open issues.
However, my thoughts are that I think this fix as a native feature in Claude code is not in the best interest of Anthropic's income statement. For example, many regular users are currently not utilising the weekly quota usage and that unused capacity is shared among others who are either enterprise users or know how to precisely set up the loops.
Imagine this, if this becomes a native feature, developers would start scheduling tasks at 9 pm and would continue until they wake up.
What you think?
Yes a soft policy but it’s a smart move to encourage the rat race.
This is how it looks.
# userEmail The user's email address is <my email>. # currentDate Today's date is 2026-06-30.
IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.
</system-reminder>I also do not understand what's the point of this, because if I have a gateway that can detect it, then we can replace the text before forwarding to the model, so what's the catch?
I mean, hooks are nice, but they are messy to manage/operate for many developers at a time.
https://github.com/softcane/cc-blackbox I started investigating the proxy path, which I think would be useful for such scenarios.
Claude Code: Anytime. I'm glad we nailed it together. Happy to help. bla bla bla....
Me: Thanks! Codex, you did a great job.
Codex: Understood.
It finally clicked to me when Peter Steinberger mentioned that 50% of Codex's workforce is European.
Harness: I'm about to commit. Good use case Harness: What has changed from X to Y. Bad use case NO?