Tabglutton από mlsimon

You open thirty tabs a day out of mild interest. Some are honest duplicates — the same
thread reached from two links, the same repo opened twice. Most are things you have
already mentally finished but don't want to lose. They belong in a notes vault, not in the
tab strip. So they sit there, and by Friday there are four hundred of them.

Tabglutton does three things about that.

DEDUP

The toolbar badge counts duplicate tabs. Open the popup to see them grouped by canonical
URL, then close them all in one action.

URLs are canonicalized before comparison: lowercased host, "www." and trailing slash
stripped, tracking parameters (utm_*, fbclid, gclid, si, …) dropped, remaining parameters
sorted, and optionally the #fragment removed. So two links to the same page match even
when they don't look alike.

The tab you touched most recently is the one kept. A toast offers Undo for six seconds and
restores closed tabs to their original positions.

DEVOUR — INTO OBSIDIAN

Select the tabs worth keeping and press Devour. Each one is read through Defuddle — the
same extractor behind Obsidian's own Web Clipper — formatted as markdown with frontmatter
(title, source URL, author, site, published date), filed into your vault under Clippings/,
and closed.

The full-screen Devour cockpit is the workspace for it: tabs grouped by host, an inspector
showing exactly where each note will land, and keyboard triage throughout. j/k to move,
space to select, d to devour, x to close, / to filter.

AGENT BRIDGE (OPTIONAL)

This is the part that isn't like other tab extensions.

Tabglutton ships a local MCP server. Turn the bridge on in settings, point Claude Code or
Codex at it, and your agent can work your actual open tabs — list them, wake the ones the
browser unloaded, read them, clip the good ones into Obsidian, close the noise. "Go
through my 400 tabs, tell me what's worth keeping, and clear the rest" becomes something
you can simply ask for.

It is deliberately hard to make dangerous. The bridge is off until you enable it. It binds
to loopback only, authenticates with a token you generate that never crosses the wire, and
checks the extension's origin. Waking tabs is a second, separate opt-in. Nothing is ever
closed that Undo could not put back.

PRIVACY

No analytics, no telemetry, no remote server, no account. Page content is extracted in
your browser and goes to exactly two places, both on your own machine: your Obsidian
vault, and — only if you turn the bridge on — a local MCP server. The developer receives
nothing.

The full source is public: https://github.com/mlsimon734/tabglutton

ZEN BROWSER

Zen gives extensions no workspace API, so "active workspace" scope is a heuristic
(tab.hidden === false). If it misreads, the popup tells you and you can switch to
current-window scope in settings.