Every so often someone asks why Rest from AI isn't just a permanent filter, on by default, forever. It's a fair question — if AI posts are the problem, why not just always hide them, the same way Zenfeed always hides promoted posts? I thought about building it that way first. I didn't, and the reason is worth explaining, because it's the same reason the feature is named "rest" instead of "block."
The complaint was never that AI posts are bad
Rest from AI didn't come from thinking AI-generated posts are low quality. It came from noticing how many of them there are. On a bad day, my LinkedIn feed would be four or five AI posts in a row before a single post from someone I actually follow showed up. I wasn't offended by any one of those posts. I was missing the other posts because there was so much AI content stacked in front of them.
That's a volume problem, not a quality judgment. And a volume problem doesn't call for a verdict on every post forever — it calls for a break from the pattern long enough for the rest of the feed to become visible again. That distinction is what shaped the whole feature.
AI posts aren't the only thing competing for that space, either. When I went through what actually clutters a LinkedIn feed in 2026, AI content turned out to be one of four categories stacked on top of each other. It's just the one where a permanent filter is most tempting, and the one where a permanent filter would be least honest.
Why isn't Rest from AI a permanent block?
Rest from AI isn't permanent because it can't be certain which posts are AI-generated. Under the hood it's a keyword and phrase match against the text of a post — a heuristic, not a detector. Hiding posts forever on that basis would claim a confidence the match doesn't have, so Rest from AI hides them for a set number of minutes instead.
It's worth being specific about what that match actually is. It checks a list of AI-related words and phrases I maintain in keywords.js against the text of a post, plus the alt text on any images in it. It reads text; it doesn't look at pixels, and it isn't running any kind of model to make the call.
A heuristic that's wrong occasionally is a fine thing to build a temporary break around. It's a bad thing to build a permanent, silent removal around, because a false positive under a permanent block doesn't just annoy you once — it quietly deletes a real person's post from your feed forever, and you'd never know it happened. A timer keeps the downside of being wrong small and visible instead of permanent and invisible.
The feature isn't answering "is this AI." It's answering "have I had enough of this pattern for now" — and only one of those two questions is honest to ask a text heuristic.
How does the Rest from AI timer work?
You turn Rest from AI on from the popup and pick a duration — 15 minutes by default — and matching posts stay collapsed until that time is up. The toolbar icon swaps to a small meditating figure with a gold countdown badge showing the minutes left, ticking down once a minute, and you can end the break early from the popup whenever you want.
Matching posts don't vanish while the break is running. On LinkedIn and X they collapse into a distinct light-yellow card with an "AI" label, so it's obvious what got filtered and why. On YouTube, where the extension does less on purpose and only once you turn it on, the video is blurred in place instead, so the grid keeps its shape.
Pick how long the break lasts from the popup. 15 minutes is the default; nothing forces that number.
The toolbar badge counts down the minutes remaining, so the state of the timer is never a mystery.
Matched posts collapse into a marked "AI" card, not a blank gap — you can always see what got folded away.
When the timer runs out, matched posts come back automatically. No permanent decision gets made about any post.
What happens when the timer runs out?
When the timer runs out, the collapsed posts come back on their own, without you doing anything. No permanent decision gets recorded about any of them, because the break ending isn't a verdict on a single post — it's just the break ending.
A post you restore by hand is treated differently, on purpose. If you click a collapsed card to bring one back, it stays visible for good, because that's you overriding the heuristic on a specific post you looked at and judged for yourself. That's a decision worth keeping. The timer expiring isn't a decision at all.
The same logic shows up in the wording
It's why the feature is called "Rest from AI" and not "Block AI" or "Hide AI." A rest implies you come back to it. A block implies you've decided the thing shouldn't be there. I only trust the heuristic enough to make the first claim.
Where that leaves the design
A permanent filter would have been simpler to build and easier to describe in a screenshot. It also would have quietly asserted more confidence in a text heuristic than the heuristic deserves. The timer is the more honest shape for what Rest from AI actually is: not a judgment on any post, just a way to give the rest of your feed a chance to be visible again for a while.