> ## Documentation Index
> Fetch the complete documentation index at: https://ai-novel-writing-assistant.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Auto Director V1/V2

> Choose director version and push method, letting AI continuously plan and write subsequent chapters

The Auto Director turns vague ideas into executable novel projects and continuously pushes world building, characters, volume planning, and chapter production. For long-form creation, you first choose between V1 and V2, then select the run mode for each push.

> [!NOTE]
>
> Short story creation has an independent complete-draft flow and does not go through the Auto Director.

## How to Choose Between V1 and V2

| | Director V1 | Director V2 |
| - | - | - |
| Entry point | Original director and novel workbench, keeping staged creation entries | This book's director console, concentrating reading directory, main text, and materials, and pushing the next segment of creation |
| Suitable for | Continuing existing novels, or preferring the original workbench operations | Starting new books, planning and generating continuously within the authorized scope |
| Tasks and recovery | Uses its own tasks, checkpoints, and recovery flow | Uses its own runs, stage results, and save progress |
| Default choice | Historical novels keep their original version | When V2 is available, new books default to V2 |

The start page lets you choose an available director version. For existing novels, you must first end the current creation, then switch in the book settings; saved main text and history are retained. **Switching versions only saves the selection; it does not automatically start generation, nor does it restore another version's old tasks.**

To temporarily disable V2, explicitly set `DIRECTOR_NEXT_ENABLED=false`.

## V2 Run Modes: Full Auto and Stage-by-Stage Confirmation

The flowchart below shows the core run chain of the V2 this-book director console: after starting a book, choose the push method and authorization scope, then enter a continuous generation loop; it stops only when the scope is complete, a pause reason is encountered, or the user intervenes.

```mermaid theme={null}
flowchart TD
    A[Start book and choose<br/>director version] --> B{Choose push method<br/>and authorization scope}
    B -->|Full auto push| C[Continuously generate planning,<br/>main text, and saves]
    B -->|Stage-by-stage confirmation| D[Save stage results<br/>and wait for review]
    D --> E[User confirms,<br/>then continue]
    C --> F{Encountered<br/>pause reason?}
    E --> F
    F -->|Yes| G[Pause and record<br/>checkpoint]
    F -->|No| H{Current scope<br/>complete?}
    H -->|No| C
    H -->|Yes| I[Stop and wait<br/>for next authorization]
    G --> J[User resolves reason,<br/>resume from checkpoint]
    J --> C
```

| Creation method | How AI pushes | What you need to do |
| - | - | - |
| **Full auto push** | Within the current authorized scope, fill in required planning, write main text, check and save; ordinary stage results auto-continue | First choose direction and scope; handle explicit pause items when encountered, then continue from the book's director console |
| **Stage-by-stage confirmation (semi-auto)** | Save results at stages needing confirmation, wait for your review before continuing; main text is confirmed at batch end | Open the current stage result, review, then click confirm; no need to manually trigger the whole chain chapter by chapter |

The current mode is shown next to the book title and at the top of the director console; subsequent main text batches follow the selected mode.

## Why Full Auto May Still Stop

Full auto continues executing within your authorized scope; **after the scope is complete, you must choose the next segment**. For example, if you submit Chapters 1 to 3, it will not arbitrarily write Chapter 4 after completion.

The system also pauses when encountering the following:

* Model unavailable or quota exhausted
* Needs re-planning
* Single-chapter usage protection triggered
* Data integrity issue

Ordinary local quality issues are recorded as chapter reminders by default and the system continues; if the "quality priority" strategy is chosen, it may wait for manual handling after main text is saved.

## Director Push Flow

The step-through widget below shows the real stage order from "confirm direction" to "chapter execution". In the Auto Director, the user's most critical creative choice is confirming the direction; after confirmation, the system writes subsequent steps into the task queue and continues pushing.

**Run mode:**

Full auto push

Stage-by-stage confirmation

Reset

/

Previous

Next

### Flow Description

| Stage | Description | Needs confirmation? |
| - | - | - |
| Idea alignment | System understands input, genre preference, target chapter count | No |
| Project positioning | Forms book-level positioning, selling points, and target readers | No |
| Direction candidate batch | Generates optional start-book directions | Yes |
| Title candidate group | Generates titles for the selected direction | Yes |
| Create novel | Turns confirmed direction into a real project | No |
| Story macro | Generates long-term conflict and push cycle for the whole book | Depends on strategy |
| Book contract | Writes target readers, selling points, promises, and hard constraints | Depends on strategy |
| World building | Generates this book's world skeleton, rules, and factions | Depends on strategy |
| Character generation | Generates character candidates and lineup draft | Yes (stops if quality is not acceptable) |
| Apply character lineup | Writes approved characters into formal assets | Depends on strategy |
| Volume strategy | Generates volume strategy, goals, and push route | Yes |
| Volume skeleton | Generates volume list and tasks per volume | Depends on strategy |
| Beat board | Breaks volume planning into executable beat nodes | Depends on strategy |
| Chapter list | Generates chapter titles, order, and basic goals | Depends on strategy |
| Chapter sync | Syncs task data to chapter records | Depends on strategy |
| Chapter refinement | Generates chapter brief and execution resources | Depends on strategy |
| Chapter batch ready | Can begin writing this batch of chapters | Yes |
| Chapter execution | Generates main text, review, repair, and status backfill | Depends on strategy |

> [!TIP]
>
> Users often simplify the flow as "direction, world, characters, chapter breakdown, execution", but the real backend covers at least 17 stages. Stages can be paused, resumed, and retried between one another.

## Run Modes and Applicable Scope

| Mode | Auto runs until | Suitable for |
| - | - | - |
| Prepare to ready for writing (recommended for beginners) | After confirming the plan, auto-completes planning, characters, volumes, and chapter tasks, stopping at ready-for-writing state | First-time book starters, those who want to review whether the plan is solid first |
| Full book auto-completion | After confirming the plan, continuously pushes planning, writing, review, and repair | Those who want to go from plan directly to novel output |
| Execute by scope | Only auto-executes the first N chapters or Volume 1, etc. | Those who want to validate a segment first, then expand the scope |
| Quality repair toggle (overlay) | After chapter main text is completed, enters AI detection removal, review, and fixable issue handling | Those who want a more complete automatic closed loop |

### What Happens After Interruption

**Full book auto-completion** stops **actively** and waits for user handling when encountering model unavailability, quota exhaustion, consecutive repair failures, requests for re-planning, or structural data issues, rather than retrying infinitely.

The diagram below shows the complete pause-to-recovery handling flow.

```mermaid theme={null}
flowchart TD
    R[Running] -->|Model unavailable, quota exhausted<br/>needs re-planning, consecutive repair failures<br/>structural data issue| P[Paused]
    R -->|Authorized scope complete| S([Stopped])
    P -->|View Director Follow-up and Run History| U{User troubleshoots}
    U -->|External cause| M[Replenish quota or switch model]
    U -->|Awaiting confirmation pause| K[Review and continue]
    U -->|Local issue| Q[Accept quality debt]
    M --> C[Resume from checkpoint]
    K --> C
    Q --> C
    C --> R
```

Handling steps:

1. Open Director Follow-up and check the pause reason
2. Open Run History and confirm the latest failed task and error message
3. Eliminate external causes (replenish quota, switch model, fix network)
4. Click **Continue Auto Director** (继续自动导演) in Director Follow-up to resume from the original checkpoint

Do not directly exit director mode or delete the project.

## Recovery and Re-Planning

When encountering a pause, judge in this order:

1. Is it only waiting to select a candidate, character, or volume plan?
2. Is there a retryable background task?
3. Is there already usable chapter content?
4. Is local repair needed or should quality debt be accepted?
5. Is re-planning explicitly required?

Only stop the global chain for explicit re-planning, irrecoverable generation failure, data integrity risk, or system security issues. Local quality debt does not equal global failure.

> [!TIP]
>
> For complete descriptions of pause reasons, continue entries, and takeover actions, see [Director Follow-up](https://ai-novel-writing-assistant.mintlify.site/en/features/director-follow-up.md); for stage-by-stage symptom and recovery entry matching, see [Recovery by Phase](https://ai-novel-writing-assistant.mintlify.site/en/guides/recovery-by-phase.md).

## Frequently Asked Questions

> [accordion] Can V1 and V2 be used on the same novel?
>
> You cannot run both director versions simultaneously. Before switching, you must first end the current creation; saved main text and history are retained.

> [accordion] Is stage-by-stage confirmation troublesome?
>
> No. The system only stops at key nodes, for example direction candidates, character confirmation, volume strategy, and chapter batch ready. You do not need to confirm chapter by chapter manually.

> [accordion] Why does it sometimes freeze?
>
> First check the pause reason in Director Follow-up, then check the background status in Run History. In many cases it is simply waiting for approval, not a failure.

> [accordion] Can I change the model midway?
>
> Yes. After correcting or switching the model in system settings, return to Director Follow-up and continue. Saved main text will not be regenerated.

> [accordion] Can the run mode be changed at any time?
>
> You can adjust it in Director Follow-up's **Continue Auto Director** (继续自动导演) or takeover actions; switching does not lose completed stage products.

> [card] [Novels & Starting a Book](https://ai-novel-writing-assistant.mintlify.site/en/features/novels.md)
>
> Create a project and choose the initial direction

> [card] [Director Follow-up](https://ai-novel-writing-assistant.mintlify.site/en/features/director-follow-up.md)
>
> View pause reasons, continue, or take over the Auto Director

> [card] [First Novel Walkthrough](https://ai-novel-writing-assistant.mintlify.site/en/guides/first-novel-walkthrough.md)
>
> Follow a complete case from idea to completed volume

> [card] [Production Pipeline](https://ai-novel-writing-assistant.mintlify.site/en/guides/production-pipeline.md)
>
> Understand what each layer of the Auto Director does


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.