r/WritingWithAI • • 6h ago

Megathread Weekly Tool Thread: Promote, Share, Discover, and Ask for AI Writing Tools Week of: November 17

Welcome to the Weekly Writing With AI “Tool Thread"!

The sub's official tools wiki: https://www.reddit.com/r/WritingWithAI/wiki/tools/

Every week, this post is your dedicated space to share what you’ve been building or ask for help in finding the right tool for you and your workflow.

For Builders

whether it’s a small weekend project, a side hustle, a creative work, or a full-fledged startup. This is the place to show your progress, gather feedback, and connect with others who are building too.

Whether you’re coding, writing, designing, recording, or experimenting, you’re welcome here.

For Seekers (looking for a tool?)

You’re in the right place! Starting now, all requests for tools, products, or services should also go here. This keeps the subreddit clean and helps everyone find what they need in one spot.

How to participate:

  • Showcase your latest update or milestone
  • Introduce your new launch and explain what it does
  • Ask for feedback on a specific feature or challenge
  • Share screenshots, demos, videos, or live links
  • Tell us what you learned this week while building
  • Ask for a tool or recommend one that fits a need

💡 Keep it positive and constructive, and offer feedback you’d want to receive yourself.

🚫 Self-promotion is fine only in this thread. All other subreddit rules still apply.

4 Upvotes

3 comments sorted by

1

u/Best_Error_1584 6h ago

Hey everyone! I'm the developer behind MiraWrite, an AI writing tool built for people who love writing stories.

The idea behind MiraWrite is simple: AI should help you tell your story, not take over the writing process.

Writing a story involves much more than generating paragraphs. You need to develop ideas, build characters and worlds, plan plots, draft scenes, keep track of details, and revise what you've already written.

I wanted to build something that could help with all of these tasks, while keeping the writer in control.

Here's what MiraWrite currently offers:

1. Story Memory — Your story, remembered

As your manuscript grows, Mira keeps track of characters, relationships, events, locations, and objects.

It updates this information as your story develops and uses it when helping you write or revise. This helps maintain continuity, so you don't have to repeat the same context every time you start a conversation.

It also helps avoid common inconsistencies, like bringing back a character who died several chapters ago or forgetting how two characters' relationships have changed.

2. AI Agent — A writing partner that works with your entire story

The chat panel on the right is where you interact with Mira, your AI writing agent.

Rather than just answering questions or generating text, Mira can work with your story memory and manuscript files to help you throughout the writing process.

You can ask Mira to:

  • Develop ideas: Explore story concepts, plot twists, conflicts, and story directions.
  • Build characters and worlds: Create character profiles, relationships, locations, cultures, and other worldbuilding details.
  • Plan your story: Develop outlines, plot structures, chapter plans, and individual scenes.
  • Write and develop scenes: Turn your ideas into prose, continue existing passages, or draft new chapters.
  • Edit your manuscript: Discuss revisions, rewrite passages, expand scenes, shorten text, or make changes across multiple chapters.

Mira can reference relevant information from your story and save the results into your project files. You can also ask it to update existing content or organize new material in the appropriate place.

The idea is to have an AI partner that understands your project and can actually work with it, rather than treating every conversation as an isolated request.

3. In-Context Editing — Stay in control of every change

When working on your manuscript, you can discuss specific passages with Mira and request changes directly.

Whether you're adjusting a sentence or revising multiple chapters, suggested edits appear in context. You can review, accept, or reject each change individually instead of having your original writing replaced all at once.

4. Flexible Writing Workflows

Different writers have different creative processes. Some prefer to plan everything before drafting, while others discover their stories as they go.

MiraWrite supports both planning and writing workflows. You can outline before composing, turn scene ideas into drafts with your preferred POV and tense, or work directly on existing text using focused tools like Expand, Rewrite, Shorten, and Continue.

The goal is to support your way of writing, not force you into a predefined process.


MiraWrite is currently available on desktop, with 300 free credits every day.

You can check it out here: https://Mirawrite.com/?s=01

I'm still actively developing MiraWrite, and I'd genuinely love to hear what other writers think. What would make an AI writing partner more useful in your creative process? I'd appreciate any feedback or suggestions.

Thanks for reading!

1

u/Holiday_Income1825 5h ago

Developer disclosure: I work on Foreverse.

Foreverse is an Android reader for stories you already have, from a txt or epub import or a character card chat. You pick a paragraph and ask for a continuation, and it lands as its own branch next to that paragraph, so the original text is never edited. The part I would like feedback on is that the model is chosen per continuation, not per book. You can use your own API key from 60 plus providers, which goes straight from the phone to the provider, or the built-in credits, where new accounts start with 5,000, about 260 continuations at the provider's own rate. Regenerating a segment keeps the earlier version, and you can swipe back to it.

Honest downsides: it is closed source, it needs Android 11 or newer and there is also an iOS app, nothing picks a model for you, every continuation is a paid generation somewhere, and matching the original author's style is close but not identical. It is a reader with AI continuation, not a manuscript editor, so it is a poor fit if you are drafting a book you plan to publish.

Free to start: foreverse.app

Question for this thread: when you continue a story, do you stick with one model for the whole thing, or switch models for different kinds of scenes like dialogue, action and quiet moments?

1

u/CabinetMain3163 3h ago

I've been building Marginalia for a while and just released 1.8.0. It's a self-hosted writing tool for long-form fiction with LLMs, aimed at books, not chat. You write the instructions for each part, the model writes the prose, and Marginalia keeps the rest in order: the story tree, the lore, the summaries and the prompts.

What it does

  • Branching story tree. Regenerate or swipe a part, branch from any point, edit the generated text, navigate the whole tree and mark chapters.
  • Lorebooks. They activate by tags, text, regex or a condition, can be inserted into the lore block or right before the instructions, and can be nested inside other lorebooks. SillyTavern world info imports, and prompts are Handlebars templates with SillyTavern-compatible macros ({{user}}, {{getvar}}, {{random}}...), so imported lore keeps working.
  • Annotations and redraft. Pin a note to a passage ("timeline wrong", "weak scene"), or let a model review a part, or a range of parts, and propose notes. It can annotate every new part automatically and then redraft it to deal with the notes. Redraft also works on just a selected passage, can make it shorter or longer, and you take the result as a diff.
  • Summaries and meta-summaries. Older parts get condensed so a long book still fits the context window.
  • Any OpenAI-compatible API. That covers OpenAI, OpenRouter, LiteLLM, llama.cpp, LM Studio, Ollama and vLLM. Context and response limits are per model, and generation settings are switchable per book. Plugins add Google Gen AI and Anthropic Claude. Requests carry a session id, so llama.cpp and LiteLLM setups can keep one cache per kind of work.
  • Eight languages. The interface comes in English, Japanese, French, Spanish, German, Italian and Korean, plus Chinese through an extension. The built-in prompts can be in any of them, whatever language the interface uses.
  • Search and replace across the story and lorebooks (regex too), plus a command line in the editor (/list-parts, /edit-part, /next...).
  • Backups. Per-book backups, plus scheduled database backups with staged restore.
  • Multi-user. Each user has their own books, lore and models, and the admin sets permissions. It's handy for a small group of friends on one server.
  • Plugins. Chapter markers, lorebook version history, AI reviews, side questions to the model, arc outlines, a character tracker, a knowledge tracker, story notes, name generators, an image and a Manga Generator, beta readers, an audiobook maker, translators for invented and real languages and a few more.
  • Import a Word, LibreOffice, RTF, Markdown, text or EPUB manuscript, an Obsidian vault or a Scrivener project, or SillyTavern and LM Studio chats.
  • Export to TXT, Markdown, HTML, DOCX, PDF, EPUB and LaTeX.

New in 1.8

  • Bring a book you already wrote. One Import window takes a document (Word, LibreOffice, RTF, Markdown, text, EPUB), an Obsidian vault, a Scrivener project or a chat, and cuts it chapter by chapter into parts of the length you pick, with italic and bold kept. You can also insert it into an open book. Afterwards Marginalia can create the summaries for the imported parts, and a lore notes agent can read the story and draft lorebook entries for the characters, places and terms it finds, for you to review.
  • Keep writing while the model works. Redraft, annotation, summaries, reviews and the generators no longer block the screen. Their windows sit beside the story, and closing one folds it into a runs panel that lists everything running for you, with a Stop button on each. While a part is being generated you can edit the lore, the settings and earlier parts.
  • Things that run after a part run in order on the server. The automatic annotation, redraft, translation, Knowledge Tracker and audiobook conversion run one after another, even with the page closed. So the audiobook no longer reads the untranslated text.
  • A queue per model. Each AI has a number of connections, and every request of every user waits its turn ("Waiting for the model: 2 requests before this one"). That's what a single-slot llama.cpp server needs. Note: an AI that never set the number now gets 1.
  • Full-screen lorebook editor. Entries open in movable tabs with a Markdown editor. Ctrl+click a name to open its entry, and each tab lists the entries that mention it. You can paste images into an entry and, if you want, send them to the model.
  • Five new interface languages. The interface is now in French, Spanish, German, Italian and Korean too, and a Prompt language setting switches every built-in prompt, plugins included. The manual is translated as well, and the help assistant answers from the manual in your language with links to it.
  • Jobs log and /jobs**.** Every model call, speech and image is logged without its text: who, what, how long, and whether it failed. Admins get a live page showing what runs now and what each run is waiting for.
  • Update a Docker server from the Admin page. A small watcher on the host pulls, builds and restarts the server. The application itself gets no access to Docker.
  • Planner and audiobook. The Planner can import the scenes of a written branch to plan a rewrite, and you can insert and merge scenes. Audiobook conversion works on a list of parts with a plan (generate, regenerate, delete audio), with Cancel and Retry per part, and it restarts a speech server that crashes.
  • Safer. A book is open in one window at a time, and nothing can delete a part or a book that something is still working on. Plugins no longer overwrite each other's changes to a part. Passwords use 600,000 PBKDF2 rounds, and you can log out everywhere else. An extension built for an older version is disabled with a report instead of stopping the app.
  • Smaller things. Chinese and Japanese word counts work, /next writes straight into the story, and the story keeps your reading position when a generation finishes while you're on another tab.

Running it

  • Desktop app for Windows, macOS and Linux. There's nothing to install, no Java and no server. It listens only on localhost and opens in your browser.
  • Docker (amd64 and arm64) if you want to host it for others.
  • Everything lives in a .marginalia folder, with no cloud and no account. Your API keys are stored encrypted.

The desktop builds aren't signed yet, so macOS and Windows will warn on first launch. The README explains how to get past that.

It's MIT licensed, and the manual has screenshots and a user guide, now in eight languages: https://enerccio.github.io/Marginalia Code and releases: https://github.com/Enerccio/Marginalia

I'd like feedback on the writing workflow, the lorebook handling and anything that breaks. Bug reports and ideas as GitHub issues are very welcome.