What it is

An AI writing assistant embedded directly in the SGEN content editor. Reads context from the current page or blog post + your site's existing tone, and offers inline suggestions for completing sentences, rewriting paragraphs, generating section headers, improving SEO clarity, and tightening copy.

The assistant lives inside the editor — no separate window, no separate tool, no copy-paste round-trip. Suggestions appear inline as you write. Accept with Tab; dismiss with Esc.

Why it matters

Today, content workflows often involve flipping between SGEN and a separate AI tool — writing a draft in SGEN, asking an external AI to rewrite or expand it, pasting back, editing again. The AI Assistant collapses that loop into one surface.

For operators publishing 5+ posts a month, the editor-internal loop saves the context-switch cost across every post. For teams maintaining brand voice across multiple authors, the tone-matcher keeps drafts converging on a consistent voice without manual style-guide enforcement on every paragraph.

How it works

Three layers compose the assistant:

Layer	What it does
Context engine	Reads the last 20 published posts on your site to understand topic patterns, sentence rhythm, and reference style
Tone matcher	Infers brand voice from existing content — formal vs casual, dense vs airy, declarative vs questioning
Suggestion layer	Renders inline ghost-text as you type. Tab to accept the suggestion; Esc to dismiss; continue typing to override

The model is invoked client-side from the editor. Each suggestion is a single request — no batch generation, no background pre-fetch that would charge tokens without intent.

What it WON'T do

• Won't autopublish. Every word reaches the page only when you accept it.
• Won't rewrite your published posts. Operates only on the active editor session.
• Won't share your content with other customers' models. Per-account context isolation.
• Won't replace structured fields. Suggestions are limited to long-form prose body content — titles, slugs, meta fields stay author-driven.

Current status

• Internal alpha — running on staging since 2026-05.
• Closed beta — May 2026 (invite-only via product team).
• GA target — Q2 2026.

Beta participants get access via SG-Admin → Tools → Beta features. GA will surface in the editor for all accounts on the Grow tier and above.

What changes when this ships

Items move out of the roadmap and into the Changelog when they ship. When AI Content Assistant ships:

1. This page archives to the roadmap/_shipped/ folder.
2. A Changelog entry lands at /blog/changelog/ai-content-assistant-ga with full release notes (features included at GA, accounts that get access, opt-out path).
3. A What's New highlight appears at /blog/highlights/ai-content-assistant-launches for the editorial layer.

Related reading

• Roadmap index — /roadmap
• Changelog — what shipped recently → /changelog
• What's New — editorial highlights → /whats-new-v2

Submit feedback

If you're in the closed beta and want to flag a behavior or request a capability, use the in-editor feedback affordance (the comment-bubble icon in the assistant's suggestion popover) or email product@sgen.com.

If you're not in beta but want to be considered, the team is sourcing invites from active Pro + Scale tier customers. Reach out via in-product support.