An AI novelist that actually remembers chapter 3

What it does Goink is a cross-platform desktop app (Go + Wails, React frontend) for writing long-form fiction with an LLM agent. Instead of a chat that forgets everything, it keeps structured state: character profiles, relationships as a directed graph, foreshadowing with target-recovery chapters, story arcs, a location map, and even what the reader currently knows. The agent queries and updates this state itself via 31 function-calling tools in a self-built ReAct loop.

The interesting bit After finishing a chapter, the system forces the agent into maintenance mode — checking character changes, overdue foreshadowing, arc progress — and an optional reviewer sub-agent re-reads the chapter against the state to catch inconsistencies. There’s also local semantic search (BGE model via ONNX, sqlite-vec) so “that pendant scene” is findable by meaning, fully offline.

Key highlights

• Every edit goes through a Diff preview you approve before it’s written; all changes auto-committed to built-in Git for rollback
• Skill system: writing methodologies as .md files, three override layers (novel > user > builtin) with hot reload, plus a style-distillation feature that turns a sample passage into an imitative skill
• Volumes and chapters are first-class structures with drag-and-drop reordering
• File access sandboxed to a regex whitelist of legitimate paths, with path-traversal protection
• Ships as a single <60MB installer — no Python, Node, database, or GPU required

Caveats

• Requires an external LLM API key (DeepSeek, GLM, MiMo templates, OpenAI-compatible); the semantic model runs locally but generation does not
• Windows builds are unsigned, so SmartScreen will complain
• AGPL v3, which matters if you’re thinking of embedding it in anything proprietary

Verdict Worth a look if you write (or want to write) long fiction and are tired of babysitting an LLM’s memory. If you just want a chatbot to draft a short story, it’s more machinery than you need.