One person builds this
Gemini Notebook Toolkit is made by Vinayak, a solo developer working from Jaipur, India. Not a team, not a studio, not a brand with a support queue — one person who reads every message that arrives.
Разработчик: Vinayak · Расширение 1.5.0
Who builds it
My name is Vinayak. I write the extension, the web app, the database migrations, the marketing pages, and the reply you get when you email support. There is nobody else.
I work from Jaipur, in India. That is roughly UTC+5:30, which usually means a reply arrives while North America is asleep and lands in your inbox by morning.
Saying this plainly matters more in this category than in most. Browser extensions ask for real access to your browser, and a lot of them are published by an anonymous account with a free email address. You should know who is on the other end of the software you install.
Why it exists
I was doing research the slow way: reading a paper, a thread, and three long AI conversations, then copying each one into a document, cleaning it up, and pasting it into NotebookLM one source at a time.
The reading was the work. The copy-pasting was not, and it was taking longer than the reading. So I built the thing that removed it — a save button on the pages I was already reading, a library to keep what I saved, and a way to push a batch of sources into a notebook without touching the clipboard.
Everything since has been the same instinct applied to whatever step still felt like clerical work: importing a screenful of open tabs, saving an AI chat as a source, exporting a whole workspace to Markdown or LaTeX in one action.
What a one-person company means for you
Being small is not automatically a virtue. Here is the honest version of both sides.
Fixes can ship in 48 hours
There is no sprint to wait for and no approval chain. When Google changes something and capture breaks, I can have a fix built, tested, and submitted the same day. That is the commitment stated on the status page.
There is no support tier
There is no first line to get past, because there is no second line. Whatever you send goes to the person who wrote the code that annoyed you, and it gets answered by that person.
What you ask for is the roadmap
With this few users, one thoughtful email genuinely changes what gets built next. Several features shipped because a single person described a workflow I had not thought of.
And the real trade-off
One person gets ill, sleeps, and occasionally takes a day off. A reply can take longer than you would like. Your data is exportable to Markdown, LaTeX, JSON, and plain text at any moment precisely so that depending on me never becomes a trap.
Things this page is not claiming
Plenty of small products pad this page. So, for the record:
- There is no team, no office, and no investors.
- There are no awards, no press coverage, and no customer logos.
- There are no user or revenue numbers here, because none of them would be impressive.
- Nothing on this page is a stock photo of a founder who does not exist.
How to reach me
Email is the whole support system, and it reaches one inbox. Bug report, feature request, refund, or a question about what the extension can see — all of it goes to the same place.
support@notebooktoolkit.com