All ideasMore in Work
Work

Naver blocks the AI’s browser, so the AI writes and a local script publishes

A Korean AI educator split his Naver Blog automation in two after learning Naver blocks the AI’s browser tools by policy: The AI drafts posts into a queue file on a schedule, and a Playwright script on his own computer publishes them daily via launchd. Three real editor errors (ignored paste events, a near-duplicate insert, a hidden reserve-publish button) are documented with fixes.

How it works

  1. The AI drafts a post into a pending queue file on a 09:00 schedule
  2. Playwright script wakes at 10:00 via launchd
  3. Script pastes HTML through the system clipboard into the Naver editor
  4. Block-count check prevents duplicate inserts
  5. Visible-button filter avoids the hidden reserve-publish button
  6. Post publishes and is logged

Why it’s worth knowing

The fix for a platform that blocks AI browsers was to fire the AI from publishing: The AI only writes files, and a plain local script presses publish.

Where it’s from

Summarized from a public post on agentickorea.net. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

WorkThe AI audited my eBay store, found 28 listings going nowhere, and sold a bundle for meWorkA contractor talks measurements into his phone and QuickBooks sends the estimate in 45 secondsWorkFive years of books rebuilt from 34,000 transactions across 27 statement formatsWorkWhatsApp agent qualified leads, sales reached 461 thousand reais

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.