Build a source-backed content queue with Codex
I started by asking Codex which people I interacted with on X, then expanded the question to their companies, colleagues, and past How I AI guests. It used authenticated X tools and the podcast feed to build a watchlist. Looking only at familiar accounts missed useful people doing related work.
From there, I asked for a way to connect those public conversations with ideas from my own work. Codex created a local content store with source-linked records from project work and meeting notes, plus privacy labels to keep private material out of public drafts. It set up a morning research routine, an evening capture routine, and a weekly editorial pass. The first research digest was ready that night.
The digest suggested a few conversations where I had something relevant to contribute, with the original post and an angle to consider. Nothing posted automatically. The work I was handing off was finding the sources, connecting them, and keeping the ideas somewhere I could return to, rather than reconstructing the week whenever I wanted to write.
# Capture ideas from actual work
Adapted from my workflow; this is not the original transcript.
Review the work sources and public feeds I authorize for this run. Look for a small number of useful ideas grounded in something I actually did, observed, or learned.
For each idea, save a short claim, the supporting source links, what happened versus what was only proposed, why it might help a reader, and what still needs verification. Mark whether the source is public, needs anonymization, requires permission, or must remain private. Do not turn private quotes or details into public copy.
Compare with the existing queue and merge duplicates. If a relevant public conversation exists, include its original link and explain what experience I could contribute. Skip conversations where I have nothing useful to add.
Give me a short digest to review. Keep all ideas as private research or drafts; do not post, reply, like, or message anyone.