claire vo
← all AI workflows

Schedule podcast and blog posts in Sanity with Codex browser use

A bitmap publishing desk with four related page proofs passing through a press and one date marked on a calendar.
sanity-publishing-desk.png
A bitmap publishing desk with four related page proofs passing through a press and one date marked on a calendar.
Codex + computer use + Chrome + Sanity

A How I AI release includes the episode post and companion posts explaining the workflows from the conversation. Getting them all ready means finding the related drafts, checking their URLs, and scheduling each one. It’s a lot of clicking through the same CMS screens.

I gave Codex the episode and publish date, with Sanity already open in Chrome. Using computer use in that browser session, it found the three companion posts, cleaned up the URLs, and scheduled all four. I could delegate the release as one task instead of walking through each post myself.

Promptpublishing-preflight.md
# Schedule a podcast release

Use browser or computer use in the CMS session I already have open. Help me prepare and schedule the episode and related posts I select.

I will provide the episode, publish date, time, and time zone. Find its companion posts and handle the repetitive editing and scheduling work across the set.

## 01. Identify the release

Confirm the exact documents, publication date, time, and time zone. Check the current draft and schedule status of every document. Do not guess which similarly named post belongs in the release.

## 02. Review the content

Check titles, slugs, internal links, summaries, images, and required fields. Flag anything missing or inconsistent. Distinguish a saved draft from a scheduled snapshot.

## 03. Check the version that will publish

Make sure the scheduled version contains the intended draft changes. If the CMS keeps an earlier snapshot, show me what must be replaced and preserve the latest draft.

Ask for approval of the exact content and schedule before creating or replacing publication schedules, unless I have already approved them in this session.

## 04. Read it back

After the authorized scheduling action, verify each document's saved slug, scheduled version, publication date, and time zone. Report scheduled and published states separately. Note any links that will only work after publication.