Jul 15, 2026 · 5 min read
Rewrite Without Losing Your Best Draft
1MarketingTool 0.6.0 makes regeneration non-destructive: every rewrite is saved as its own version, an adjustment prompt tells the AI exactly what to change, and the version you pick can cross-post to every channel you're connected to.

You regenerate a post because the first draft isn't quite right. The hook is soft, or the CTA rambles, or it runs forty characters over the limit for X. So you hit regenerate — and the draft you had is gone. The new one fixes the CTA and loses the one line you actually liked.
That's the trade every marketing tool has quietly asked you to make: you can have another take, or you can keep this one, but not both. The usual workaround is a scratch file full of pasted drafts named final-2-actually-final.
1MarketingTool 0.6.0 — Campaign Versions and Delivery — removes the trade. Rewrites stack up as versions instead of replacing each other, and the version you settle on can go out to more than the single channel it was written for.
What changed
Regeneration is now non-destructive. Every rewrite is saved beside the original, and a dropdown on the piece switches between the latest take, earlier versions, and the content you started with. Nothing overwrites anything.

How it works in practice
Ask for another take — or say exactly what to change
Choose Re-Generate with AI on any piece and the rewrite modal opens with two methods. Fresh variation lets the AI write another take from the same campaign context — useful when the draft is fine but you want options. Adjust with prompt is the one you'll reach for more: you tell it what to change, in your own words. "Write less than 280 chars." "Make the opening more direct." "Drop the emoji." The prompt box takes up to 2,000 characters, so you can be specific about the angle, tone, details, or CTA.
The difference matters more than it sounds. A blind regenerate rerolls the dice and hopes. A prompt-guided rewrite changes the one thing you asked about and leaves the rest of the piece alone.
Pick the AI for one rewrite, not for the whole app
"CLI AI for this rewrite" lets you choose any detected local agent for this run only — your global AI route stays exactly as it was. If your default is Codex but you want Claude Code for one stubborn caption, that's a dropdown, not a trip through settings and back again.
While it runs, the panel shows generation progress, timestamped logs, and a live draft as the text arrives, so a long rewrite looks like work happening rather than a spinner.
Switch between versions without losing anything
Each finished rewrite becomes a version on the piece, and the dropdown moves between them and the original. Pick the one you want and the preview updates — attached images and video included, which now render with the selected version across the X, LinkedIn, Facebook, Reddit, blog, document, YouTube, TikTok, and Instagram previews.

That's the part that changes how you work. Trying a shorter version costs nothing, because the longer one is still sitting there.
Send that version anywhere it fits
A post written for X is usually fine on Bluesky or Mastodon unchanged. Post Now on a single piece opens Preview before posting, and under Cross-post channels you can tick any connected channel assigned to the project — Bluesky, Mastodon, LinkedIn, Discord, Ghost, WordPress, Dev.to, and the rest. The text and its attachments are reused as-is on every destination you select.

Bluesky and Mastodon enforce their own character limits, and a post over the limit used to simply fail. Now it's shortened at a word-safe, emoji-safe boundary, and the result tells you the published text was shortened.
Know what actually published
Campaign Results reports what happened to each version: publishing, success, partial, skipped, or failed — with the channel's own message, the timestamp, and a link to the public post when the network returns one. Partial delivery reads as partial instead of quietly resembling success, failed results stay open for review or retry, and View detail opens the full distribution history for that piece.
Before vs after
| What you're doing | Before 0.6.0 | With 0.6.0 |
|---|---|---|
| Improving a draft | Regenerate and lose the previous copy | Every take saved as its own version |
| Steering the AI | Reroll and hope | An adjustment prompt says what to change |
| Choosing a model | Switch the global AI route, then switch it back | Pick a CLI agent for this rewrite only |
| Comparing drafts | Paste them into a scratch file | Switch with the version dropdown |
| Reaching another network | Copy text, re-upload media, post again | Tick the channels, post once |
| Confirming it landed | Open each network and look | Per-channel state, message, timestamp, link |
Who benefits most
Solo founders posting across five networks. Writing once and cross-posting the same version is most of the job. The channels you've connected are one grid, and one confirmation covers all of them.
Anyone who edits by rewriting. If your process is generate, read it, regenerate, then versions turn that loop from lossy into cheap. You can always go back to the take you had three rewrites ago.
People running local CLI agents. Per-rewrite agent choice means you can spend a fast model on bulk drafting and your best one on the caption that actually matters, without touching settings between the two.
Try it
Open a campaign in Campaign results, choose Re-Generate with AI on a piece, and pick Adjust with prompt. Tell it what to fix. When the new version lands, use the dropdown to compare it against the original — then send whichever one won to every channel you're on.
1MarketingTool 0.6.0 is available now. Everything above runs on your machine, with your own API key or a local CLI agent.