Coder Legion - Recent posts tagged chromeextension

Stop copy-pasting research. Start thinking with AI

Tue, 27 Oct 2026 07:02:56 +0000

Most people waste 40% of their research time switching tabs, copying random quotes, and manually formatting prompts for ChatGPT.

That friction kills deep work.

Meet MindContext — your local-first AI research side panel for Chrome.

💡 Take persistent notes & color-code key quotes as you browse.
⚡ Transfer compiled articles + your thoughts into ChatGPT, Claude, or Gemini in 1 click.
📺 Extract full timestamped YouTube video transcripts instantly.
📁 Group multiple web sources into dedicated Research Projects for cross-source synthesis.
🔒 100% private: All data stays in your browser sandbox. No tracking, no cloud dependencies.

Try MindContext Free on Chrome Web Store:
👉 https://chromewebstore.google.com/detail/mindcontext-ai-research-n/nmagjifaanaaddbogdebppjdcoaignnd?authuser=1&hl

Copy-pasting research into ChatGPT, Claude, or Gemini is broken!

Sun, 18 Oct 2026 17:10:04 +0000

You read 10 articles, highlight sentences, copy fragments into notes, open 5 tabs, and manually assemble prompts.

It kills your focus.

So I built MindContext — the local-first AI research copilot for Chrome. 🧵👇

1/ 💡 How it works:
While reading any webpage, take instant notes & highlight key quotes directly in a sleek side panel.

With one click, MindContext compiles your clean article text + thoughts + quotes into a structured AI handoff prompt.

No formatting hassle. No lost context.

2/ 🎯 Structured AI Handoffs:
Stop getting generic AI answers.

Choose from curated prompt frameworks right inside your browser:
• Executive Summary (distinguish facts from hype)
• Critical Analysis & Counterarguments
• Action Items & Next Steps
• Multi-Source Synthesis

3/ 🚀 Take it to the next level with MindContext PRO:

For serious researchers, founders, and knowledge workers:

📺 YouTube Full Transcripts: Turn 2-hour podcast or technical talk transcripts into structured AI context in 2 seconds.
📁 Unlimited Research Projects: Group notes & quotes across dozens of tabs for comparative cross-source synthesis.
🎨 4-Color Smart Highlighter: Color-code ideas, facts, bugs, or competitors — click any quote to jump directly to its exact spot on the page!
⚡ Saved Chat Links: Automatically routes prompts straight into your ongoing ChatGPT/Claude/Gemini chats instead of spamming new conversations.

4/ 🔒 100% Privacy-First by Design:
Your notes and research NEVER touch external servers. Everything lives locally in your browser sandbox (chrome.storage.local). Zero tracking, zero cloud dependencies.

Try MindContext Free on the Chrome Web Store:
👉 chromewebstore.google.com/detail/mindcontext-ai-research-n/nmagjifaanaaddbogdebppjdcoaignnd

Unlock Pro for just $24/year (~$2/mo):
⚡ [Link to Lemon Squeezy / Store]

buildinpublic #AI #productivity #ChatGPT #Claude #ChromeExtension #PKM

From Bug Reproduction to Playwright Test — Without Starting From Scratch

Fri, 16 Oct 2026 07:59:06 +0000

Ever reproduced a bug, documented the steps, and then had to write the same steps all over again as an automated regression test?

That repetitive workflow is what inspired me to build QA Bug, a Chrome extension designed to turn browser-based bug reproductions into Playwright test drafts.

🛠️ How it works

Reproduce the bug — Interact with the website as you normally would.

Capture the steps — Record browser actions and relevant interactions.

Add assertions — Define what the test should verify.

Generate a Playwright test draft — Turn the recorded session into a .spec.ts file that you can review, edit, and adapt to your project.

The goal isn't to replace QA engineers or magically generate perfect tests. It's to reduce repetitive work between reproducing a bug and creating a starting point for regression automation.

I'm building this as a practical tool for QA engineers and developers who want to make browser testing less repetitive.

💬 I'd like your feedback

Would you use a tool that converts bug reproduction sessions into Playwright test drafts?

What would you need before trusting the generated tests in a real project?

Which part of your bug-to-regression workflow takes the most time?

I'm interested in honest feedback from people who work with manual testing, Playwright, and test automation.

🔧 I'd rather build something QA engineers actually need than add features nobody uses.

Chrome Web Store:
https://chromewebstore.google.com/detail/qa-bug-→-regression-test/khoelciicbkdeieibchdndccdncpelbg?authuser=1&hl=tr

Dock: Stops Letting Google Meet Links Open a New Window Every Time

Thu, 08 Oct 2026 09:00:51 +0000

title: Dock: Stops Letting Google Meet Links Open a New Window Every Time
published: true
date: 2026-09-25 07:46:18 UTC
tags: GoogleWorkspace,GoogleMeet,chromeextension,Productivity

canonical_url: https://blog.nandan.dev/dock-stops-letting-google-meet-links-open-a-new-window-every-time

Three Workspaces, infinite windows

I have three Google Workspaces: personal Gmail, my own Workspace, and my company's. That means three separate PWAs for Mail, three for Meet, three for Calendar, and so on down the line.

Here's the thing: every time a Meet link landed in my chat, it opened a brand new window. Not focused an existing one — opened a new one. Multiply that by three accounts and a normal day of meetings, and you end up with a wall of Meet windows and duplicate Gmail tabs you can't tell apart. It got really hard to manage.

What I built

So I built Dock. If you click a link and there's already a matching PWA open, Dock redirects you to that window instead of spawning a new one. Gmail, Meet, Calendar, Drive, Docs, Sheets, Slides, or Chat — same idea for all of them. Holding Shift bypasses it for that one click, for the times you actually want a fresh window.

Dock also helps me manage all my open tabs. Say I've got six Meet windows open across accounts — I can close any of them, for any account, from any screen. It keeps everything decluttered, the mental load is reduced. You don't need five mailboxes open just to check personal email once. One mailbox for personal, one for work, one for the side Workspace — or whatever your split looks like.

And I gave it a cute mascot: Meet Doc-k

Getting the account right

The tricky part isn't catching the link. It's knowing which account's window to send you to. Dock routes to the window for the account the link actually names — via authuser=, /u/N/, or a stored mapping — and it keeps a window's identity correct even after you switch accounts from inside the PWA itself. It reuses the already-open window for that account instead of spawning a duplicate.

The switcher

Press Ctrl/Cmd+Shift+Space and you get a fuzzy-searchable popup listing every app window, grouped by account. Live calls are surfaced first. One-click close, per window or per whole account.

A few other things it does:

Each login gets an automatically assigned, editable colour tag, shown on the toolbar icon and in the switcher.
You can add your own custom rules for apps Dock doesn't know about — Figma, Notion, whatever — with a match pattern, target behaviour, and account strategy.
Built-in Google Workspace rules can be disabled but not deleted.
Rules import/export as JSON.

No network requests

It makes no network requests — nothing it does ever leaves your device. All the routing logic runs locally against windows Chrome already knows about.

Try it

I haven't put it in the Chrome Store yet. Not sure I will. So clone the repo, build it yourself, and load it as an unpacked extension: github.com/sirius93/dock.

That's the whole idea, and so far it's worked wonders for me. If it works for you too, star the repo or leave feedback — and if enough people find it worth the hassle, I'll look at making it live.

Prismwar: a six-color card game with a built-in AI opponent that runs entirely in the browser

Fri, 11 Sep 2026 03:51:32 +0000

Hey CoderLegion!

I've been building Prismwar, an original trading card game you play against a computer opponent right in the browser. If you've played Magic, the shape will feel familiar: five colors of mana, creatures, spells, deckbuilding. Then there's a sixth color, Purple ("Undertow"), built around disruption.

It's heading for my browser arcade at play.dhseadev.online and for a Chrome extension. Both run the same game, and neither needs an account.

Features:

A 250-card set, "Refraction": 240 collectible cards plus 10 Ascendants, a new permanent type with loyalty and two abilities. Ascendants can't be pulled from packs. They unlock only through redeem codes.
Signed redeem codes: codes are signed with ECDSA P-256. The game can verify a code, but it can't create one, because the signing key never ships with it.
8 starter decks: one for each of the six colors, plus two dual-color decks (White/Red and Green/Blue). They're all commons-only, and so are the AI's decks, so the opponent can't out-rare you.
Tutorial mode for learning the rules.
Fair packs, with the odds shown in-game: slot 4 is guaranteed uncommon or better, slot 5 is rare or better, there's a pity counter for Signature cards, and duplicates are protected. You earn cards a few ways: dust for every finished match, a pack for your first win of the day, and a bonus for win streaks.
Collection and crafting: your collection is grouped by rarity, and you can craft missing cards with dust.
Procedural pixel art for all 250 cards, with no drawn assets: each color has a 5-tone palette, light always comes from the top left, and a card's keywords choose its form (beast, humanoid, flyer, serpent, colossus, wisp). My favorite bug: two unrelated cards had identical art because the effect sigils had no randomness. Now a build gate hashes the geometry of every card and fails if any two match.
Card interactions: click to flip for rules and flavor text, shift-click to enlarge, hover for a quick preview.
Generated music: three styles (ambient, chiptune, synthwave) built live with Web Audio, with intensity that follows the match. There are no audio files at all.
Game feel: particles when cards are cast and screen shake on hits. Sound, music, screen shake and motion each have their own setting, and turning motion off disables the effects.
Backup and restore for your collection.
The Ledger: export your collection progress as a generated PNG card to share, or post it to a shared wall.

Tech Stack:

Vanilla JavaScript, HTML and CSS: no framework
Canvas 2D for card art and the shareable Ledger card
Web Audio API for all sound effects and music
ECDSA P-256 signatures for redeem codes
Chrome Manifest V3 with a single storage permission
Cloudflare Pages for the arcade, and playhtml for the shared Ledger wall
Testing: a Node unit suite, a sabotage suite that must catch deliberately broken builds (15 of them), and a headless Chromium suite that runs under the production Content Security Policy, both from source and from the packaged extension

Status

In final prep, not live yet. Links will go here once it deploys:

More from me: https://dhseadev.online/

I'd love your input

AI-vs-AI testing says the aggressive starters (the White go-wide deck and the Red burn deck) are the strongest right now, and the Green ramp deck and the White/Red deck are the weakest. If you've balanced a card game before, how would you tune commons-only starter decks without flattening what makes each color different?

And if you could design a sixth color from scratch, what would it do?

I Auto-Save Every Accepted HackerRank Solution to GitHub — Here's How

Sun, 26 Jul 2026 16:55:59 +0000

I practice on HackerRank a lot. The problems are fine, but I kept losing my own work.

I'd solve something, move on, and weeks later I couldn't remember:

What trick I used
The time/space complexity of my solution
Where I even saved the code

Copy-pasting into random files didn't scale. I wanted a GitHub repo that looked like interview prep, not a junk drawer.

So I built PrepPush — a Chrome extension that watches for Accepted submissions and pushes them to your GitHub repo automatically.

The workflow I wanted

Solve a problem on HackerRank
Click Submit Code until it's Accepted
Code lands on GitHub — organized, labeled, ready to revise before interviews

No manual copy-paste. No forgetting which approach was approach1 vs approach2.

What shows up on GitHub

Each accepted solution goes here:

solutions/{language}/{difficulty}/{problem-slug}/solution-approach1.py

If you solve the same problem with a different algorithm, you get solution-approach2.py, and so on.

Re-submitting the same logic updates the same file — no duplicate spam.

Example header PrepPush adds to the file:

# Link        https://www.hackerrank.com/challenges/alternating-characters/problem?isFullScreen=true
# Problem     Alternating Characters 
# Difficulty  Easy
# Subdomain   Strings
# Language    python3
# Submitted   2026-07-25, 10:46 a.m.
# Technique   linear-scan-adjacent-comparison
# Time        O(n)
# Space       O(1)
# Insight     The algorithm counts the total number of adjacent character pairs that are identical, which corresponds to the minimum number of deletions required to eliminate all consecutive duplicates.
# Interview   Before: "I could use a stack to track characters and pop duplicates." After: "A linear scan is more efficient at O(n) time and O(1) space, as we only need to compare each character with its immediate predecessor to identify necessary deletions."
# Pitfalls    (1) Failing to handle empty strings or single-character strings, which the code explicitly guards against to return zero.  (2) Incorrectly indexing the loop by starting at zero instead of one, which would cause an index out of bounds error when accessing the previous character.

The HackerRank link is the first row so you can jump back to the problem anytime.

How PrepPush captures submissions

PrepPush runs only on hackerrank.com — including contest and prep-kit pages.

When your submission is accepted:

PrepPush captures the solution from HackerRank's submission data
It pushes to your GitHub repo (it can create the repo on first push if your token allows)
Optionally, Gemini adds technique, Big-O, trick, and hint in the header

A small toast appears on the page when capture succeeds. Open the extension from your toolbar if you want to see status or the AI analysis — push and analysis still run in the background either way.

One-time setup (~2 minutes)

You bring your own keys. PrepPush does not host your code or credentials.

1. GitHub personal access token

Create a classic token with repo scope
Generate token on GitHub
Expiration: 90 days or No expiration — your choice
Paste it in PrepPush Settings → Test GitHub

2. Gemini API key (optional)

Only needed if you want AI notes in the file header.

Free tier: Google AI Studio
Paste in PrepPush Settings → Test AI

That's it. Submit an accepted solution and check your repo.

Why I built it as an extension (not a script)

HackerRank doesn't give you a clean "export all my solutions" button for the workflow I cared about.

I needed something that:

Fires on Accepted — not on Run/Compile
Works on full-screen and prep-kit URLs
Writes to my repo structure, not a third-party server

A Chrome extension made sense: local keys, no PrepPush backend, you own the data.

What I learned shipping it

Early users helped a lot. A few real-world fixes:

SQL / DB2 problems needed correct file paths (.sql, not .py)
Prep-kit pages use different APIs than classic challenges — capture had to follow both
AI headers had to reference your actual code, not generic interview tips

It's a small project (~50 early users) but it solves a real problem for me every week.

Limitations (honest list)

Topic	Notes
Platform	HackerRank only — not LeetCode or Codeforces
Trigger	Submit Code → Accepted — Run Code doesn't count
Keys	You provide GitHub token + optional Gemini key
Privacy	Keys stay in Chrome on your device — see privacy notes

Try it

Chrome Web Store: Install PrepPush
Source / issues: github.com/tridibbanik17/PrepPush
Demo video: YouTube walkthrough

If you use HackerRank for interview prep, I'd love feedback — what breaks, what's missing, what would make this a weekly habit for you.

PrepPush is an independent project. Not affiliated with HackerRank, GitHub, or Google.

Question for you: How do you track HackerRank solutions today — GitHub, Notion, or not at all? I'd love to hear what would make this workflow stick for you.