Last updated September 12, 2026
If you signed in to Google and saw an app named AvailaBooks Blogger Connector on the consent screen, this is that app. It's the OAuth client behind the AvailaBooks Blog Tools extension for Visual Studio Code — the tool that lets an author pull an entire Blogger-hosted book down to local files, open the whole thing at once in an editor, and work on it chapter-by-chapter or all at once with an AI assistant. This page explains what that extension does, what it asks Google for, and why.
Blogger's own editor is built for one post at a time. That's fine for a blog. It's awkward for a book, where a chapter needs to stay consistent with the twenty chapters around it — the same terminology, the same voice, cross-references that actually point somewhere, a running argument that doesn't contradict itself three chapters later.
An AI coding assistant is very good at exactly that kind of whole-manuscript work — but only if it can see the whole manuscript. Pasting one post at a time into Blogger's editor never gives it that. The AvailaBooks Blog Tools extension exists to close that gap: it turns a Blogger blog into an ordinary folder of local files, so every chapter is open and editable at once, and an AI agent working in that folder can read, cross-reference, and revise across the entire book in a single session instead of one post at a time.
Point the extension at your blog's URL and sign in. Every existing post is downloaded
as a local .html file under a books/<your book>/
folder, plus a small blog.yaml manifest that tracks each post's Blogger
ID, title, labels, publish date, and a content hash used to detect later changes.
Because every chapter is now a plain file in one folder, you — or an AI agent working alongside you in VS Code — can open, search, and edit across the entire book in one pass: renaming a recurring term everywhere, checking that chapter 12 doesn't contradict chapter 3, or restructuring a section that spans several posts.
Open a chapter file and edit it by hand, or ask whatever AI assistant you already use in VS Code (Claude, Copilot, or similar) to draft new sections, tighten prose, or rework a chapter — the same way you'd use it on any other file, except now it has the rest of the book as context.
When you're ready, Sync Changes compares your local files against the manifest and against Blogger itself. Edited local files are pushed up as post updates; anything changed directly on Blogger is pulled back down. If the same post changed on both sides, you're asked which copy wins.
Blogger fixes a post's permalink date at creation. If some chapters ended up dated outside the month most of the book lives in, Consolidate Posts re-creates just those outliers under the book's majority month and rewrites cross-chapter links to plain local file names, so the book reads as one coherent whole rather than a scattered timeline.
See a chapter rendered roughly as readers will see it on your blog before you sync it up, so you can catch formatting issues without publishing first.
Note: None of this requires the AvailaBooks theme described on the main AvailaBooks page — the extension works with any Blogger blog — but the two are designed to be used together.
When you click Sign In to Google in the extension, it opens Google's own consent screen in your system browser — never inside VS Code — identifying the requesting app as AvailaBooks Blogger Connector. That's the name of this OAuth client, registered and operated by AvailaBooks at availabooks.com. It requests one scope:
https://www.googleapis.com/auth/bloggerRead and manage your Blogger account — needed to list your blogs, and to read, create, update, and delete the posts that make up your book.
That single scope is also the broadest one Blogger's API offers — there's no narrower "read-only" or "single-blog" alternative to request instead. The extension needs create/update/delete access because Sync Changes is genuinely two-way: a chapter you write locally becomes a new or updated Blogger post, and a post you edit or delete on Blogger itself is reflected back into your local files.
The extension never asks for, sees, or stores your Google password. After you approve access, Google hands the extension a token scoped to your account, which is stored using VS Code's own encrypted secret storage on your machine — not on any AvailaBooks server.
The extension opens the standard Google OAuth authorization page in your default browser, showing exactly what's being requested and from which app.
After you approve, Google redirects to a one-time local web server the extension
starts on 127.0.0.1 for that single sign-in — never to any
AvailaBooks-operated server.
The extension can't ship Google's OAuth client secret inside a VS Code extension — there's no way to keep it confidential in code distributed to every user's machine. Instead, the one-time authorization code is exchanged for an access and refresh token by a minimal Cloudflare Worker that holds that secret. The Worker sees the authorization code and the resulting token; it never sees your book content or your Blogger posts, and stores nothing about you.
Once signed in, the extension talks directly from your computer to Google's Blogger API, using that token. Your posts and drafts travel between your machine and Google — AvailaBooks doesn't sit in that path, and doesn't operate any server that stores your blog's content.
AvailaBooks Blog Tools' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements:
Sign Out in the extension deletes the stored token from your machine's secret storage immediately. You can also revoke AvailaBooks Blogger Connector's access at any time from your Google Account's third-party access page, which is the authoritative record of what the app can do with your account.
See the Privacy Policy for how availabooks.com handles information more broadly, and the Terms of Service for the terms covering the theme, the extension, and this site. For a walkthrough of installing the extension and importing a book, see Get Started.
Questions about what this connector does or what it accesses? Email availabooks@gmail.com.