Changelog

You can now publish finished posts straight into your Webflow CMS collection. Connect your Webflow workspace from Settings → Integrations, choose a site and collection, map your fields (title, slug, body, meta description), and pick a publish mode — draft, staged, or live.

When you hit Publish to Webflow, Parallel converts your markdown to clean, Webflow-compatible HTML (including bullet points, code blocks, and a readable fallback for tables) and creates or updates the CMS item automatically. Duplicate slug? You'll see an inline error so you can fix it on the spot.

The integration includes retry logic for transient API errors and a proactive health check — if your Webflow token expires, you'll be prompted to reconnect before you try to publish, not after.

You can now ship finished posts directly into your static-site repo. Connect your workspace to GitHub from Settings → Integrations, pick the repository and branch you want commits on, and choose a preset (Astro, Hugo, Jekyll, or Next.js MDX) so files land in sensible paths out of the box.

Parallel builds the markdown file for you — body plus YAML frontmatter driven by your field mapping — and creates or updates the file with a single commit when you publish from the content plan. Mark fields editable at publish if you want a last-pass chance to tweak slug, tags, or other frontmatter before the commit lands.

When you publish, your item moves to Published and the modal links straight to the commit on GitHub so you can open a PR, review the diff, and merge on your usual workflow.

Every draft now goes through a stronger research pass. Parallel pulls fresh information from authoritative sources — research papers, official documentation, primary-source reporting, and authoritative voices — and uses it to ground claims, statistics, and references throughout the post.

Drafts also link more thoroughly. External citations point to the sources that informed the writing, and internal links connect to your existing docs and posts where relevant. The result: less generic AI content, more grounded technical writing your readers can trust.

All content generation now runs on Claude Sonnet 4.6. Expect sharper writing, better structure, and stronger brand voice alignment across all post formats.

Parallel now decides per-post whether external research is needed, and targets primary sources when it is: official documentation, specs, changelogs, and authoritative references. Posts on fast-moving subjects (new APIs, emerging standards, competitor comparisons) get current, verified sources automatically.

The result is more accurate content with links your readers can actually trust.

We launched a public blog and this changelog. The blog covers AI discoverability, developer content marketing, and content at scale — the things we think most about as we build Parallel.

Both pages are markdown-driven so we (and you, if you're dogfooding the same setup) can publish quickly without leaving the editor.

When you send a draft for review, the editor now dims and shows a clear banner letting you know editing is paused (and who's reviewing, when available). Previously the editor stayed fully interactive, so you could type away without realizing your changes weren't being saved.

The banner clears automatically once the review is complete.

You can now regenerate any drafted content item up to 2 times for free. The first generation still costs 1 credit, but if the result isn't quite right, the next two re-rolls won't dip into your balance.

Failed generations don't count toward the limit either. If a regeneration fails, retrying it stays free.

The redraft modal shows your remaining free regenerations, and the regenerate action is disabled across the row dropdown, editor menu, and slideout once you've used them up.

When you bulk-generate from the content plan, the confirmation modal now tells you exactly how many credits the operation will use (e.g. "This will use 3 credits"). No more guessing whether you're about to blow through your balance.

The dashboard now shows a live credit gauge with your remaining balance and any overage usage at a glance. The gauge animates on load and uses two rings — one for plan credits, one for overage — so you can see your billing-period state in a single look.

There's also a new upgrade widget in the sidebar that appears once you cross 80% usage, with contextual copy to help you decide if it's time to bump up your plan. You can dismiss it for the current billing period if you'd rather wait.

KB crawl credits used to be tracked on a rolling 30-day window across your whole team. They're now per-workspace, tied to your Stripe billing period, and they carry over if you don't use them.

File uploads remain free — only URL crawls and brand kit scrapes consume KB credits. Each plan has its own KB credit allowance (Free, Launch, Build, Scale), and you'll see your remaining balance in the gauge on the knowledge base page.