# InkOS: The Open-Source AI Agent That Writes Entire Novels — And Actually Keeps the Plot Straight *An autonomous 10-agent pipeline that drafts, audits, and revises full-length fiction. 2.4k GitHub stars. MIT licensed. No SaaS. No subscriptions.* --- Every AI writing tool I've tried has the same fatal flaw: it forgets. Feed it 20 chapters of a LitRPG novel and watch what happens. The protagonist's sword changes names. A dead character shows up alive three chapters later. Plot hooks planted in chapter 4 never resolve. The prose reads like every other AI-generated text — "intricate", "testament", "pivotal" — over and over. I spent months trying to fix this with prompt engineering. Longer system prompts. Retrieval-augmented generation. Custom chains in LangChain. None of it worked at novel scale. The fundamental problem: a single LLM call cannot hold the state of an entire book in its head. So I built InkOS. ## What InkOS Actually Does InkOS is not a chatbot wrapper. It's a CLI agent — a pipeline of 10 specialized AI agents that autonomously write, audit, and revise novels. Here's the pipeline: **Radar** scans your story bible, author intent, and current focus to understand what should happen next. **Planner** generates a hook agenda — scheduling which plot threads advance and which pay off this chapter. **Composer** selects the minimal context window from truth files so the Writer doesn't hallucinate from stale data. **Architect** builds the story bible and book rules from your creative brief. **Writer** produces the actual prose — with de-AI-ification baked in (fatigue word detection, style fingerprint injection, banned sentence patterns). **Observer** extracts every fact from the draft. **Reflector** validates those facts against canonical truth and outputs Zod-validated JSON deltas. **Normalizer** handles length governance without destroying the chapter. **Auditor** checks the draft across 33 dimensions. **Reviser** auto-fixes anything that fails audit. Every chapter is validated against 7 canonical truth files: world state, character matrix, resources, plot hooks, emotional arcs, subplots, and chapter summaries. These aren't just notes — they're structured JSON with schema validation. When the Reflector updates a truth file, it outputs a surgical delta, not a full rewrite. This is how InkOS stays coherent past chapter 50, past chapter 100. ## The Numbers - **2,400+ GitHub stars** in the first months - **10 specialized AI agents** in the pipeline - **33 audit dimensions** checked per chapter - **7 canonical truth files** maintained across the entire book - **10 English genre profiles** shipped: LitRPG, Progression Fantasy, Isekai, Cultivation, System Apocalypse, Dungeon Core, Romantasy, Sci-Fi, Tower Climber, Cozy Fantasy ## Why This Matters Now The AI writing space in 2026 looks completely different than it did a year ago. OpenClaw dropped, giving us a universal skill standard. Claude Code and compatible agents can now invoke InkOS as an OpenClaw skill — meaning you can say "write me a LitRPG novel" to your coding agent and it orchestrates InkOS behind the scenes. But more importantly: long-form AI writing is finally being taken seriously. Projects like AutoNovel (NousResearch), kimi-writer, and gemini-writer are all attacking the same problem. The difference is InkOS's approach: don't try to make one LLM smarter — make 10 agents collaborate with validated state. ## De-AI-ification: The Feature Nobody Else Has Every genre profile ships with a fatigue word list. For LitRPG: "delve", "tapestry", "testament", "intricate", "pivotal". The Writer agent checks against these lists in real-time. The Auditor catches anything that slips through. And `revise --mode anti-detect` runs a dedicated rewriting pass on existing chapters. Style cloning goes further: `inkos style analyze` extracts a statistical fingerprint from any reference text — sentence length distribution, word frequency, rhythm profiles — and injects it into your book. Every future chapter adopts that voice. The Reviser audits against it. The result: prose that doesn't read like it came from an LLM. ## Getting Started Takes 3 Commands ```bash npm i -g @actalk/inkos inkos book create --title "The Last Delver" --genre litrpg inkos write next ``` That's it. InkOS handles the rest: planning, drafting, auditing, revising. You review when you want to. Export to EPUB when you're ready. Multi-model routing lets you run Writer on Claude, Auditor on GPT-4o, Radar on a local model. Use expensive models where quality matters, cheap ones where it doesn't. ## What's Next v0.6 shipped with structural state management (Zod-validated JSON, SQLite temporal memory, hook governance, length governance). Studio — a web UI for chapter review and editing — is in progress. InkOS is MIT licensed. No telemetry, no SaaS, no subscriptions. Your data stays on your machine. **GitHub:** https://github.com/Narcooo/inkos **npm:** `npm i -g @actalk/inkos` **OpenClaw:** https://clawhub.ai/narcooo/inkos --- *Tags: AI Agent, AI Writing, Novel Writing, Open Source, LitRPG, Creative AI, Multi-Agent System, CLI Tool*