Roadmap
Last updated: May 2026
Scriptri is in active beta. The core workflow is available now: import or create scenes, associate entities with those scenes, write continuity notes, and use the “At This Point” panel to check what is true at a specific moment in the manuscript.
This roadmap is not a fixed release schedule. It separates what is available now from what is planned next and what belongs to longer term product research. Priorities may change as writers test Scriptri on real manuscripts.
Manuscript import and refresh
Scriptri already imports DOCX, Markdown, plain text, JSON, EPUB, and zipped Scrivener projects. Import flows include split options so writers can turn an existing manuscript into Scriptri scenes without starting from a blank project.
Available now
- DOCX, Markdown, plain text, JSON, and EPUB import
- Zipped Scrivener project import
- Split options for headings, separators, chapters, and whole document import
- Scrivener source metadata for imported scenes, including source UUID tracking
- Scrivener refresh: compare a later Scrivener upload against previously imported scenes, then choose which changed or new scenes to bring in
- Automatic local snapshots before high-risk import or delete actions
Planned improvements
- Clearer Scrivener refresh previews, especially for skipped, empty, deleted, or renamed binder items
- Better handling for Scrivener synopsis and document notes
- More import verification with large manuscripts and unusual formatting
- Project-wide review of likely entity mentions that have not been associated with scenes yet
- Future refresh workflows for non-Scrivener sources, such as DOCX and Markdown, if beta users need them
Non-goals: no write-back to Scrivener, no live Scrivener sync, and no silent whole-project auto-tagging.
Continuity review
The current beta already supports the main review loop: continuity notes, continuity flags, before/after scene context, note filtering, and the At This Point panel. The next work is about making long-project review easier.
Available now
- At This Point view for carried-forward context at a selected scene
- Before Scene and After Scene modes for checking prior context or current-scene changes
- Continuity flags with resolution and reopening behavior
- Search and filtering for notes by content, entity, note type, tag, and related context
- Closed notes visible in context and entity history, rather than disappearing from review
- Session memory for common review state, including tab selection, filters, and context expansion
Planned improvements
- Project-wide audit views for open flags, unresolved concerns, and scenes with no continuity notes
- POV-aware filtering, so notes and flags can be checked against what the viewpoint character could plausibly know
- Better handling for notes that are opened and resolved in the same scene
- Tools for reducing context clutter in long manuscripts, such as pinned notes, superseded notes, or condensed review modes
- Safer scene-reordering review, so structural edits are less likely to hide continuity changes
Entity timelines and story memory
Scriptri already shows entity history inside the entity view, including notes grouped by scene. Future timeline work should make that history easier to scan across a full manuscript.
Available now
- Entity records for characters, places, objects, factions, and concepts
- Aliases and full-name fields for entity management
- Entity history showing where an entity appears and which notes are attached to it
- Search inside the entity timeline to find relevant notes faster
- Manual entity association, even when an entity name does not appear directly in the scene text
Planned improvements
- Character timelines showing how knowledge, emotional state, relationships, and physical condition change across scenes
- Thread-based views for following one evolving belief, emotion, relationship, clue, or continuity concern over time
- Lightweight entity facts for stable details that do not belong in scene-state notes
- Relationship arcs between two entities across the manuscript
- Object and location histories, including where an object moved or when a location changed
- Better duplicate-name and alias handling for entities who appear under multiple names
The design principle stays the same: Scriptri should stay tied to scenes and story time. It should not turn into a generic wiki.
Visual continuity tools
Some continuity questions are easier to answer visually. A timeline can show when a subplot appears, when a reveal happens, or where a flag remains open. A location view can show where characters are at a specific point in the story.
- Timeline view: scenes arranged by story order or in-world date, with state-change and flag markers
- Entity-specific timelines for appearances, state changes, and flags
- Reveal and knowledge markers showing when key information enters the story and who has access to it
- Location views for answering “Where is everyone at this point?”
- Map and location continuity, with location data attached to scenes and entity movement tracked over story time
These features need reliable continuity data first. They belong after the core workflow and entity timeline layers feel solid.
Backups, export, and project safety
Scriptri is local-first, so project safety matters. Writers need to know what is stored locally, what can be exported, and how to recover from risky edits.
Available now
- Local-first project storage in the browser
- Scriptri JSON export and import
- Local snapshots before scene delete, entity delete, project delete, restore, and manuscript import
- Privacy-focused app behavior, with manuscript text kept out of analytics
Planned improvements
- Clearer backup browsing and restore controls
- Markdown manuscript export, with scene titles as headings
- Continuity report export
- Open flags report
- Entity timeline or character knowledge report
- Safer import-as-copy behavior with fresh internal IDs for duplicated projects
Cloud backups and accounts
Scriptri does not require an account today. Project data lives in browser storage on the writer’s device. Cloud features may be added later, but they should be opt-in and clearly explained before any manuscript data leaves the device.
- Optional cloud backups, either manual or automatic, with clear controls over what gets backed up
- User accounts for accessing projects across devices
- Restore from cloud backup
- Paid plans for cloud features when the product is ready
- A migration path for current local-beta data into an account-backed store
Manuscripts are sensitive. The local-first path should remain available, and any cloud storage should explain what data is stored, where it is stored, and how the writer can export or remove it.
Help, onboarding, and feedback
Scriptri has a specific workflow. New users need a clear path through import, entity association, continuity notes, and the At This Point panel.
Available now
- A demo project new users can explore
- A landing-page demo video
- Guide pages covering continuity concepts and workflows
- Feedback links in the app during beta
- Privacy and roadmap pages for transparency
Planned improvements
- A help page that explains the core Scriptri workflow step by step
- Task-specific guides for importing a manuscript, refreshing Scrivener, creating entities, writing notes, and using At This Point
- Lightweight note-writing helpers inside the Notes workflow
- Clear documentation for current limitations and edge cases
- Better first-run guidance for writers starting from an existing manuscript
Mobile and accessibility
Desktop remains the primary writing environment, but mobile review matters. Writers may want to check notes, read context, or review flags from a phone or tablet.
Available now
- Initial mobile layout support
- Safe-area handling for mobile browsers
- Contrast and visibility improvements across the app
Planned improvements
- Better mobile review flows for context, notes, entities, and flags
- A mobile-friendly tagging workflow that does not fight the browser’s native text-selection menu
- Keyboard and screen-reader accessibility review
- Touch target and panel-density improvements
Series and shared-world support
Scriptri projects currently work at the manuscript level: one project per book or story. Multi-book continuity support is a longer-term direction for series, trilogies, spin-offs, and shared worlds.
- Multiple manuscripts in one story world, including series, spin-offs, prequels, and novellas
- Shared entity records across related works, with manuscript-specific state notes
- Cross-book continuity, such as what a character knows at the end of book one and carries into book two
- Reader-knowledge tracking across prior books or installments
- Series-level timelines and maps
This work should wait until single-manuscript continuity is stable and validated. It is not part of the current beta.
Future workflow modes
Future direction, not part of the current prose-first beta
Scriptri’s continuity model may eventually support screenwriters, visual storytellers, and tabletop RPG campaign managers. Those workflows involve scenes, sessions, locations, props, NPCs, secrets, unresolved hooks, and story state over time.
These modes should remain separate from the prose manuscript workflow until the core product is validated. Scriptri should not become a screenwriting app, a virtual tabletop, or a generic wiki. The shared center should stay the same: scene-linked continuity, writer control, and clear story state.
Scriptri is in free beta
The core continuity workflow is available now. No account required. Your manuscript stays in your browser. Try it on a real project and send feedback as the roadmap takes shape.