能力标签

🤖 Agent 🔄 工作流 🐳 Docker 💻 CLI 🔗 REST API 🧬 Embedding 📚 RAG 🧠 Claude ✨ GPT

⚙️

Agent工作流

AI小说生成

基于 Go · 无代码搭建完整 AI 自动化流程

英文名：novelbuilder

⭐ 11 Stars 🍴 1 Forks 💻 Go 📄 GPL-3.0 🏷 AI 8.0分

8.0AI 综合评分

AI小说生成工作流

⬇ 下载源码（GPL） ⚙️ 配置说明 📺 TG 频道

✦ AI Skill Hub 推荐

AI小说生成是 AI Skill Hub 本期精选Agent工作流之一。综合评分 8.0 分，整体质量较高。我们强烈推荐将其纳入你的 AI 工具库，帮助提升工作效率。

📚 深度解析

AI小说生成是一套完整的 AI Agent 自动化工作流方案。随着 AI 能力的不断提升，基于 Agent 的自动化工作流正在成为提升个人和团队效率的核心方式。区别于传统的 RPA 自动化（模拟鼠标键盘操作），AI Agent 工作流通过理解任务意图、动态规划执行路径，能够处理更复杂的非结构化任务。

AI小说生成工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。

在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 8.0 分，是同类 Agent 工作流中的精选推荐。

📋 工具概览

AI小说生成是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。

GitHub Stars

⭐ 11

开发语言

支持平台

Windows / macOS / Linux（跨平台）

维护状态

轻量级项目，按需更新

开源协议

GPL-3.0

AI 综合评分

8.0 分

工具类型

Agent工作流

Forks

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

📌 核心特色

可视化 Agent 工作流编排，无需编写复杂代码
支持多步骤自动化任务链，实现全流程无人值守
与外部 API、数据库和第三方服务无缝集成
内置错误处理与自动重试机制，保障稳定运行
提供可复用的自动化模板，快速在同类场景部署

🎯 主要使用场景

自动化日常重复性工作，将精力集中于创造性任务
构建数据采集 → 处理 → 输出的完整自动化管线
实现跨平台、跨系统的数据流转和业务协同

以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。

安装命令

# 方式一：go install（推荐）
go install github.com/spiritLHLS/novelbuilder@latest

# 方式二：从源码编译
git clone https://github.com/spiritLHLS/novelbuilder
cd novelbuilder
go build -o novelbuilder .

# 方式三：下载预编译二进制
# 访问 Releases 页面下载对应平台二进制文件
# https://github.com/spiritLHLS/novelbuilder/releases

📋 安装步骤说明

访问 GitHub 仓库获取工作流文件
在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
上传工作流文件
按照提示配置必要的环境变量和 API Key
运行测试确认流程正常后投入使用

以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。

常用命令 / 代码示例

# 查看帮助
novelbuilder --help

# 基本运行
novelbuilder [options] <input>

# 详细使用说明请查阅文档
# https://github.com/spiritLHLS/novelbuilder

以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。

配置示例

# novelbuilder 配置说明
# 查看配置选项
novelbuilder --config-example > config.yml

# 常见配置项
# output_dir: ./output
# log_level: info
# workers: 4

# 环境变量（覆盖配置文件）
export NOVELBUILDER_CONFIG="/path/to/config.yml"

📑 README 深度解析真实文档完整度 36/100 含工作流图查看 GitHub 原文 →

以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

NovelBuilder

中文说明

NovelBuilder is an AI long-form fiction workbench with a Vue UI, Go API gateway, Python agent sidecar, optional graph/vector memory, and deployment profiles from SQLite-only local mode to full all-in-one Docker.

Deployment Profiles

Tag	Dockerfile	Shape	Suggested resources	Notes
`latest`, `full`, `YYYYMMDD`	`Dockerfile`	Single container with PostgreSQL, Redis, Qdrant, Neo4j, Python, Go, Vue, Playwright	4 CPU, 8 GB RAM, 20 GB disk	Complete local deployment
`standard`, `YYYYMMDD-standard`	`Dockerfile.standard`	Single container with PostgreSQL, Redis, Python, Go, Vue	2 CPU, 4 GB RAM, 10 GB disk	Installs base Python deps only; graph/vector/browser routes are disabled
`app`, `YYYYMMDD-app`	`Dockerfile.app`	App, sidecar, and Vue only	2 CPU, 2 GB RAM plus external services	Includes graph/vector/browser Python deps for external services and upload automation
`sqlite`	`Dockerfile.sqlite`	Independent minimal image with SQLite and optional services disabled	1 CPU, 2 GB RAM, 5 GB disk	Base Python deps only; intended for single-user local use
`no-neo4j`	`Dockerfile.no-neo4j`	Independent single container with PostgreSQL, Redis, Qdrant, browser automation, Python, Go, Vue	3 CPU, 6 GB RAM, 15 GB disk	Omits Neo4j and graph Python/runtime deps
`no-qdrant`	`Dockerfile.no-qdrant`	Independent single container with PostgreSQL, Redis, Neo4j, browser automation, Python, Go, Vue	3 CPU, 6 GB RAM, 15 GB disk	Omits Qdrant and vector Python/runtime deps
`no-graph-vector`	`Dockerfile.no-graph-vector`	Independent single container with PostgreSQL, Redis, Python, Go, Vue	2 CPU, 4 GB RAM, 10 GB disk	Omits graph/vector/browser runtime deps
`no-redis`	`Dockerfile.no-redis`	Independent single container with PostgreSQL, Python, Go, Vue	2 CPU, 3 GB RAM, 10 GB disk	Omits Redis service and optional graph/vector/browser runtime deps

The release workflow builds full, standard, app, and each variant from its own Dockerfile. Variant Dockerfiles no longer inherit from a same-run base tag.

Build And Size Controls

VERSION=dev UPX_ENABLED=auto ./scripts/build-binaries.sh
TARGETS="linux amd64,windows amd64" ./scripts/build-binaries.sh

Go binaries are built with -trimpath, stripped symbols, and an empty build id. If upx is installed, Linux and Windows binary packages are compressed automatically. Docker builds use Node 24 builder images, npm ci, no pip cache, no Python bytecode writes, and split sidecar requirements (base, graph, vector, browser) per profile. GitHub Actions also run JavaScript actions on Node 24-compatible action versions.

Quick Start

All-in-one full profile:

```bash cp .env.example .env

edit .env and replace ADMIN_PASSWORD, DB_PASSWORD, POSTGRES_PASSWORD, and NEO4J_PASSWORD

docker compose up -d open http://127.0.0.1:8080/setup


Standard profile without graph/vector services:

bash cp .env.example .env

edit .env and replace ADMIN_PASSWORD and DB_PASSWORD

docker compose -f docker-compose.standard.yml up -d


Minimal SQLite profile:

bash docker compose -f docker-compose.sqlite.yml up -d


Source or binary local mode:

Prerequisites for source builds: Go 1.22+, Python 3.11+, Node.js 20.19+.

bash ./scripts/install.sh ./scripts/run-local.sh


Windows:

powershell powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1 powershell -ExecutionPolicy Bypass -File .\scripts\run-local.ps1 ```

Open /setup first. It checks runtime readiness and then the in-app guide walks through model configuration, project creation, references, blueprint generation, and chapter generation.

Configuration

Infrastructure settings are environment variables. Application settings, LLM profiles, prompt presets, and runtime snapshots are stored in the database.

Variable	Default	Notes
`APP_PROFILE`	`full` in Docker, `binary` in local scripts	Displayed in setup diagnostics
`SERVER_HOST`, `SERVER_PORT`, `SERVER_MODE`	`0.0.0.0`, `8080`, `release`	Go gateway listener
`ALLOWED_ORIGINS`	localhost dev and `:8080` origins	Comma-separated CORS allowlist; use your HTTPS origin for public deployments
`TRUSTED_PROXIES`	empty	Comma-separated proxy CIDRs; set only when running behind a trusted reverse proxy
`ADMIN_USERNAME`, `ADMIN_PASSWORD`	`admin`, generated at runtime when unset	Set a strong `ADMIN_PASSWORD`; if omitted, read the temporary password from startup logs
`SESSION_TTL_HOURS`	`24`	Sliding session lifetime
`LOGIN_MAX_ATTEMPTS`	`5`	Failed login attempts before lockout
`LOGIN_WINDOW_SECONDS`	`300`	Counting window for failed logins
`LOGIN_LOCKOUT_SECONDS`	`900`	Lockout duration after too many failures
`DB_DRIVER`	`postgres` in containers, `sqlite` in local scripts	`sqlite`/`sqlite3` or `postgres`
`SQLITE_PATH`	`/data/novelbuilder.db` or `./data/novelbuilder.db`	Used when `DB_DRIVER=sqlite`
`DB_HOST`, `DB_PORT`, `DB_USER`, `DB_PASSWORD`, `DB_NAME`, `DB_SSLMODE`	host/user/name defaults; password required in PostgreSQL Docker profiles	Used when `DB_DRIVER=postgres`
`DB_MAX_OPEN_CONNS`, `DB_MAX_IDLE_CONNS`, `DB_CONN_MAX_LIFETIME_MINUTES`	`25`, `5`, `60`	Go database pool sizing; open/idle values are clamped to at least `20`/`5`, lifetime to at most `60` minutes
`REDIS_ENABLED`, `REDIS_ADDR`, `REDIS_URL`, `REDIS_PASSWORD`, `REDIS_DB`	profile-specific	Go uses `REDIS_ADDR`; Python uses `REDIS_URL`
`SIDECAR_URL`, `SIDECAR_TIMEOUT`	`http://127.0.0.1:8081`, `600`	Go to Python sidecar
`SIDECAR_DB_MIN_CONNS`, `SIDECAR_DB_MAX_CONNS`	`5`, `20`	Python sidecar PostgreSQL pool sizing for legacy DB-backed analysis routes
`NEO4J_URI`, `NEO4J_USER`, `NEO4J_PASSWORD`	profile-specific; password required when Neo4j is enabled	Empty `NEO4J_URI` disables graph services
`QDRANT_URL`	profile-specific	Empty disables vector services
`TASK_WORKERS`, `TASK_MAX_RETRIES`	`4`, `3`	Background task queue
`NB_ACCELERATOR`	`auto`	`auto`, `cpu`, `cuda`, `rocm`, `mps`, or `npu`
`VECTOR_EMBED_CONCURRENCY`	`4`	Python-sidecar embedding concurrency during vector rebuilds

Reference uploads accept .txt, .md, .markdown, .pdf, and .epub files up to 50 MiB. Files are stored under /data/uploads, and the sidecar only reads paths inside that directory.

Authenticated API documentation is available at /api/docs and /api/docs/openapi.json. The docs routes use the same admin session middleware as the main API; CLI callers should pass Authorization: Bearer <token>, while direct browser access can use /api/docs?token=<token>.

🎯 aiskill88 AI 点评 A 级 2026-07-05

创新性的AI小说生成平台