Narcooo/inkos
Agent system for long-form story creation — novels, screenplays, interactive film/games, IP franchises and multilingual translation — shipped as an npm package (@actalk/inkos) under AGPL.
What is the idea?
An agent pipeline that holds a long story together — plot state, character continuity, four-transformation-style world rules — and drives it from outline to chapter after chapter, with screenplay, interactive-game and translation modes on the same spine. It ships as an npm package (@actalk/inkos) you configure with your own model key.
Who would use it, and what do they get?
The ordinary person here is a working web-novel author, and the finished thing they walk away with is a chapter they can publish today — this qualifies under the one allowed exception (AI producing a deliverable a human uses), not as developer infrastructure.
Why would anyone bother?
A web-novel writer paid by the chapter, who is not a Node developer. What they walk away with is a manuscript — chapters at the length they asked for, with the same character still recognisably the same character 200,000 words later.
What is missing today?
Only geeks can use it, and the output still reads like filler. The person who wants this is a web-novel writer, not a Node developer: they must install Node 20+, hand-edit a .env, and pick a model provider before the first sentence — and the ones who get through report chapters that lose word-count control and plots that converge on the same opening.
What makes this one different?
Do not ship a pipeline; ship a manuscript. One-click desktop install with a model key pre-wired, and the product's promise is narrowed to the single job the issue tracker proves is broken: keep a 200k-character story consistent and keep each chapter at the length the writer asked for. Sell the divergence, not the volume — a 'sameness check' that flags when chapter one is drifting into the same mine-shaft opening as everyone else's. Cold start (Chinese): the inkos issue tracker itself plus 番茄小说作者交流 and 龙的天空 forums, where writers post exactly these complaints; Cold start (English): r/WritingWithAI and r/HFY, search 'lost the plot chapter'.
What is the sharpest thing about it?
Keeping plot state and character continuity across hundreds of chapters was not attemptable while context windows were short. The agent-plus-external-state pattern on top of cheap long-context reading is what makes a 300-chapter run something you can even try to hold together.
What could kill it?
The sameness complaint is not a bug you can patch — it is what a language model does when you ask it for 300 chapters, and every competitor will hit the same wall. Meanwhile Chinese platforms (番茄/起点) are shipping their own authoring assistants to the writers who already live there, with the distribution and the payout attached. A tool that makes bad novels faster has no buyer.
Who pays, and for what?
A web-novel writer paid by the chapter — the readable-output-per-hour number is literally their wage. Monthly subscription priced against one extra chapter a day.
What is the main risk?
The demand is real but the quality ceiling belongs to the model, not to you; if frontier models close the long-form consistency gap natively, the orchestration layer evaporates.
What did real people actually say?
Verbatim from the public sources linked above, not paraphrased: “大家没有发现这个问题吗？多开几本同类型的小说，比如：玄幻，你会发现主角开局要么下坑要么下矿要么捡垃圾，接着有个对他怀恨在心的npc张虎或者其他，再来一个对他好的老头吧啦吧啦，说实话去除人名，这些故事几乎一样。发散性严重不足。” — github-issue “AI味道还是有点，感觉写出来就像流水账，小说第一章字数正常，后面的字数无法控制” — github-issue “一开始我用很详细的和它说建立书， 他要啥给啥，然后总是建立失败， 说参数不对，引号问题，但是他又解决不了，就一直卡在这里。” — github-issue
How much work is it?
about two months of work
Where does the evidence come from?
https://github.com/Narcooo/inkos
← yizhiyanhua-ai/fireworks-tech-graph · nexu-io/open-design →