Most common mistake I see with Claude: cranking effort to max “just to be safe.”
You’re not buying quality. You’re buying tokens.
Here’s the math on why max is almost never the right call 🧵
What I actually run:
• Notes, drafts, docs, routine → medium
• Real code, multi-file refactors → high
• Genuinely hard architecture → xhigh, rarely
• max → never once
no jailbreak — works because iOS trusts user-installed CAs and authy doesn't pin. best part: Claude debugged its own dead ends from the logs, like a stale expired mitmproxy CA throwing "SSL error" on the phone.
authy quietly killed the desktop app, the export, and the Raycast extension. mobile-only now. the only "supported" way off it: re-enroll 2FA on every account by hand — a pain that trips a security review on half of them.
it stood up a mitmproxy, walked me through the proxy + cert on the iPhone, and intercepted the encrypted token DB authy pulls on login. decrypted it with my backup password → every account as standard otpauth:// URIs. moved to Ente Auth.
If your Claude Code limits started draining faster since yesterday, the official security-guidance plugin is a likely culprit.
It used to be a simple deterministic hook. Now it spins up background review agents on every turn + commit — running Opus 4.7 by default.
Looking for ways to optimize instruction execution in gpt-3.5-turbo?
Pro tip: Custom instructions, like specifying a JSON format response, perform significantly better when incorporated into a user message rather than a system message. A subtle yet powerful tweak! #OpenAIapi
Stop writing shell commands manually 🔥🔥
Use Shell AI to generate queries in terminal 🦾
Just run pip install shell-ai to start usage
Github link below ↓