Overgrown Chrome Extension: Clear the Vines Before You Resume a Tab
Overgrown puts growing plants over browser tabs you leave unread. Charlie Gerard introduced the Chrome extension on October 20, 2026, as a creative experiment. Returning to an abandoned page means clearing the growth with your mouse before continuing your normal work.
The appeal is easy to understand if your browser contains a collection of articles you keep meaning to read. Before trying it, understand the interruption it adds and keep Chrome’s extension controls within reach.
Overgrown’s creator explains the experiment
Understand what happens to the page
The creator describes a neglect clock that runs while a tab is out of view and pauses when you look at it. Plants spread inward as the tab stays neglected. Once coverage exceeds 5%, the page can still scroll, but clicking, selecting and dragging its content are blocked.
Dragging the mouse through the vines clears them. Reaching 5% makes the remaining growth disappear; leaving the tab again restarts the process. The popup offers a growth-duration setting and a choice of clearing tools.
That makes a useful first trial very small: choose an ordinary reading page, leave it aside, return and check whether clearing it feels enjoyable or distracting. Judge that experience before adding the extension to a busy working session.
Follow the project’s documented installation route
At this check, the repository README documents a local installation: obtain its dist folder, open chrome://extensions, enable Developer mode, choose Load unpacked and select dist/. Follow the linked repository rather than substituting a similarly named download.
Overgrown’s repository and installation instructions
Google’s own extension tutorial describes Load unpacked as loading an extension directory locally. Its project-structure guidance says manifest.json belongs at the extension root. If Chrome cannot load the folder, check that you selected the directory containing that file rather than a surrounding download folder.
For later code changes, Chrome documents an extension reload for the manifest, service worker and content scripts; content-script changes also require reloading the host page. Simply reopening a popup is not the same update step.
Chrome’s local-loading and reload instructions
Keep a simple way to pause the experiment
Chrome’s management page lets you turn an extension off and back on. You can reach it from the Extensions menu through Manage extensions. To remove an extension completely, select Remove and confirm.
Google also documents site-access choices, including selected sites or access when you select the extension. The available effect depends on the extension’s host permissions. Review the actual controls shown for your installation instead of assuming every extension behaves identically under every permission choice. A work or school administrator may restrict extensions.
Chrome’s extension controls, site access and removal
Decide what would make the trial worthwhile
Choose one outcome before installing: perhaps you want returning to a saved article to feel more playful. Then check three things during your own trial: whether the clearing gesture is comfortable, whether the delay fits the task, and whether you can pause the extension when you need uninterrupted access.
A completed trial should leave you with a clear preference. Keep it if the interaction helps your reading routine; turn it off if the extra step gets in the way. Treat the creator’s documented behavior as the starting point and your observed experience as the decision.
Check your Overgrown trial plan
