Prerequisites

This step is a one-time thing. Skip anything you already have.

If more than half the commands are unfamiliar, take a look at the “Who this was written for” section in Beginner overview first. The learning level the manual assumes is planted there.

OS-by-OS differences

Item	macOS	Windows	Linux
Terminal you use	Terminal.app or iTerm2	Ubuntu on WSL2 recommended	the shell your distro ships
Verified state	verified	install WSL2 first, then run every command inside it	verified

On Windows, finish the WSL2 install guide first, then come back here. Every command in this manual assumes you run it inside the Ubuntu shell on WSL2.

1) Python 3

The publish script (scripts/deploy_to_blogger.py) runs on Python 3. Most macOS and Linux systems already have it.

python3 --version    # a line like Python 3.11.x means it's fine

If nothing shows or you get “command not found,” install it.

# macOS
brew install python3

# Linux and WSL2
sudo apt update && sudo apt install -y python3 python3-pip

2) git

macOS

xcode-select --install

A small dialog pops up, takes your agreement, and starts installing. If git is already installed, it just prints one notice and ends.

Linux and WSL2

sudo apt update && sudo apt install -y git

Verify and register your info once

git --version    # git version 2.x.x
git config --global user.name "Your Name"
git config --global user.email "[email protected]"

3) Claude Code

The official install guide is at docs.claude.com/en/docs/claude-code/quickstart. After installing, run claude once to log in or register an API key.

claude --version    # a version number means you're ready

You can use the OpenAI Codex CLI instead of Claude Code. In that case the entry point is the repository root AGENTS.md, and the same flow applies. If this is your first time, Claude Code is recommended.

4) A Google account and a Blogger blog

Sign in to blogger.com with a Google account and create a blog. If you’ll run a Korean blog and an English blog separately, make two. blog-studio puts the Korean version on the BLOG_ID_KO blog and the English version on the BLOG_ID_EN blog.

Once you’ve made the blog, that’s it for now. Planting the blog ID into .env is covered in first-run and publish.

5) Issue OAuth credentials

To post to Blogger automatically, you need credentials issued by Google. Two files.

• scripts/credentials.json — the OAuth client you get from the Google Cloud console (desktop app type)
• scripts/token.json — the token generated automatically once you go through the consent screen on your first publish

Getting credentials.json is the flow of creating a project in the Google Cloud console, enabling the Blogger API, and issuing an OAuth client ID of the desktop app type to download. The screen order and button locations are written up in the repository’s scripts/README.md, and since the Google console screens change often, keep the official docs alongside.

Where credentials go

credentials.json and token.json must not be planted in code or committed to git. Both are already in the base’s .gitignore and drop out of git tracking. A mistake here becomes a security incident that leaks access to your Blogger account.

There’s no need to make token.json now. It’s created automatically once you consent in the browser on your first publish.

6) Optional — a code editor

If you want to peek at how posts are saved, VS Code is fine. Since AI does the writing, it isn’t strictly necessary.

Next

Once the items are in place, go to clone-and-install.