I shipped StoryWeave v0.10.0 today. This is a product update focused on making long-form AI writing more predictable before generation starts. What changed:
- Chapter planning now shows estimated AI credit usage before generation starts.
- Scene Plan expansion checks available credits before running.
- If the estimate is insufficient, StoryWeave blocks the job before the model call and shows wallet top-up or plan upgrade guidance.
- Wallet balance is shown with estimated credit coverage, so authors can decide how much to recharge when they only need a small extra amount.
- Plan purchases now activate immediately when allowed.
- Same-tier and lower-tier plan purchases are blocked while active plan credits remain; wallet top-up is the intended path for short-term extra usage. This came from testing real long-form generation flows. Longer projects, especially high-quality runs, need clearer cost visibility before the author starts a large job. StoryWeave is still aimed at author-controlled fiction writing: plan the story, generate structure, draft with AI assistance when useful, review and edit manually, then save and export only the text the author approves.
I shipped StoryWeave v0.9.0. This is not a relaunch, but a product update focused on making the long-form writing workflow clearer. What changed: - StoryWeave now keeps one editable current outline. - Regenerating replaces the current outline instead of creating outline history. - Optional extra generation instructions apply only to the current generation run. - The onboarding guide, writing assistant, landing page, and SEO pages now describe the same workflow. The reason behind this change is simple: outline history was adding friction. For many authors, the more useful workflow is to keep one current outline, revise it directly, and move forward into chapter planning and saved chapter text. StoryWeave remains an author-controlled AI writing workspace for long-form fiction. AI can help with planning, drafting, review, and structure, but the author keeps the final judgment.
I shipped StoryWeave v0.8.0 today. This update adds Thinking Records: a Markdown timeline for the writing process itself. What changed: - Writing-assistant discussions are now saved as Markdown records. - The records cover site help, web research, story brainstorming, and AI review. - Early exploration can stay "Unfiled" before a project exists. - Project-specific thinking can stay attached to the current project. - Project foundation fields can be revised after creation. - Later outline generation, review, and chapter planning use the latest saved project foundation when the author triggers them. This is part of the same product direction as previous releases: StoryWeave is meant to be an author-controlled workspace, not a one-click novel generator. AI can help with research, brainstorming, planning, and review, but the writer keeps the judgment and the final control.
This update focuses on making the product more useful for real writing projects, especially when moving from idea ->outline -> scenes -> chapter prose.
What changed:
- Structured project setup with story type, audience, narrative structure, and writing style
Shipped a new StoryWeave update focused on making the writing workflow feel more connected.
StoryWeave is designed as a project-based writing workspace, not just a one-shot AI text generator. This update improves how context moves across the workflow.
What changed:
- Outline generation can now use the project foundation, including title, genre, and premise.
I shipped v0.3.0 today, focused on making the long-form writing workflow more coherent.
The main improvement is the connection between outline, chapter, and scene generation. Outline chapters can now be synced into the workspace, and scene generation uses chapter-level context so the generated scenes are better aligned with the current chapter goal.
This is part of an ongoing effort to make StoryWeave less like a one-off AI text generator and more like a structured writing workspace for longer stories.
