Saved Plans: Reopen an Episode Without Paying Twice

August 21, 2026 7 min read

What it does: Keeps every episode you plan — with the corrections you made on it — so you can open it again months later without re-reading the episode and without spending anything.

Antradus AI Studio v2.7.0 · Last updated 2026-08-26

Cannot find this tab? It is part of Studio. On a Publisher licence the Bulk Publishing screen shows it locked rather than hiding it, so you can see what it does before deciding — see Installation & License Activation.

Why this exists

A plan costs you twice, and only one of those costs is money.

Reading a three-hour episode is around twenty requests. That is the part you can see on the invoice. The part you cannot see is the twenty minutes you then spend on the plan screen: telling the plugin which voice is the guest, fixing a name the captions misheard, deciding which of fourteen quotations are actually worth printing, correcting a sponsor row that came through with the discount code mangled.

None of that is guesswork the plugin can redo for you. It is your knowledge of your own episode. And until this version, all of it lived in a twelve-hour session and then evaporated. Close the tab, come back on Monday, and the episode had to be read again from scratch — at full price — and every one of those corrections made again by hand.

Saved Plans is the fix. It is not a cache and it is not an optimisation. It is the thing that stops the expensive half of the work being thrown away.

Where it lives

Antradus AI → Bulk Publishing → 💾 Saved Plans, the tab beside Podcast to Articles.

Saving a plan

Two ways, and you will mostly use the second without thinking about it.

On purpose. Once an episode has been planned, a 💾 Save this plan button appears next to the button that writes the articles. Press it whenever the screen looks right.

On the way out. The plan also saves itself when you press the button that creates the articles. That is the moment a plan is finished being corrected — and it is also the moment you stop thinking about it, which is exactly when losing it hurts.

Saving the same episode twice in one sitting updates the same record rather than piling up near-identical rows. The second save is the corrected one, so it is the one that is kept. Re-reading the episode from the top starts a fresh record instead, so a new read can never overwrite a plan you meant to keep.

Opening one

Press Load on any row. The podcast screen comes back exactly as you left it: the same settings, the same articles ticked, the same titles and keyphrases you typed, the same speaker chosen on each quotation, the same sponsor and link rows.

Nothing is re-read. Nothing is charged. Loading a plan costs zero requests.

If a plan is already open on the screen, you are asked before it is replaced.

Before you spend anything

Paste an episode address you have planned before and a line appears above the read button, before you have committed to anything:

💾 You planned this episode on 3 May — 7 article(s), 12 quotation(s), about 13 requests spent. Open that plan instead of reading the episode again?

You can take it or dismiss it and read the episode again. The check recognises the same episode from a share link, a full watch link, a link with a timestamp on the end, or the bare id — the four ways the same episode reaches you.

This is the feature paying for itself, and it is the reason the offer is made before the read rather than after it.

What is stored


The plan	Every article, its title, keyphrase and brief, and which ones you ticked
Your corrections	The speaker you chose on each quotation, every name you typed, every edited sponsor, link and glossary row
The screen	The settings above the plan, so the whole page comes back, not just the list
The episode	Service, addresses, show, guest, thumbnail, and the measured clock offset in Both mode
The recording	The transcript itself, compressed — see below
The outcome	Which articles have already been written from this plan

The recording, and why it is kept

The plugin already keeps a copy of each episode beside the episode itself, so that an article written days later can still have its quotations checked. That copy is cleaned up after thirty days, because it exists to serve a drip schedule, not an archive.

A saved plan keeps its own compressed copy, and that one is not cleaned up. This is what makes an old plan fully useful rather than half useful: quotations can still be checked word for word against what was actually said, and articles can still be placed against the stretch of the episode they came from. When you load a plan whose thirty days have passed, the recording is put back where the rest of the plugin expects to find it, and everything works exactly as it does on a fresh read.

A three-hour episode is a few hundred kilobytes compressed. The Saved Plans tab shows what your plans are costing in storage, and there is a switch to stop keeping recordings if you would rather not. A plan saved without one still reloads — it just cannot re-check anything, and it says so on its row and again when you open it.

Two deliberate refusals

A plan from a different version is refused, not partly loaded. If the stored format does not match the one this copy of the plugin understands, you are told so by name — both formats, in the message — and nothing is put on screen. A plan that loads with three fields silently missing looks fine and is not, and you would find out somewhere downstream. Refusing is the safe failure.

The same applies at a smaller scale: if the plan loads but the screen it was captured from has since changed shape, the plan itself is restored and you are told plainly that your row edits could not be put back and should be re-checked. Nothing is guessed into place.

A plan too large for your database is saved without its recording. Some shared hosts refuse a database write over a certain size. If that happens, the recording is dropped and the plan is saved anyway, and you are told. Losing the recording costs a reload some of its powers. Losing the save would cost you the corrections — which is the whole reason the feature exists — so the recording is what gives way.

Writing the articles twice

A plan remembers which batch it produced. Open one that has already been used and it says so:

4 articles have already been written from this plan. Creating articles again will write them a second time.

It does not stop you — sometimes writing them again is exactly what you want, after changing the settings or the ticks. It just makes sure you are choosing it.

Duplicate gives you a copy that has written nothing yet, which is the cleaner way to run the same episode a second time with different settings.

Moving a plan between sites

Export hands you a .json file containing the plan, your corrections and the recording. Import on another site reads it back. The import is validated exactly as a plan submitted from the screen is — a file that is not one of ours, or is in a format this version does not understand, is refused with a reason.

This is also the practical way to send us a plan that is behaving strangely.

Uninstalling

Saved plans are not deleted when you uninstall the plugin, unless you explicitly tick the box on this tab asking for that.

Months of your own corrections are not something an uninstall should quietly take with it. The default is to leave them, and the box that changes it is off until you turn it on.

What this did not change

Nothing in Podcast to Articles behaves differently. Quotation verification, the trim rules, punctuation, attribution, timestamp mapping, the measured clock offset in Both mode, how quotes are dealt to articles, and every word of the articles themselves are exactly what they were. Saved Plans watches that pipeline and keeps what it produces; it does not sit inside it.