Settings and project data

This section changes only the device. It never enters project data, an export pack, or account sync:

• Interface and alerts: interface language (简体中文 / English—buttons and prompts only, not your work’s language or the language the agent replies in), where the app goes on startup (lobby / new project / last project, falling back to the lobby), interface zoom (⌘= / ⌘- / ⌘0), and two toast switches (agent task finished or failed, background maintenance outcome). Turning a toast off only stops the pop-up; the record and the bell’s unread count remain.
• Editor: entity highlighting in the draft, script font (Song / Hei), script size (14 / 16 / 18), smart punctuation (straight quotes fold to Chinese curly quotes, repeated minuses into a dash; titles and structure blocks untouched), and typewriter scrolling (the caret line stays near 40% of the viewport height).
• Privacy and about: where manuscripts are hosted, the AI data note, the current version, and the legal documents.

“Default location for new projects” is a folder picker on desktop; in the web app storage belongs to the browser and no path is exposed.

This section belongs to the work and travels with it. Basics holds the project name and cover (local upload, JPG / PNG / WebP up to 10 MB, compressed into the project and shown on the lobby card); renaming updates the lobby and the top bar, while the folder name on disk stays as it was.

The creative baseline is saved into the project’s managed DESIGN sections, which the agent reads but never edits: project language (new writing and automatic maintenance default to it; switching does not translate what exists, nor change the interface language), positioning, genre, target audience and content scale, core themes, worldview principles, and visual expression. Visual expression is the odd one out: it is the project’s default basis for image generation, kept out of DESIGN and out of the long conversation prefix.

Writing style is the nine-dimension template (narrative distance, time presentation, prose rhythm, dialogue style, narrative diction, scene description, character presentation, emotional expression, imagery techniques). Each dimension pairs what to do with what to avoid, can be disabled, and takes its own extra constraint. Loading a built-in template copies it into this project’s own snapshot, so later edits elsewhere do not reach it; and you can save the current setup as a personal template.

Automatic maintenance decides whether the background runs once you stop, via four separate switches: maintain this chapter’s profiles after a continuation, maintain character profiles when a chapter is created, continuity check after a chapter update, and scene / scene setting summaries during a quiet period. The running condition is fixed: it waits its turn when no foreground task is active and never runs alongside a agent session.

The manual area is independent of those switches and can run now: update all profiles from the text, check this chapter, check every chapter, generate the whole overview, view the continuity report. A check reports hard conflicts and suspects; it never edits the draft. Intent and summaries you wrote by hand are not overwritten. With no chapters yet, these actions tell you to build the structure first.

• Version snapshots: archive by hand, or restore an earlier state. Writes by AI and a two-minute pause both archive automatically; automatic snapshots keep the latest 12 per source, manual ones stay forever. Restoring archives the current content first, so you can come back.
• Delivery export: Word (.docx), PDF (through the system print dialog), or Quilldown plain text (.txt); whole script or one chapter, note lines optional.
• Project backup: the full project as a .quill.json pack—draft, structure, records and bundled assets—for machine moves and independent restores; importing creates a new local copy.
• Archive box: deleted scenes and scene settings land here instead of vanishing. Restoring appends them to the end of their original chapter; each project keeps the most recent 60 items, and permanent deletion is final.
• Danger zone: move to trash (web: the lobby trash, restorable or permanently cleared), remove the record only (desktop: it leaves the lobby list, the folder on disk is untouched), or delete the current project, which asks you to type the name.

This is where account facts live: available and reserved credits, agent task records, the credit ledger, and text and image call summaries. A cloud AI task first drains the sync queue and checks the project version, and the ledger and notifications update with the result.

• Devices and security: desktop keeps its refresh token in the system credential store and restores sign-in on restart; the browser uses an HttpOnly cookie. Other sessions are listed here and can be revoked one at a time.
• Friends can enter your referral code at sign-up. Eligible rewards are granted by the server after their first confirmed payment; the related reward is recovered on refund.
• Deleting the account starts a cooling-off period you can withdraw from. While it is processing you cannot top up or start new agent tasks, though orders, ledger and task history stay readable. A completed deletion clears that account’s notification records.

The Global edition uses Creem and the CN desktop website uses Alipay. Confirm the product and price after sign-in. Subscriptions last 30 days and renew manually, without automatic charges. Billing and credits.

• A preference that fails to save does not report success: the in-memory value stays as it was and the next change warns again. Corrupt stored values fall back to defaults.
• Leaving a settings page with unsaved changes asks once: keep editing or discard. Nothing is dropped silently.
• If a DESIGN section changed outside the project, the settings page refuses to write back and asks you to reopen the project rather than overwriting your own text.
• Credit figures in settings come from the server ledger; offline you are looking at the last read.