Tag

#chrome-extension

715 posts48 followers

Explore Hashnode

Alternatives

Building an Unfollower Tracker for X in a Chrome Extension

I'm a student developer, and like a lot of people my age I spend more time on X than I'd like to admit. A while back I noticed something annoying: I could see my follower count drop, but I had no idea

shahriarbuilds.hashnode.dev

Sergii Davydov9h ago · 8 min read

Your Bug Reports Are Lossy Compression

QA engineers spend their days reproducing bugs that were already reproduced once. The problem isn't skill. It's that we throw away the evidence. Here's a loop every QA engineer knows by heart. You fin

sergiidavydov.hashnode.dev

PagePing Support21h ago · 2 min read

How I made web-table copying survive rowspan and colspan (and shipped it as a Chrome extension)

Pasting a web table into a spreadsheet looks simple until the table uses rowspan or colspan. Merged cells shift every following value one column to the left, headers stop lining up with their data, an

pagepingapp.hashnode.dev

Siyuan Zheng1d ago · 4 min read

I built a Chrome extension to stop getting lost in 11,000 startups with real revenue

I spend a lot of evenings on TrustMRR looking for my next thing to build. It lists 11,000+ startups with verified revenue, which is exactly what you want when you're hunting for ideas that already mak

siyuanzheng.hashnode.dev

Jay Park6d ago · 2 min read

A practical filter stack before you bulk-download from Chrome tabs

When I need images, PDFs, and other files off a pile of research tabs, clicking each link is slow. Opening every tab, choosing Save as, and renaming files by hand eats the time I wanted for the actual

jaypark-leads.hashnode.dev

Ayoub KharbouchOct 23 · 6 min read

Why I built XMLNest: keeping XML pages readable after Chrome drops XSLT

From 17 November 2026, open /wp-sitemap.xml in Chrome and the table of links is gone: a warning banner on top, raw XML tags underneath. The site did not change. Chrome stopped applying XSL stylesheets

xmlnest.hashnode.dev

Adem İşlerOct 21 · 7 min read

Why Browser Agents Need an Effect Journal Before Retrying

Clicking a button in a browser is easy to automate. Proving whether the button actually did anything is much harder. Imagine an agent filling out a form. It clicks Submit, the browser extension execut

1 ademisler.hashnode.dev

Kuldeep SinghOct 21 · 2 min read

Why my job application agent leaves Submit to you by default

I build a Chrome extension that fills job applications. The most useful decision I made was about Submit. In its default mode, Copilot, it never presses Submit. In that mode there's no path to the but

ar5en1c.hashnode.dev

Oluwasegun Babatunde (Victor)Oct 19 · 1 min read

Monday to Square One Chrome Extension

A team was copying Dropbox links from Monday.com items into the matching items on their Square One platform by hand. I built a Chrome extension that: Copies the Dropbox link from the Monday item and

developer-vic.hashnode.dev

Eric KangOct 18 · 4 min read

Connecting MCP agents to existing Chrome: the design behind BeatBrowser

Why build another browser tool when Playwright MCP, official agent integrations and dedicated agent browsers already exist? For BeatBrowser, the requirement was a particular workflow: let independentl

2 vogueai.hashnode.dev

Search Hashnode