GuideGen

Install GuideGen

Early access · while the Chrome Web Store review is in progress

This is a manual install, and it's temporary. GuideGen is in review with the Chrome Web Store. Until it's approved, Chrome won't install it for you — you load the folder yourself. It takes about two minutes, and everything in the product works exactly as it will from the store.

Download the extension

A ZIP file, about 3 MB. The offline voice for narrated video is a separate 78 MB download, and it only happens the first time you actually export one — once, on that machine, with a progress bar.

Download ZIP

Six steps

  1. Unzip it. You'll get a folder called guidegen. Put it somewhere you won't delete by accident — Chrome loads the extension from that folder every time it starts, so if the folder moves or goes away, the extension stops working.
  2. Open chrome://extensions. Type it in the address bar — links to chrome:// pages don't work, which is why this one isn't a link.
  3. Turn on “Developer mode.” Top-right of that page.
  4. Click “Load unpacked” (top-left, appears once developer mode is on) and pick the guidegen folder — the folder itself, not a file inside it.
  5. Pin it. Click the puzzle-piece icon in the toolbar, then the pin next to GuideGen. You'll be clicking it a lot.
  6. Sign in and record. Click the icon, create an account, press Start recording, do your workflow, press Stop. The editor opens on this site with your guide in it — Export → Copy for AI puts it on your clipboard as text, or pick a document format.

Two things that will look like bugs, and aren't

Chrome will warn you about developer mode

Every time you restart Chrome you'll get “Disable developer mode extensions”. That warning is about the install method, not about GuideGen — Chrome shows it for anything loaded from a folder, because normally only developers do that. Dismiss it. It goes away for good once you install from the store.

Reload any tab you had open already

A tab that was open before you installed the extension hasn't loaded the recorder yet. Reload it once and recording will work. New tabs are fine.

Two things worth trying first

Capture the last 2 minutes

The one that has to be switched on before it can help you, which is the awkward part of it: open GuideGen on a site you actually document and turn on catch-up capture. From then on, on that site, GuideGen quietly holds what you do — a small dot in the corner is the only sign. Work normally for a few minutes, then open GuideGen again and press Capture last 2 minutes. You get a guide of work you never pressed record for.

It is per site and off everywhere else, it holds nothing for longer than 7 days, it never runs in an incognito window, and none of it is uploaded. Pending captures are listed in your dashboard with how long each has left.

The API log

Every step now also records the requests the page made and what came back. Steps where everything worked show a single quiet line; a step where something failed shows the failure. The full log is behind API log in the editor's toolbar.

Go and reproduce a bug for this one — that is where it earns its place. The handoff you copy will say clicking Save sent POST /api/orders and got a 500, which is a very different message to send an engineer than "it didn't work". Only the AI handoff includes it; documents, slides and video never do.

Tick Include full API requests & responses next to Start recording and every request carries a curl you can copy, with what came back — successes included. It's off by default, so tick it before the recording you want it in. Do be deliberate: a successful response is often real data, and it's the one thing GuideGen keeps that you can't look at first.

Credential header values are masked before anything is stored, along with query-string values and obvious secrets in a submitted body, so nothing captures your tokens. That does mean the cURL documents the call rather than replaying it — paste your own token in to re-run it.

Important, if you plan to keep the guides you make now.

Removing this version and installing the store one gives you a fresh, empty storage — Chrome clears an extension's data when you remove it. So the guides you recorded in this version won't be there afterwards. Nothing is broken; there is just no way to carry local guides across an uninstall.

If a guide matters, publish it before you switch. Published guides live in your account, so they show up on any browser you sign in to — including the store version.

When the store version lands

  1. Publish anything you want to keep.
  2. Install from the Chrome Web Store link I'll email you.
  3. Remove this one at chrome://extensions, and turn developer mode back off.

If something doesn't work

The dashboard says it can't find the extension

Record a short guide and press Stop. That opens this site with the extension's identity attached, and it's remembered from then on. Visiting the dashboard directly before you've ever recorded is the one case where it can't find it yet.

“Start recording” isn't there

You're not signed in. The extension asks for an account before it records — that's what lets you publish a guide and get a link for it. Signing in doesn't upload anything.

Nothing happens when I click

Check the page isn't a chrome:// page, the Web Store, or a PDF viewer. Chrome blocks extensions on those, and there's nothing GuideGen can do about it.

Still stuck

Email heygauravsingh@gmail.com and say what you saw. Screenshot helps.

GuideGen is free during early access. Everything runs on your own machine except signing in, and the single guide you press Publish on — the privacy policy is specific about which is which. Pasting a handoff into an assistant is your own send, to whoever you chose; nothing leaves here to make it happen.