u/Myth_Thrazz

TL;DR

• Claude Code shipped AFK mode (away from keyboard) in v2.1.198, built July 1, 2026. It is not in the changelog and there is no release note.
• An unanswered AskUserQuestion dialog now auto-answers after 60 seconds (with a 20-second on-screen countdown) and tells the model to proceed on its best judgment.
• Two undocumented env vars control it: CLAUDE_AFK_TIMEOUT_MS and CLAUDE_AFK_COUNTDOWN_MS. Set the timeout to 2147483647 and it effectively never fires.
• I found all of this by running strings over the local binary and bisecting four versions. Every command in this post is reproducible on your own machine.
• The upside: unattended and remote sessions stop hanging forever. The catch: an away user hasn't agreed to anything, so the model can now proceed on a guess and act on it.

• WordPress debug.log has no size cap, rotation, or dedup — it just grows forever
• One noisy plugin repeating the same error every request = a multi-GB file
• It fills the disk and can take the whole site down, silently
• Once it's huge you can't even open it to diagnose (editor OOMs, "cat" kills a small VPS)
• Usual fixes both lose: delete it (lose all history) or paste into AI (won't fit context)
• Built a module that streams the log (no RAM blowup), groups duplicates into a counted table, and size-guards it without losing the errors you need
• It's disk-safety + log hygiene, not a speed boost

I'm supporting many client sites - both retainers and one-off optimizations. More often than not, while looking for the sources of the slowness I end up finding an enabled debug.log that takes 5G+ and is full of notices and deprecation messages.

So on one side it's good as this is the mine of useful information about website.

On the other side - sifting through the 5G of crap takes ages.

Do you have any good solutions to deal with that?

From 19 June 2026, every shop selling to EU consumers has to put a clearly labelled, one-click "withdraw from contract" function in the storefront. That's Directive (EU) 2023/2673, which adds a new Article 11a to the old Consumer Rights Directive.

WooCommerce has no native support for it - there's just an open request (#65443) sitting there with no roadmap.

I've tested 11 plugins that do that and selected the best one ( in my opinion )

TL;DR; It's WAY more about QUALITY than it is about QUANTITY.

A major release of the WP Multitool (1.3.0) that massively improves the Image Optimizer module - adding the advanced detection of the unused images and thumbnails and allowing to remove them.

WordPress still registers blocks even if you're not using them, and not only basic WP, WooCommerce too. And even if it doesn't take MUCH time - it still takes some time on every request.

So I've made a free plugin that just... removes them https://wordpress.org/plugins/zero-blocks-given/

In the X I'm in the 'bubble' with other tech/builders and we all hate doing marketing - I came with an idea that would pair builders with marketers in Tinder-like style.

What do you think? Are there any marketers here that would be interested in something like this?

Post mortem cautionary tale about how I built Auto Updater for my plugin on top of Polar licensing system, and what went bad with that.

ps. Marking as [PREMIUM] as it's about a paid plugin, but the post is educational.

The plugin is called WP Multitool - its a modular WordPress optimization plugin with 14 independent modules for performance and control - aimed for WordPress power users (agencies, devs)

I've tried:
- SEO
- Reddit
- LinkedIn
- X
- Cold email ( crawling the internet to get the list of agencies turned out to be harder than I thought)

Plugin is very good - people are buying it for $199/year and $499 lifetime and I haven't heard anyone yet who wouldn't like it.

It saves a lot of time when debugging server-side performance issues.

It is NOT another CACHING plugin.

--

TL;DR: - I'm an engineer, not marketer - I know I have a good product, but I don't know how to reach customers

Over weekend I got an idea of a potential very fast WordPress + WooCommerce stack. Yesterday I've started to work on it and today I've finished. The results blew my mind.

WooCommerce can become really, really fast... <5ms loading time (locally)