MoTai.
More structure. More room to create.
Earlier MoTai interface with fictional content; the current repository has a revised workspace.
- 01
Problem
How can AI support a long story without losing its characters, context or the writer’s control?
- 02
Context & constraints
Manuscripts stay local. AI access depends on a configured runtime and provider; generated content needs author review before it becomes part of a story.
- 03
My contribution
I started MoTai with a friend and developed AI-assisted writing workflows, connecting structured story context to model APIs and keeping the author in control of accepted text.
- 04
Approach & implementation
Story materials and chapter context feed LLM-assisted planning and writing. The current repository documents draft review before writing, local storage, exports and backups, with AI credentials managed by the local runtime.
- Local manuscript storage
- LLM-assisted drafting
- Author review before writing
- 05
Outcomes & evidence
A desktop prototype and source code are available. The current README describes planning, chapter writing and review before accepting generated material. Local beta work is ongoing; no user adoption or productivity gain is claimed.
- 06
Limitations
Local beta checks remain in progress. Model output still needs review, and earlier interface captures do not represent every current feature. No production reliability or paid adoption is evidenced here.
- 07
Future work
Complete the documented local beta checks and evaluate continuity and author review with representative writing tasks.
Interface walkthrough
Stack
Electron · JavaScript · Local JSON · AI APIs
Evidence & source
The linked README describes the current workflow and links to beta progress. The gallery records an earlier interface using fictional content, rather than a new acceptance test of the latest release.
Read project documentation ↗