Short Story Lovers ChatGPT Plugin Is Now Live for Authors
The Short Story Lovers ChatGPT plugin is now live, helping authors upload their own manuscripts, organize chapters and story details, preview work, check publishing readiness, publish with confirmation, manage their Author Site, and review reader feedback and notifications.

NOW LIVE: November 5, 2026: The Short Story Lovers ChatGPT plugin is now publicly available for authors. Install the Short Story Lovers plugin in ChatGPT and then read the Short Story Lovers ChatGPT plugin guide for practical setup steps and copy-and-paste prompts.
This was first announced on October 6 and updated on November 5, 2026. The plugin connects ChatGPT to your own Short Story Lovers author account through OAuth. It is designed to help you add your own completed work, manage chapters and story details, preview stories, check publication readiness, publish when you explicitly confirm, maintain your Author Site, review privacy-minimized audience feedback, and manage notifications.
What began as a quiet project is now a live integration that goes beyond adding another AI feature to Short Story Lovers.
Short Story Lovers for ChatGPT is now available to authors. Through the plugin, ChatGPT can connect to an author's Short Story Lovers account and work with their real SSL stories, drafts and author tools.
The goal is simpler publishing and Author Site management, not AI-written stories.
The integration lets a writer stay inside a natural conversation while ChatGPT can safely understand and work with the things that already exist on Short Story Lovers: Drafts, chapters, story metadata, publishing readiness, Author Site, reader feedback, notifications and the author's current SSL eligibility.
The conversation can continue where your writing actually lives
Authors write their stories. Afterward, uploading chapters individually, setting categories and tags, and updating Author Site details can take time.
The problem usually begins after that.
The actual manuscript may be sitting somewhere else. The writer has to copy text back and forth, remember where the latest Draft lives, update metadata separately, preview it in another tab, check whether it is ready to publish, and then move through the publishing workflow.
The live integration helps remove much of that friction.
With the connected SSL integration, an author can ask things such as:
- “Which of my stories still need a category, subcategory or tags?”
- “Show me my unfinished stories.”
- “Organize my completed manuscript into chapters so I can approve the structure.”
- “Add my completed chapter three exactly as written, and save it as a Draft.”
- “Use this image as the cover.”
- “Is this story actually ready to publish?”
- “Make this Private, but ask me before you do it.”
- “What are readers saying about this story?”
- “Improve the headline and About section on my Author Site.”
- “Do I have any new Short Story Lovers notifications?”
ChatGPT can suggest ways to organize the work and handle repetitive publishing steps. Short Story Lovers supplies the live account state and performs the bounded author action.
That distinction is central to how the integration works.
It works with the real author account, not a copy of it
Once an author connects Short Story Lovers through OAuth, ChatGPT can identify the connected author and request only the SSL capabilities needed for the task.
It can find the author's own stories and return their real state: Draft, Private, Published or Pending. It can retrieve the current content and chapters, work with live story versions, and return the actual Short Story Lovers Preview, Edit or public story link supplied by SSL.
It also understands live product context.
For example, when an author asks whether something can be published, ChatGPT does not need to guess the author's plan, quota, Private Story allowance, publishing eligibility or current story state. It asks Short Story Lovers for the current answer.
That is important because those rules can change. They should come from SSL at the moment the author asks, not from a static AI explanation remembered from months earlier.
Draft-first by design
One of our strongest product decisions has been to keep manuscript uploads and changes Draft-first.
Adding an author-written manuscript through ChatGPT saves it as a Draft. Updating a title, category, description or tags stays a Draft edit. Uploading an author's completed chapter stays an authoring action.
Publishing is separate.
Authors can organize and prepare their existing writing without every save becoming a potentially public action.
The current integration can save author-supplied standalone and multi-chapter manuscripts as Drafts, update selected story details, save completed chapters, reorder them, set a story cover and help prepare the work for publication.
It can also return the SSL Preview link after meaningful Draft work, so the writer can see the story in its real Short Story Lovers context before deciding what happens next.
Publishing is something the author still controls
We do not want “publish” to become a casual side effect of a conversation.
Before a consequential story-state change, the integration checks the live Short Story Lovers readiness state again.
If something is blocked, the author gets the real blocker.
If the story is ready, ChatGPT can explain what is about to happen and then ask for explicit confirmation.
Only after that confirmation can the supported transition happen.
The live V1.3 integration supports transitions such as publishing publicly, sharing as a Private Story, publishing for subscribers when the author is already eligible, moving an eligible story back to Draft, and publishing eligible chapters.
This is one of the places where the integration becomes more useful than a generic writing assistant. It can move from “here are suggested categories and tags for your approval” to “your Draft is saved, here is the Preview, and here is exactly what still blocks publication.”
Covers can be part of the same flow
Cover handling has also been built into the author workflow.
An author can supply an image through ChatGPT and use it as the story cover. We have also tested the flow where a cover is generated in ChatGPT, the author approves it, and the approved image is handed to SSL.
Short Story Lovers still performs its own file validation and normalization before saving the cover.
The goal is not to make image handling invisible. The goal is to make it feel like part of the same creative session.
Multi-chapter stories are first-class
A large part of SSL writing is not a single standalone story.
The V1.3 integration therefore treats chapters as real authoring objects rather than flattening everything into one text field.
ChatGPT can inspect the chapter workspace, add an author's completed chapter as a Draft, update chapter details, reorder chapters, remove an eligible chapter with confirmation, and publish selected eligible chapters after the appropriate checks.
That also opens up much more natural writing conversations.
An author can organize an existing manuscript into chapters, review the chapter order, add completed chapters, and assign chapter titles without repeating each publishing step manually.
November 14 update: Manage stories in 54 languages through ChatGPT
The live Short Story Lovers plugin now supports managing author-written manuscripts and chapters in 54 story languages. Authors can provide their own text in Hindi, Spanish, Urdu, French or another supported language, add it to SSL, organize the details, and check current publishing rules. The story language is chosen explicitly; using the plugin does not translate or automatically publish a manuscript.
Eligible public non-English stories can be submitted for free multilingual review, without needing a Pro Author membership for that review. ChatGPT asks for confirmation before submission. Under Review does not mean Published: a story becomes public only after SSL approves or automatically clears the review checks. Eligible chapters in already-published non-English series also follow review before release. English publishing and Private Story rules remain unchanged.
For setup steps and examples, read the Short Story Lovers ChatGPT Author Guide and our multilingual review guide.
It can help after the story is published too
We do not think the author journey ends at Publish.
The plugin can work with the connected author's Author Site, including public presentation fields such as the headline, About text, social links, spotlight stories and supported branding.
That means an author could ask ChatGPT to read the current headline, suggest a stronger version, save the chosen wording and then return the live Author Site link.
It can also provide privacy-minimized audience context and story feedback.
For an author's own story, ChatGPT can retrieve bounded rating/comment signals and summarize what readers are saying without unnecessarily exposing reader identity.
It can also help moderate an unwanted comment on the author's own story, but only within a deliberately narrow moderation boundary.
And for day-to-day account awareness, the plugin can read SSL notifications and update supported notification preferences.
What this can feel like for a writer
This is the part we are most excited about.
Imagine finishing a writing session and saying:
“Find my most recent Draft. Suggest relevant categories and tags based on my existing story, and ask me before saving any changes.”
ChatGPT can locate the actual Draft instead of asking the writer to paste it again.
After the author approves the details:
“Preview it.”
The response can return the actual SSL Preview link.
Then:
“Is it ready to publish privately?”
Instead of giving generic advice, ChatGPT asks SSL for the live readiness result.
If it is ready:
“Okay, make it Private.”
The state change still requires the author-controlled confirmation boundary, and the resulting Short Story Lovers link comes back into the conversation.
The same conversation can later become:
“What are readers saying?”
or:
“My Author Site headline feels weak. Can you improve it?”
That continuity is what makes the idea interesting to us.
Tested with real author journeys
Before the public launch, we ran end-to-end QA on connected author workflows. In those tests, ChatGPT successfully:
- listed recent Short Story Lovers stories from a connected author account
- identified the author's latest Draft
- returned the real SSL Preview link
- found the story with the strongest available engagement signal
- updated Draft metadata and content through the connected author workflow
- accepted story-cover handoff from ChatGPT
- checked Private publishing readiness
- waited for an explicit author instruction before the story-state change
- successfully changed an eligible story to Private and returned the SSL continuation
- worked through a real taxonomy inconsistency and, after the underlying rule was corrected, saved the compatible category state correctly
- refused a request to withdraw earnings and change payout banking details because those operations are intentionally outside the public plugin
The last point matters as much as the successful writes.
A useful author assistant also needs to know what it must not do.
Twenty-two tools, but the number is not the point
Under the hood, the live plugin provides 22 narrowly defined tools for writing, managing stories, and contacting support.
They cover connected author context, stories, Drafts, covers, chapters, publishing readiness, story-state changes, Author Site, audience summaries, reader feedback, comment moderation on the author's own stories, notifications and notification preferences.
We deliberately avoided building a generic “do anything” tool.
Every public capability has a defined purpose, ownership boundary and scope.
That makes the integration a little less magical in engineering terms, but much more trustworthy as a product.
Things we deliberately do not let it do
There are important parts of Short Story Lovers that are not in V1.3.
The public plugin does not withdraw earnings, change bank or payout information, buy or change paid plans, spend True Reader Points or SSL Credits, purchase Featured Story placement, delete an account, change login/security information, send newsletters or bulk messages, expose subscriber personal information, or perform arbitrary admin/server/database actions.
It also cannot post a general standalone comment on somebody else's story.
We made that comment decision deliberately because a generic author-comment tool could become a spam or abuse path. V1.3 can read feedback on the connected author's own stories and can moderate comments there, but it cannot become a general comment-posting bot.
These boundaries are part of the product, not missing features disguised as limitations.
Privacy should be understandable
The connection uses OAuth rather than asking a writer to hand ChatGPT an SSL password.
The integration is scoped to the connected author and the specific capabilities the author has authorized.
Short Story Lovers receives the specific plugin tool requests needed to perform an SSL action. It does not receive the author's entire ChatGPT conversation simply because the plugin is connected.
We also minimize what comes back from privacy-sensitive areas. Audience information is designed around useful counts and summaries, not unnecessary subscriber identity. Reader feedback can be summarized without exposing personal information that the author does not need for the request.
Why MCP matters
The technical bridge underneath the plugin is MCP, the Model Context Protocol.
For a writer, the name is less important than the separation it gives us.
ChatGPT can help interpret account information, organize chapters and metadata, and explain publishing options in a natural conversation.
Short Story Lovers remains authoritative for ownership, Draft state, chapters, taxonomy, quotas, eligibility, publication rules and saved actions.
The MCP layer is the narrow bridge between the two.
That is how ChatGPT can assist with the process without replacing the author's creativity or deciding whether a story may be published.
Public launch access and the author guide
The V1.3 author experience is now publicly available. Start with the exact Short Story Lovers ChatGPT plugin link, connect your own account through OAuth, and review the requested permissions before approving.
For current platform terminology, connection steps, useful prompts, confirmation boundaries and troubleshooting, use the Short Story Lovers ChatGPT plugin guide. Availability can vary by plan, region, workspace policy, role and ChatGPT surface.
After connecting, use the plugin by mentioning it with @ or selecting it from the Tools/Plugins picker where that control is available. Do not put passwords, email codes, OAuth tokens or other credentials into a ChatGPT message. Complete sign-in in the provider authorization flow.
The plugin reads the connected author's real plan, quotas and eligibility so it can explain what that particular account can do instead of assuming everyone has the same capabilities. If a connection, permission or action fails, check the canonical Short Story Lovers link or website result before retrying a consequential action.
What we think this can become
The most interesting possibility is not that AI writes more text.
It is that an author can have a conversation that stays connected to the work.
An author can add completed chapters, organize story details, preview, understand publishing blockers, make a deliberate publication decision, update the public Author Site and come back later to discuss reader feedback, without repeating the same setup work.
ChatGPT becomes a conversational way to manage the author's Short Story Lovers publishing workflow.
The writer is still the author.
Short Story Lovers is still the publishing platform and the source of truth.
ChatGPT becomes a much more capable assistant between the two.
This was first announced on October 6, and on November 5, 2026, the plugin is publicly available for authors to try.
The Short Story Lovers ChatGPT plugin guide is the best place to begin.
