Authorization notice. DSH Agent RP is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA fiction writer with an ongoing multi-character story who needs consistent outlines and private knowledge for each character.
The problemLong stories lose track of foreshadowing, public history, and who knows what, chapter after chapter.
The outcomeA story project with an editable outline and per-character knowledge, where the story engine writes each passage and records what happened afterward.
What you need first
- Node.js 22.19+ or 24+
- pnpm 11 (or `npm install --global pnpm@11` to install it)
- A working DSH setup (Windows, macOS, or Linux installer path, or DSH Desktop with the limits the README describes)
- Character cards (PNG, JSON, or CHARX) and any World Info or preset files you are allowed to use
Steps
- Install and start Agent RP, then open a session with 开始游玩.
- Enable 故事工程 and create a story project.
- Edit the outline, foreshadowing list, public history, and character private knowledge.
- Write a passage and let the research, character, director, section, and editor workers run before the final reply.
- Review the events the story engine saved back to the project, then continue to the next passage.
Prompt for your agent
In the repo hewzhew/dsh-agent-rp, read docs/story-engine.md and set up a story project following it for <story-title>. Report the outline sections created and confirm that character private knowledge is kept separate from public history. Verify that the saved events match the final passage.
Caveat. The README says multi-character story engine support exists, but traditional group chat UI and multiple parallel top-level character agents are not finished yet.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page