Can you write a local newsletter with just Claude or ChatGPT?
Yes, and here is how to do it properly, plus the four things a repeatable AI newsletter needs and where the chat-only approach honestly breaks.
A manual local newsletter workflow, research, writing, formatting and checking, usually takes 2 to 3 hours per issue, while lightbreak says most publications on its system ship an issue in under 15 minutes from source to send. That gap is not really about the writing tool. It is about whether the work lives in a system or gets rebuilt from scratch every week. This piece argues that Claude or ChatGPT can absolutely produce your newsletter, but that without a saved source list, standing section instructions, a fixed design and a human editing step, the output drifts until the workflow stops being repeatable.
The short answer
Yes, you can write a local newsletter with just Claude or ChatGPT. Paste in your local news links, tell the assistant who your readers are and what sections you want, and it will draft a credible issue in minutes. For a first issue, or an occasional one, that is enough. The trouble starts at issue ten. A fresh chat has no memory of your town, your voice, your section structure or your layout, so every week you are re-explaining everything and getting a slightly different result.
That is the honest answer the operator of a local publication needs. The chat is a capable writer and a terrible editor-in-chief. It drafts well and remembers nothing. The fix is not a better prompt typed faster, it is moving the parts that should never change out of the chat and into a document, or into a system built to hold them.
What breaks when the chat is the whole workflow
Three breaks show up reliably. First, drift. Each new chat session produces a different structure, tone and quality than the last, because the assistant is starting from zero. Your readers feel this before you do. Second, no standing feeds. A chat assistant does not know what happened in your town this week unless you paste it in, and the discipline of pasting in the same sources every issue is exactly what falls apart on a busy week. Third, no held design. The chat does not hold your layout, so the issue you paste into your email platform looks different every time and formatting becomes a manual chore.
Each break has a fix, and none of the fixes require buying anything. The pattern behind all of them is the same: write it once, save it, reuse it every week.
The four things a repeatable AI newsletter needs
Whichever tool you use, a repeatable AI newsletter workflow needs four things: a saved source list checked every issue, instructions written once in advance for each section, a fixed design, and an editing step a person controls. Here is the do-it-yourself version of each with nothing but a chat assistant and a document.
- 01Write your source list once
Create a document listing every local source you check each week, such as the city and school district news pages, the police log, event calendars, shelter pets, new business listings and home listings, then paste the whole list into the chat every issue.
- 02Write standing section instructions
For each recurring section, such as New This Week, Pet of the Week or the events calendar, write one saved instruction describing the format, length and voice, and reuse it verbatim instead of prompting from scratch.
- 03Fix the design in a template
Build the layout once as a template in your email platform with fixed slots per section, so the chat only fills slots and the design never drifts.
- 04Add a human edit before send
Read the full draft, open the source links yourself and check names, prices, dates and places, then a person decides when it sends. The assistant drafts, you edit and send.
That document-plus-chat setup is genuinely workable, and some publishers will be happy with it indefinitely. It costs nothing beyond the assistant subscription and your email platform, and it fixes the worst of the drift because the source list and section instructions stop being improvised. What it does not fix is the weekly labor of gathering, pasting and checking, which is the same labor that makes the manual workflow take hours.
Where the chat-only version stops scaling
The do-it-yourself version holds up for one publication on a regular schedule. It starts to strain when you add a second publication, a small or part-time team, or a week where the deadline arrives before the paste-and-gather work does. At that point the workflow needs the same four things, but held somewhere sturdier than a document: a system that works like a database holding the feeds, the saved section instructions and the design, which a person or an AI agent can pull from.
That is the idea behind lightbreak. It is newsletter publishing software for local media that pulls in local news, restaurants, businesses, homes, events, pets and jobs, writes each story in the publication's voice, and pushes the finished issue to Beehiiv or ActiveCampaign. It checks a publication's sources every morning, holds the section instructions and design, and a review agent reads the whole issue against every source it came from, listing what to fix without sending anything. A person still decides when an issue sends, and AI agents such as Claude or ChatGPT can use lightbreak over MCP, a protocol that lets an assistant call the same tools as the app, so your own agent can build an issue, write sections and push a draft. Most publications on lightbreak ship an issue in under 15 minutes from source to send, against the 2 to 3 hours the manual workflow usually takes.
To be fair, if you publish one newsletter, enjoy the weekly gathering and have the hours, the document version is the better fit and costs nothing new. The system earns its place when the math in the workflow stops working, which is when publishers typically switch, as a separate lightbreak article on the 2026 shift describes.
What to do first this week
Start with the source list. It is the one piece that improves both workflows immediately, chat-only or system-backed. Open a document, list the five to ten local sources you want covered every week, and paste them into your assistant with one section's saved instruction. If the first draft holds together, add the other sections the same way. If the weekly paste-and-check becomes the bottleneck, that is the signal to look at a system that holds it for you.
