ZenStory CLI
The zenstory command and skill let Claude Code and Codex read and edit chapters, outlines and characters in a ZenStory project.
- 96 ★ on the repository
- Last commit
Extended access
Why this level
- With the `write` scope the agent creates, overwrites and deletes project files in a cloud account.
- The API key opens every project of the account and must not be pasted into an agent chat.
Install
- Works in
Manual install
npx zenstory skill installFrom the Connect external agents section. For Codex add `--target codex`. The API key is created in Settings, Agent.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- With the `write` scope the agent creates, overwrites and deletes project files in a cloud account.
- The API key opens every project of the account and must not be pasted into an agent chat.
This is third-party code. Review the repository files before installing.
What it does
ZenStory is a browser workspace for novels, short stories and short-drama scripts. A project keeps most material as files: outlines, chapters, character sheets, world notes and snippets. For external agents the repository ships the `zenstory` CLI and a standard Agent Skills package. The agent gets project context, searches files, creates and updates chapters, moves files between folders and rolls versions back. Every command has `--json` output for scripts. The API key is created in ZenStory settings, and writing to files is enabled by a separate `write` scope.
Who it is for. Web-novel authors and screenwriters who keep a project in ZenStory and want their own agent to write chapters.
Good fit when
- Claude Code should continue a chapter and first load context: characters, world and earlier chapters.
- A draft has to be saved back into the project without hand-copying text from the terminal.
- You need to find in which chapter a specific character appears.
- An agent edit went wrong and a file must be rolled back to an earlier version.
Not a fit when
- The project lives in Word or Google Docs: the CLI works only with the ZenStory API.
- You need fully offline work without an account: commands do not run without an API key.
- You want to write only inside the browser window with the built-in agents.
Example request
Use zenstory to load the project context, read the outline of chapter three and write a draft that respects the heroine character sheet.Limitations
Node.js 20 or newer and a ZenStory API key (starting with `eg_`, created in Settings, Agent section) are required. Without the `write` scope the agent can only read. The `projects delete` and `files delete` commands ask for the `--yes` flag. The product interface and texts target Chinese web fiction first. The workspace itself is licensed AGPL-3.0, and the hosted version runs at app.zenstory.ai. Request limits are set by the server: exit code 5 means the rate was exceeded.
How to disable. Remove the skill from the agent directory, revoke the key in ZenStory settings and run `zenstory logout`. Remove the global package with `npm uninstall -g zenstory`.
FAQ
How do I connect zenstory to Claude Code?
Create an API key in Settings, Agent section, and run `npx zenstory skill install`. For Codex and OpenClaw add `--target codex` or `--target openclaw`.
Can the agent delete my chapters?
Only with the `write` scope and the `--yes` flag on delete commands. File versions are kept, and `files rollback` restores an earlier one.
How do I pass the key without shell history?
Through stdin: `printf %s "$KEY" | zenstory login --key -`. Avoid putting the key itself in the `--key` argument.
Does it work with a self-hosted server?
Yes, `zenstory login --api-base <address>/api/v1` points the commands at your own ZenStory installation.
Where is project data stored?
In your ZenStory account at app.zenstory.ai or on your own server if you deployed the workspace yourself. The CLI keeps no project locally.
Discussion
No questions or reviews yet.
Related
CLI toolsA set of 13 skills for writing web fiction inside a coding agent: rank scanning, hit deconstruction, outline and prose, AI-flavor cleanup, cover art
24 skills for fiction in Markdown, from premise to print, and a story command that catches plot contradictions before readers do
A plugin for novels and serial fiction: a muse agent leads from idea to draft, while writer, critic, editor and canon-check agents each handle one job
A novel-writing skill with nine agents: setting, volume and chapter plans, prose, a machine-style check and an archive with character memory
A Codex skill that takes a novel from idea to finished book, keeping plan, chapters and continuity in Markdown files.
A skill helps Codex plan Chinese web fiction, revise scenes and check character actions against earlier chapters
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| ZenStory (this card) | no | 96 | |
| Oh Story | no | 8,526 | a skill pack for writing inside the agent; zenstory connects the agent to a ready-made workspace and its projects |
| Webnovel Writer | no | 7,939 | a local novel-writing pipeline; zenstory works with ZenStory projects over an API |
README in short
The main repository is the whole workspace: a web client, a Python server and a set of writing agents. The `apps/cli` folder with the dependency-free `zenstory` package is meant for external agents.