The newsroom now takes requests

One field. It reads what you typed.

You never pick a mode from a menu. Type a line and it is one article. Press Enter for a second line and it becomes a list - one article per row. Delete back to a single line and it is one article again.

Whichever way in you use, the same newsroom runs: real sources found at the time of writing, the article written from them, and a record of what was checked delivered with the piece.

Seven ways to hand it work

Each one is the same pipeline underneath - they differ only in how the brief is assembled.

• A topic - one keyword or headline, one article.
• A list - up to hundreds of rows, one article each, with an optional shared outline.
• A structure you reuse - build the shape once, cross it with your own values, generate the set.
• A URL you already published - refreshed, rewritten, or written to beat it.
• Two subjects - one comparison that picks a side.
• A subject and a count - one ranked list.
• A term - one plain-language explainer.

Point it at your own sitemap

Give it yoursite.com/sitemap.xml and it lists what you publish - narrowed to a path like /blog/, and to pages untouched in the last 3, 6, or 12 months. Every operator has a hundred posts quietly going stale; this is the list of which ones.

Lists arrive from files too: .txt, .csv, .xlsx, .docx, .pdf, .json - several at once, deduplicated.

Nothing is sent unread

Hand it URLs and every page is fetched and shown to you before a generation is spent - the headline found, the domain, the word count, the date. A page it could not read is named and left out of the run rather than written against. That catches a dead link, a paywall, and a section index that was never an article.

Nothing you typed is thrown away

Leave a writing surface with work on it - the back button included - and it offers to save the list as a record you can reopen later, surviving a cleared cache and a different browser. Ten articles free over 7 days to try it, no card.

A saved list is a record, not a browser draft

Park an assignment, a list of URLs, a comparison, a rundown or a set of terms you are not ready to send. Every writing surface parks, and what it writes is a record of its own rather than a draft held in this browser, so it survives a cleared cache and a different machine.

Each surface offers back only what it parked, because a list of addresses is not a list of topics. Saving the same thing twice keeps one copy; anything different keeps both.

Value lists, saved once

Save a table of values once, by pasting it in or loading a CSV, and cross it with any Blueprint run afterwards. The structure is reusable and so is the data you run through it.