u/lethaldesperado5

Image 1 — Built a chrome extension to preview links instantly without opening new tabs
Image 2 — Built a chrome extension to preview links instantly without opening new tabs
Image 3 — Built a chrome extension to preview links instantly without opening new tabs
Image 4 — Built a chrome extension to preview links instantly without opening new tabs
Image 5 — Built a chrome extension to preview links instantly without opening new tabs

Built a chrome extension to preview links instantly without opening new tabs

I'd open 20-40 'just to check' tabs mainly for github issues and docs pages and then lose track of what I was actually working on. To fix that, I built an extension that lets you open links in a live mini browser window without leaving the current page.

There were many hurdles to bypass to get this smoothly working as it as now. Right now it's in an open beta (unpacked extension) and I'm looking for feedback from other web devs on UX and positioning. You can try it here and give me feedback if you like https://gopeekapp.github.io/gopeek/

Happy to share code snippets or talk about

u/lethaldesperado5 — 4 days ago

I built a Chrome/Edge extension to preview links instantly without opening 47 new tabs

I’d open 30-40 tabs 'just to check' them and completely lose track of what I was actually working on. So I built GoPeek, an extension that lets you preview links in a floating window without leaving the current page.

Mainly built it for workflows like:

GitHub hopping

docs/research

Reddit/Wikipedia-like rabbit holes. Basically for daily quick link inspection.

Before launch, I'd appreciate feedback.

You can try it here: https://gopeekapp.github.io/gopeek/

u/lethaldesperado5 — 7 days ago

I built a Chrome/Edge extension to preview links instantly without opening 47 new tabs

Instead of opening tons of tabs just to quickly check links, GoPeek lets you instantly preview them in floating windows/sidebars without leaving the current page.

Mainly built it for workflows like:

GitHub hopping

docs/research

Reddit/Wikipedia-like rabbit holes

Basically for daily quick link inspection

I'm looking for beta testers like you so that you can give some feedback before i launch it on web store.

would genuinely love feedback from people here.

Try it here: https://gopeekapp.github.io/gopeek/

u/lethaldesperado5 — 8 days ago
▲ 2 r/SaasDevelopers+1 crossposts

Building a 'peek browser' extension, because I got tired of tab chaos, looking for feedback

(used chatgpt to write)

I've been hacking on a browser extension, GoPeek, because I got sick of the open tab → wait → oh, this isn’t useful → close tab loop, because my work includes a lot of opening and closing tabs to check trival stuff. So i have trying to make such a tool that saves me that fatigue, and most importantly the thing I would like it to be quick, quicker than actual tab loading.

So I built a chrome extension (GoPeek, yet to launch) that lets you preview links instantly in a floating mini-browser without leaving the current page.

I’ve been polishing it for a while and I’d genuinely like feedback from people who browse heavily.

Main things it does right now:

  • Hold a modifier key + hover a link (customisable) → instant preview window

  • Opens inside a draggable mini-browser overlay

  • Auto theme adapts to the site

  • Sidebar snap mode (left/right)

  • Floating bubble minimize mode

  • Back/forward navigation inside the preview

  • Hover intent + preloading so links feel nearly instant

  • Search selected text directly in the mini-browser

  • Multiple preview windows support

  • Auto-hide header while scrolling

The weirdly hard part wasn’t the UI, it was making it feel native and smooth instead of extension-y.

Most of the work ended up being around:

  • avoiding iframe flashes

  • keeping dragging/resizing smooth

  • handling scroll performance

  • preventing sites from breaking out of embeds

  • managing preload vs memory usage

I’m attaching a short demo video because it’s easier to understand visually than through screenshots.

Would love feedback on:

features that would make it genuinely part of your workflow

UX things that feel annoying immediately

whether the hover-to-preview interaction feels natural or intrusive

Tbh, in the course of making it, I have been using it daily and seems it's become my muscle memory and can't do without it lol. Looking for feedback, thanks in advance!

u/lethaldesperado5 — 9 days ago

I was tired of tab fatigue, so I am building a mini browser you can open with shift + hover, looking for feedback

I’ve been hacking on a browser extension, GoPeek, because I got sick of the open tab → wait → oh, this isn’t useful → close tab loop, because my work includes a lot of opening and closing tabs to check trival stuff. So i have trying to make such a tool that saves me that fatigue, and most importantly the thing I would like it to be quick, quicker than actual tab loading.

So you hold shift and hover over any link and a small browser window pops up on top of the page you’re already on. You can skim an article, check a reference, or watch a video inside that little window without navigating away. You can next or prev tabs as well. I have applied the safari's ui, i hope that doesn't cause any legal problems though.

Under the hood, it’s not just a basic iframe preview. Most big sites refuse to be embedded, so I’m using declarativeNetRequest to strip X-Frame-Options and CSP headers on the fly, which lets those pages actually load inside the mini browser.

Right now it has a few things baked in: ad and tracker blocking inside the preview window so it stays fast, a draggable and pinnable panel so you can move it around and keep it open, some CSS tricks to stop sites from trying to “break out” of the frame, and options to tweak the window size, scrollbars, and a dynamic theme that matches the site you’re on. Everything runs locally in the browser; there’s no server and I’m not collecting any browsing data.

The red button is to close the tab, yellow for pinning it, and the green for opening it in actual new tab.

It’s still in the refining phase and not on the Chrome Web Store yet. I’m mostly polishing the transitions and the header behavior, like making the header auto-hide when you scroll inside the peek.

Looking for your earnest feedback, thanks in advance

u/lethaldesperado5 — 11 days ago

Stuck in the 'one more feature' loop before launch

I’m deep in the classic builder trap right now. The MVP works, it solves the main problem end to end, and there’s nothing obviously broken about it. Still, every time I get close to hitting publish, I manage to come up with one more 'must-have' tweak before anyone can see it.

In my head it sounds like this, the onboarding isn’t smooth enough, google login should really be there before I show it to strangers, the dashboard looks too empty and needs at least one or two more things before it feels real. None of these are core to whether the product is useful, but they’re great excuses to stay in the code instead of putting it in front of people.

On paper I know the rational move is to validate the core mechanic first and let users tell me what actually matters, but the fear of a weak first impression keeps pushing me back into just keep coding mode. For those of you who have actually shipped, what got you over that line?

reddit.com
u/lethaldesperado5 — 12 days ago

Which enlightened master has brought enlightenment to the most number of people?

I think as far as I have read, Gautam Buddha seems to be the one, and in modern times Osho.

What do you think?

reddit.com
u/lethaldesperado5 — 12 days ago

LangChain vs custom wrappers, when did you realize you needed to drop the framework?

When I first started messing around with LLM agents, langchain seemed like absolute magic. It felt like I could hook up memory, tools, and chains in five lines of code.

But over the last few weeks of building something slightly more complex, it’s been driving me crazy. The abstractions are so deep that when an agent gets stuck in a loop or hallucinates a tool call, debugging it feels like untangling spaghetti.

I recently ended up stripping it out and just writing direct API calls to OpenAI, anthropic and managing the message state myself in a simple python class. It’s more boilerplate, but the execution imo is 10x more predictable. At what point in your projects did you hit the framework wall?

reddit.com
u/lethaldesperado5 — 13 days ago

i switched from vs code to Neovim a few months ago and really miss the built in chat with repo side panel plus the inline apply button from the official Blackbox extension.

right now i’m just running the blackbox CLI in a tmux pane next to nvim and copy pasting edits back and forth, which gets old fast. has anyone wired up a Lua plugin, custom command, or keymaps that pipe the current buffer/selection to Blackbox and write the response back into a buffer or are CLI pipes and manual paste still the only practical workflow for terminal users?

reddit.com
u/lethaldesperado5 — 18 days ago

I know the Blackbox web app and IDE extension have the vision to code feature for uploading screenshots.

but does anyone know if the WhatsApp remote agent supports image processing? I’d love to be able to just take a photo of a UI bug on my laptop with my phone and text it to the bot, asking 'what css property is causing this overlap?'

I haven't tried sending it images yet because I'm not sure if it just drops the attachment or actually parses the pixels.

reddit.com
u/lethaldesperado5 — 18 days ago

I hit this a few times a day. I’ll use repo‑chat to debug a component, then completely rewrite that file by hand. when i ask a followup question, the agent would talk about variables and functions that no longer exist, so it’s clearly holding onto a cached snapshot of the file to save tokens.

right now the only reliable way i’ve found to fix it is to completely reload the vs code window (cmd+shift+p -> reload window) which is pretty disruptive. Is there any hidden command or slash action that forces the extension to immediately rescan the repo and drop its stale context without having to restart the editor?

reddit.com
u/lethaldesperado5 — 19 days ago

We all know that for 1m + token contexts, you rely heavily on prompt caching on the API side so you aren't paying for the same boilerplate every time you ask a question. But I realized yesterday why my Blackbox bill was creeping up. Every time I hit cmd+s, my vs code runs prettier. Prettier changes a few spaces or trailing commas. That completely changes the file hash, which invalidates the massive context cache on the LLM provider's end.

Every single time I save a file and ask a follow up question, the agent re-indexes the entire 1m tokens from scratch instead of hitting the cache. I am literally paying 2 bucks just because Prettier added a semicolon. How are you guys handling format on save when working with cached agent workspaces?

reddit.com
u/lethaldesperado5 — 20 days ago