How to Automate a Daily News Brief With Codex

TL;DR

You can use Codex to build a daily news brief around your interests, schedule it for the morning, and save the results as a webpage you can open in your browser. In this walkthrough, I set up a short daily edition and a separate Monday, Wednesday, and Friday edition for stories that deserve more context.

I follow AI tools, search marketing, markets, and fantasy football, but I do not want to spend an hour reading through every update. I want a short brief that tells me what happened and gives me a link when I want to read more.

For this project, I asked Codex to suggest topics based on the work I already do, separate quick headlines from longer coverage, and create something I could read like a small newspaper. I also wanted the results in chat, so I would not have to open a separate file every time.

The setup was mostly a matter of explaining what I wanted. There was one useful correction along the way: Codex initially made a dashboard about the instructions instead of a dashboard containing the news. That difference matters when you turn the task into an automation.

In this guide:

  • You will create a dedicated folder and connect it to a Codex project.
  • You will choose the subjects, sources, and length of each edition.
  • You will ask for news in chat and in a readable HTML dashboard.
  • You will test the output and review the recurring schedule.

This guide is for people who want news about their work and interests without building a separate news application. You do not need to write the dashboard code yourself, but you do need to review the stories and check that the saved file contains what you requested.

Create a project for your daily news brief

Give the brief its own folder so Codex has a clear place to save the instructions and finished editions. In the recording, I create a Codex folder on my Desktop and put a News Briefs folder inside it.

The location looks like this:

Desktop/Codex/News Briefs/

You can use a different location. The important part is knowing where the files will go and keeping them separate from unrelated work.

To connect the folder:

  1. Create the News Briefs folder on your computer.
  2. Create a project in Codex and name it News Briefs.
  3. Select the folder you just created as the project location.
  4. Start a chat and confirm that Codex is working in that folder.

I use Codex in OpenAI’s desktop app for this demonstration. If you need to install the app or check the current interface, use OpenAI’s desktop app setup guide. The current documentation calls it the ChatGPT desktop app and includes Codex alongside ChatGPT.

My Desktop also syncs through iCloud, which gives me a way to find the saved files on my phone. That depends on having Desktop and Documents syncing enabled; putting a folder on your Desktop does not automatically enable it. Apple explains the setup in its guide to syncing Desktop and Documents.

Keep the project folder available locally for scheduled runs. Syncing the finished files to another device is separate from running the task on your computer.

Choose topics from the work you already do

You can ask Codex to suggest news categories from an approved project folder, or you can give it a topic list yourself. I use my Hermes Projects folder because it reflects much of my regular work and interests.

The suggestions cover subjects such as AI agents and coding tools, local AI, Mac hardware, markets, search and digital marketing, web development, and fantasy football. Those subjects make more sense for my brief than a general list of whatever happens to be trending.

I also tell it not to include specific client names or personal information. An adaptable version of that request is:

Review the non-sensitive project material in [APPROVED FOLDER]
and suggest categories for a personal news brief.

Do not open tax records, credentials, private correspondence,
or confidential client documents. Do not include client names
or personal details in the suggestions.

Break the suggestions into a topic list and explain briefly
what news each category would cover.

Do not create files or schedule anything yet.

Replace the bracketed folder with a location you are comfortable letting the agent read. Asking it to leave names out of its answer is not the same as preventing it from accessing private documents. If the folder mixes public research with sensitive work, give it a cleaned topic list instead.

Once you have the suggestions, choose which subjects deserve regular coverage. I ask for the first four topics on my approved list to receive daily attention, with the remaining categories included when there are meaningful updates. You should choose those priorities for your own brief rather than copy mine automatically.

Give the two editions different jobs

The morning edition should help you catch up quickly, while the less frequent edition should explain developments that need more reading. I ask for both because a short headline and a useful analysis are different things.

For the daily version, I want timely stories with brief summaries and links. For the Monday, Wednesday, and Friday version, I want major developments with enough context to understand why they matter.

Edition Schedule in the walkthrough What it should contain
Morning brief Daily at 7 a.m. Timely headlines, short summaries, and links to the original stories.
Longer edition Monday, Wednesday, and Friday Major developments, more explanation, and links for further reading.

The longer edition is not simply the morning headlines with extra words. You could ask it to explain a significant product release, a change in search, or an economic announcement that needs background.

I also request a limit of three to five stories per topic. Treat that as a ceiling, not a requirement to fill every category. If nothing useful has changed, the agent should not manufacture a reason to include another story.

There is a limit to the phrase “one sheet,” too. Several categories with multiple stories can still create a long document. If you want a strict reading length, add a total word limit across the whole brief. That is a refinement you can make after reviewing a sample.

For a related workflow in Hermes, I have a separate guide to scheduling daily news briefs in Hermes. This walkthrough uses Codex’s scheduled tasks instead.

Set the rules for sources and summaries

Tell Codex how to select and summarize the news before you ask it to repeat the task. A topic list alone does not explain which sources to trust, how recent a story should be, or whether several articles are reporting the same event.

In the recording, I point out that you can request specific publications. You can also ask for official announcements and original reporting where available, rather than several summaries of the same release.

You could add these rules to the instructions:

Use current web sources for the news. Include a direct source
link for every story and the publication date when available.

Prefer official announcements and original reporting. Combine
articles about the same development instead of repeating it.

Keep each morning summary brief. Explain what happened and why
it is relevant to the category. Separate reported facts from
commentary, predictions, and your own interpretation.

Do not invent a story, quotation, date, or URL. If you cannot
verify a claim or access a source, say so. Do not fill a category
just to reach the maximum number of stories.

Open a few source links during the first review. Check that the article exists, that it is recent enough for your edition, and that the summary says what the source actually reports.

A brief is useful because it helps you decide what to read. It should still give you a way to inspect the original information.

Ask for the news in chat and in a dashboard

Specify both outputs: a readable brief in chat and an HTML file containing the actual stories. An HTML dashboard is simply a webpage saved as a file, which you can open in a browser.

My layout has topic navigation on the left and the news in the main section. The goal is to move between subjects without scrolling through a long conversation. You can change the colors and arrangement to suit how you like to read.

I provide an existing design in the demonstration. If you do not have one, describe the layout in ordinary language. For your own version, you could also request dated files and a layout that works on smaller screens:

Create a readable HTML dashboard for the news brief.

Put the topics in a left sidebar and the actual news stories
in the main area. Include the edition date, story headlines,
short summaries, publication names, and direct source links.

Make the layout work on smaller screens, with readable text
and navigation that does not cover the stories.

Save each edition as a separate dated HTML file in this project
folder. Keep the earlier editions instead of replacing them.

Each run should also return a readable brief in chat and give
me the location of the saved HTML file.

The dashboard must contain that edition's researched news,
not just the instructions for producing it.

I use a similar approach in my guide to building an AI marketing dashboard: describe the information and controls you need, then inspect the result rather than judging it only by its appearance.

Confirm the instructions before scheduling

Ask Codex to repeat the plan before it builds or schedules anything. I make that request in the walkthrough so I can check the topics, timing, and delivery format together.

This is also the point to confirm your timezone. “7 a.m.” needs to mean the morning where you live, not an assumed timezone.

You can adapt this planning request after approving the topic list:

Plan two recurring news editions using the topics we approved.

The morning brief should run daily at 7 a.m. in [TIMEZONE].
The longer edition should run on Monday, Wednesday, and Friday
at [TIME] in the same timezone.

Review the four priority topics each day. Include the remaining
categories when there are meaningful updates. Include no more
than five stories per topic, and fewer when appropriate.

The morning edition should be brief and timely. The longer
edition should explain major developments in more detail.

Use the source rules and dashboard requirements we approved.
Each scheduled run should start a separate chat and save the
actual news as a dated HTML file in this project folder.

Confirm the full plan, including the schedule, sources, output
locations, and required permissions. Wait for my approval before
building or creating the scheduled tasks.

Replace the bracketed time and timezone before using the prompt. Choose a time for the longer edition separately from the daily 7 a.m. brief.

Once the plan looks right, ask Codex to generate a sample manually. After you have checked it, approve the creation of the two scheduled tasks and confirm their next run times in Scheduled.

OpenAI’s guide to managing scheduled tasks confirms that standalone tasks start a new chat for each run. It also explains the Scheduled view, where you can review tasks and their results.

For this local project, keep your computer on, the app running, and the project folder available when the task is due. Saving the output in iCloud does not move the scheduled work to the cloud.

Use only the access the task needs. The brief needs current sources and permission to save its output, but it does not need unrestricted access to unrelated files. Confirm that those actions can run under the task’s unattended permissions before relying on the schedule.

Test the actual news before relying on the automation

Generate a sample edition and open the saved dashboard before waiting for the next morning. OpenAI recommends testing the prompt manually before scheduling it; that gives you a chance to fix the output without repeating the same mistake every day.

In my demonstration, I ask for a preview so I can see real stories rather than only the design. The recording also shows the Scheduled section with the active tasks and the next daily run set for 7 a.m.

The main issue is what Codex puts in the HTML file. It initially treats the dashboard as a place to present the instructions. I clarify that the dashboard itself needs to contain the news, like the newspaper I described.

If that happens, a direct correction is:

The HTML dashboard should contain the actual news for this
edition, not an explanation of the automation instructions.

Populate it with researched stories, short summaries, and
working source links. Open the saved file and verify the
stories appear there. Use this requirement for future runs too.

After a correction like this, open the saved file again before treating the dashboard as finished. The agent saying it understands is not enough to confirm the result.

For your own test, confirm that the stories appear in both requested formats, the links open the right sources, and the file is saved in the correct folder. Then review the first scheduled run as well. A task appearing in Scheduled confirms that it exists, not that its next edition will be correct.

I use the same order when building a daily Gmail recap. Check one useful result before asking an agent to repeat it.

Change the brief as you learn what you read

Use the Scheduled section to review the task and pause it when you no longer need it. In the walkthrough, I also show that the model, reasoning effort, project, and instructions can be changed.

You can ask Codex in chat to update the topics or timing, too. After any change, open the scheduled task and confirm that the new instructions and schedule were saved. A discussion about changing the brief is not the same as changing the task.

If you mostly open the search marketing stories, give that category more attention. If a subject rarely produces useful updates, include it only when something significant happens. You can also switch the morning edition to weekdays if you do not want weekend briefs.

The first version gives you something to react to. The next versions should reflect what you actually read.

Frequently asked questions

Do I need to write code to set this up?

You can ask Codex to create the dashboard and scheduled tasks in ordinary language. You still need to choose the folder, approve the instructions, check the necessary permissions, and review the first results.

Will the local brief run if my computer is off?

No. OpenAI’s documentation says project-based scheduled tasks need the computer powered on, the desktop app running, and the project available on disk. Syncing the output folder through iCloud does not remove those requirements.

Do I need Hermes or Skill Deck for this workflow?

No. This demonstration uses Codex in OpenAI’s desktop app. Hermes is a separate agent, and Skill Deck is a companion app for browsing and organizing Hermes skills; neither is required to create this brief.

Build a brief you want to read

Start with the subjects you care about, give the short and longer editions different jobs, and make the sources easy to open. Test the news itself before you rely on the schedule, especially if the first dashboard contains instructions rather than stories.

If you also work in Hermes, visit my new Hermes Skill Deck preview page to see the app I am building for finding and organizing skills across profiles. The page includes the current free project and a preview of Premium, which is still in development. It is separate from the Codex setup shown here.

If you want help adapting a recurring brief or dashboard to your business, you can discuss your marketing automation needs.

Leave a Comment

Scroll to Top