Getting started
NovelGraph requires Node.js 22.13 or newer. This is the first Node 22 release where the built-in SQLite module is enabled without an experimental flag. Manuscripts, credentials, revisions, and story state remain in the project directory on your machine.
Launch the public alpha
Section titled “Launch the public alpha”The 0.5.0 npm records have not been published. Run the verified source build until the release gate clears:
git clone https://github.com/CSandbatch/novelgraph.gitcd novelgraphcorepack pnpm install --frozen-lockfilecorepack pnpm -r buildnode packages/cli/dist/index.js studioStudio binds to 127.0.0.1, creates .novelgraph/studio.sqlite, and opens the local workbench. Use --no-open when running without a desktop browser. Binding to another host is an explicit, security-sensitive choice.
Once npm canary verification and promotion are complete, npx @actalk/novelgraph studio will replace the source-build sequence. The documentation will not mark that command available before the registry does.
Complete the first loop
Section titled “Complete the first loop”- Create a series and book in New project.
- Select the Mystery pack and seed its fairness ledger.
- Draft the opening in Manuscript; each save creates a revision.
- Inspect characters, clues, and obligations in Story graph.
- Start a budgeted run in DAG control.
- Resolve findings in Review center.
- Export only after Publication gate reports ready.
Provider configuration
Section titled “Provider configuration”Set provider credentials in a project .env or the existing NovelGraph global configuration. Never commit .env files. The public demo makes no provider calls and accepts no credentials.
NOVELGRAPH_LLM_PROVIDER=openaiNOVELGRAPH_LLM_BASE_URL=https://api.openai.com/v1NOVELGRAPH_LLM_API_KEY=replace-locallyNOVELGRAPH_LLM_MODEL=your-modelRun novelgraph doctor when provider setup fails. It reports connectivity and configuration errors without printing secrets.