Share tools while keeping each book’s facts separate
Oh Story organises long fiction under a book directory with its own 正文/, 设定/, 大纲/ and 追踪/. Choose your names, but reads and writes must address the same book. Discussion or planning alone does not require generating manuscript and tracking directories.
| Keep separate | Reason |
|---|---|
| Draft and outline | Chapter eight can belong to two different stories. |
| Cast, rules and knowledge | Another book’s experience is not a fact here. |
| Style and progress | A neighbouring folder cannot supply missing book-local style or state. |
Installed skills provide methods rather than manuscript storage. Do not initialise a new book by copying another book’s tracking: its promises, objects and clues would come too. For existing manuscripts, see import and continuation.
Check the selector and the actual task path
Deployed discovery code reads the first line of workspace-root .active-book and tries the declared target, with discovery when no declaration is adopted. Hosts differ in their treatment of nonexistent paths; check the actual directory rather than assuming an incorrect declaration is repaired automatically. Finding the first book is not an author choice; do not rely on an unset default for switching.
For example, 我的书库/ contains existing 灯塔往返/ and 周末修理台/ directories. To select the latter, the root selector can contain the relative directory 周末修理台 on its first line. This indicates a directory, not a chapter, list of books or access isolation. Check the host’s deployment and real path as well.
Parallel sessions cannot keep changing a shared default while assuming each retains its old binding. Fix each task’s root and materials; use separate workspaces when defaults must be independent. A switch does not automatically erase story facts from an earlier conversation.
Complete example: switching from lighthouse to repair shop
This original workspace arrangement is an illustration, not an executed writing project. Two existing manuscripts have different cutoffs:
| Book | Current fact and scope |
|---|---|
| 灯塔往返 / Lighthouse Journeys | Eight chapters; Gu Lan obtained docking permission, cargo not delivered. No continuation now. |
| 周末修理台 / Weekend Repair Table | Three chapters; Ning Yue received a trial-room key, reading stand unrepaired. Plan chapter four only. |
Record the old task’s cutoff and keep its files. Check that the current workspace contains 周末修理台/, target that root and load its settings, progress and relevant outline. A recent “permission obtained” in the old chat cannot give Ning a harbour permit.
Use this complete task:
Work only in
我的书库/周末修理台/. Through chapter three, Ning Yue has a trial-room key and the stand is unrepaired. Plan only chapter four: check room-use arrangements and ask the owner about replacing the base. Follow this book’s existing style and settings; preserve the owner’s currently ungranted approval. Draft no prose and change no files in Lighthouse Journeys. If the open book differs, identify the path mismatch first.
Check delivery: chapter-four outline belongs to this book, while prose still ends at three. Replacement approval is a planned event, not accomplished tracking. The lighthouse book remains at eight with cargo undelivered. This establishes target and scope without promising that AI cannot make mistakes.
If books were mixed, locate the actual changes
Keep the current diff and locate affected prose, settings or tracking, then compare trusted drafts and actual chapters for this book. Replacing another book’s names is insufficient if abilities, time, promises and possessions came with them.
After correcting prose, handle tracking and downstream changes from this book’s actual events. Oh Story has a tracking commit workflow; do not edit a derived state card to hide contamination. Check the other book separately if it also changed rather than deleting a manuscript to clear context.
A first task after switching can be a read-only diagnosis of name, cutoff and next artifact. Request chapter and stopping point explicitly before drafting. See batch chapter writing for a different task: this page addresses boundaries between books.
FAQ
Do two chat windows guarantee separation?
No. Check actual read/write directories and whether they share a selector. Fix name, root, cutoff and artifact in each task.
Must every book reinstall the skills?
Do not put manuscripts inside skill directories. Follow the tool’s installation and project deployment while keeping book materials separate and checking real paths at each switch.
Do it with the skill
Use /story-long-write, or $story-long-write in Codex, only for the named book and artifact with its root, cutoff and materials. Check the target first; specify chapter and stopping point for prose instead of automatically continuing the previous book.
Read the method: Book-local files and tracking · Actual active-book and fallback discovery · Book-root discovery in the host adapter · Book-local style and factual boundaries