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 long-time SillyTavern user who has a saved JSONL chat log and wants to continue that story in DSH.
The problemYears of chat history stay trapped in SillyTavern files and cannot be reused in a new runtime.
The outcomeA new character dialogue in DSH that holds the migrated chat, while the source file and source session stay unchanged.
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 using the installer path for your operating system from the README.
- Open a character session in DSH.
- Attach your SillyTavern JSONL file to the session.
- In the migration panel, pick a character card already in the resource library, or import a new PNG, JSON, or CHARX card.
- Confirm the new character dialogue opens and check that the migrated messages appear.
Prompt for your agent
In the repo hewzhew/dsh-agent-rp, use the migration panel described in the README to migrate <path-to-chat.jsonl> with the character card <path-to-card>. Report the new session name and the message count. Verify that the source JSONL file and the original session are unchanged.
Caveat. The README says migration creates a new character dialogue and does not modify the source file, but it does not describe how much of the original formatting is preserved, so spot-check the result.
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