features · approval

The approval flow

Magic Share is built so that nothing reaches your readers without you. The agent researches, writes and checks, and then it stops. Every run ends in a draft, and every publish starts with a button you press or a schedule you set.

What the agent does on its own

Research, drafting and link verification run in the background, and so do a post’s hero image and X thread when you ask for them. With auto-draft switched on (Starter and Pro), the agent also wakes at 06:00 UTC and writes whatever your topic queue has due.

All of that produces drafts. No setting lets the agent publish a post you haven’t approved, on any plan.

Reviewing a draft

A draft opens with everything you need to decide:

  • the rendered article and its markdown source;
  • the link-verification report, one row per cited URL;
  • the agent’s own report on the run;
  • the X thread written from the post, or one press to write it.

A draft waits as long as you like. Approve it, leave it, or delete it if it isn’t worth keeping.

Publishing is yours

Once a post is approved, you choose where it goes:

  • A GitHub pull request against your site’s repo, using a fine-grained token scoped to that one repo. Each PR holds one markdown file, and merging it is the publish button. See blogs that live in git.
  • An X thread through the X account you connect to the site (paid plans; the free plan shows the thread as a preview).
  • A download of the markdown or HTML for any other stack.

Scheduling, when you ask for it

On Starter and Pro you can schedule approved posts and let the publish schedule space them out on your cadence. At the time you picked, Magic Share opens the pull request, checks that it holds exactly the post you approved and nothing else, merges it, and, if the site has an X account connected, posts the X thread with the live link. Scheduled posts go out because you put them on the calendar, and you can unschedule any of them before they do. Daily tweets work the same way: they post at the times on your calendar. One press spreads them across a posting window you choose, and you can move any of them or send one right away. See social posts.

After a post goes live

Once a post publishes through GitHub, the agent can propose one linking sentence in up to three of your related older posts, so the new post doesn’t start with no internal links pointing at it. Those edits arrive as their own pull request, and that PR is never merged for you.

Why it works this way

Google’s guidance on AI-assisted content is about effort and oversight, not the tool. A person who reads, corrects and approves each post is the oversight, and a draft that arrives with its sources checked is what keeps that review short enough to actually happen. The approval step isn’t a safety net bolted on at the end. It’s the product.

Try the approval flow on your own site

Add your URL, read your first draft and decide what happens to it. The first 3 posts are free.

Plant your first post