Upload 888 files

.gitattributes

@@ -33,3 +33,103 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.zst filter=lfs diff=lfs merge=lfs -text
 *tfevents* filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/bedroom[[:space:]]clean.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/bedroom[[:space:]]cyberpunk.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/bedroom[[:space:]]red.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/bedroom[[:space:]]tatami.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/cityscape[[:space:]]medieval[[:space:]]market.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/cityscape[[:space:]]medieval[[:space:]]night.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/cityscape[[:space:]]postapoc.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/forest[[:space:]]treehouse[[:space:]]fireworks[[:space:]]air[[:space:]]baloons[[:space:]](by[[:space:]]kallmeflocc).jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/japan[[:space:]]classroom[[:space:]]side.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/japan[[:space:]]classroom.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/japan[[:space:]]path[[:space:]]cherry[[:space:]]blossom.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/japan[[:space:]]university.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/landscape[[:space:]]autumn[[:space:]]great[[:space:]]tree.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/landscape[[:space:]]beach[[:space:]]day.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/landscape[[:space:]]beach[[:space:]]night.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/landscape[[:space:]]mountain[[:space:]]lake.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/landscape[[:space:]]postapoc.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/landscape[[:space:]]winter[[:space:]]lake[[:space:]]house.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/royal.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/backgrounds/tavern[[:space:]]day.jpg filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/default_Seraphina.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/admiration.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/amusement.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/anger.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/annoyance.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/approval.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/caring.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/confusion.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/curiosity.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/desire.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/disappointment.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/disapproval.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/disgust.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/embarrassment.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/excitement.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/fear.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/gratitude.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/grief.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/joy.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/love.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/nervousness.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/neutral.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/optimism.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/pride.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/realization.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/relief.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/remorse.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/sadness.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/default/content/Seraphina/surprise.png filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/st-launcher.ico filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/st.ico filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/fa-brands-400.ttf filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/fa-brands-400.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/fa-solid-900.ttf filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/fa-solid-900.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Black.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Black.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-BlackItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-BlackItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Bold.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Bold.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-BoldItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-BoldItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraBold.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraBold.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraBoldItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraBoldItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraLight.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraLight.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraLightItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ExtraLightItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Italic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Italic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Light.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Light.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-LightItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-LightItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Medium.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Medium.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-MediumItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-MediumItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Regular.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Regular.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-SemiBold.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-SemiBold.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-SemiBoldItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-SemiBoldItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Thin.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-Thin.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ThinItalic.woff filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSans/NotoSans-ThinItalic.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-100.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-200.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-300.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-500.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-600.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-700.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-800.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-900.woff2 filter=lfs diff=lfs merge=lfs -text
+jiuguan2025cc/public/webfonts/NotoSansMono/noto-sans-mono-v30-regular.woff2 filter=lfs diff=lfs merge=lfs -text

jiuguan2025cc/.dockerignore

@@ -0,0 +1,15 @@
+.git
+.github
+.vscode
+node_modules
+npm-debug.log
+readme*
+Start.bat
+/dist
+/backups
+cloudflared.exe
+access.log
+/data
+/cache
+.DS_Store
+/public/scripts/extensions/third-party

jiuguan2025cc/.editorconfig

@@ -0,0 +1,14 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{js,conf,json,css,less,html}]
+charset = utf-8
+indent_style = space
+indent_size = 4
+
+[*.md]
+trim_trailing_whitespace = false

jiuguan2025cc/.eslintrc.cjs

@@ -0,0 +1,102 @@
+module.exports = {
+    root: true,
+    extends: [
+        'eslint:recommended',
+    ],
+    env: {
+        es6: true,
+    },
+    parserOptions: {
+        ecmaVersion: 'latest',
+    },
+    overrides: [
+        {
+            // Server-side files (plus this configuration file)
+            files: ['src/**/*.js', './*.js', 'plugins/**/*.js'],
+            env: {
+                node: true,
+            },
+            parserOptions: {
+                sourceType: 'module',
+            },
+            globals: {
+                globalThis: 'readonly',
+                Deno: 'readonly',
+            },
+        },
+        {
+            files: ['*.cjs'],
+            parserOptions: {
+                sourceType: 'commonjs',
+            },
+            env: {
+                node: true,
+            },
+        },
+        {
+            files: ['src/**/*.mjs'],
+            parserOptions: {
+                sourceType: 'module',
+            },
+            env: {
+                node: true,
+            },
+        },
+        {
+            // Browser-side files
+            files: ['public/**/*.js'],
+            env: {
+                browser: true,
+                jquery: true,
+            },
+            parserOptions: {
+                sourceType: 'module',
+            },
+            // These scripts are loaded in HTML; tell ESLint not to complain about them being undefined
+            globals: {
+                globalThis: 'readonly',
+                ePub: 'readonly',
+                pdfjsLib: 'readonly',
+                toastr: 'readonly',
+                SillyTavern: 'readonly',
+            },
+        },
+    ],
+    ignorePatterns: [
+        '**/node_modules/**',
+        '**/dist/**',
+        '**/.git/**',
+        'public/lib/**',
+        'backups/**',
+        'data/**',
+        'cache/**',
+        'src/tokenizers/**',
+        'docker/**',
+        'plugins/**',
+        '**/*.min.js',
+        'public/scripts/extensions/quick-reply/lib/**',
+        'public/scripts/extensions/tts/lib/**',
+    ],
+    rules: {
+        'no-unused-vars': ['error', { args: 'none' }],
+        'no-control-regex': 'off',
+        'no-constant-condition': ['error', { checkLoops: false }],
+        'require-yield': 'off',
+        'quotes': ['error', 'single'],
+        'semi': ['error', 'always'],
+        'indent': ['error', 4, { SwitchCase: 1, FunctionDeclaration: { parameters: 'first' } }],
+        'comma-dangle': ['error', 'always-multiline'],
+        'eol-last': ['error', 'always'],
+        'no-trailing-spaces': 'error',
+        'object-curly-spacing': ['error', 'always'],
+        'space-infix-ops': 'error',
+        'no-unused-expressions': ['error', { allowShortCircuit: true, allowTernary: true }],
+        'no-cond-assign': 'error',
+        'no-unneeded-ternary': 'error',
+        'no-irregular-whitespace': ['error', { skipStrings: true, skipTemplates: true }],
+
+        // These rules should eventually be enabled.
+        'no-async-promise-executor': 'off',
+        'no-inner-declarations': 'off',
+    },
+};

jiuguan2025cc/.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,93 @@
+name: Bug Report 🐛
+type: Bug
+description: Report something that's not working the intended way. Support requests for external programs (reverse proxies, 3rd party servers, other peoples' forks) will be refused! Please use English only.
+title: '[BUG] <title>'
+labels: ['🐛 Bug']
+body:
+  - type: dropdown
+    id: environment
+    attributes:
+      label: Environment
+      description: Where are you running SillyTavern?
+      options:
+        - 🪟 Windows
+        - 🐧 Linux
+        - 📱 Termux
+        - 🐋 Docker
+        - 🍎 Mac
+    validations:
+      required: true
+
+  - type: input
+    id: system
+    attributes:
+      label: System
+      description: >-
+        For deployment issues, specify your [distro or OS](https://whatsmyos.com/) and/ or Docker version.
+        For client-side issues, include your [browser version](https://www.whatsmybrowser.org/)
+      placeholder: e.g. Firefox 101, Manjaro Linux 21.3.0, Docker 20.10.16
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: What version of SillyTavern are you running?
+      placeholder: (check User Settings to see the version)
+    validations:
+      required: true
+
+  - type: textarea
+    id: desktop
+    attributes:
+      label: Desktop Information
+      description: Please provide details about your desktop environment.
+      placeholder: |
+        - Node.js version (if applicable): [run `node --version` in cmd]
+        - Generation API [e.g. KoboldAI, OpenAI]
+        - Branch [staging, release]
+        - Model [e.g. Pygmalion 6b, LLaMa 13b]
+    validations:
+      required: false
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Describe the problem
+      description: Please describe exactly what is not working, include the steps to reproduce, actual result and expected result
+      placeholder: When doing ABC then DEF, I expect to see XYZ, but I actually see ZYX
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Additional info
+      description: Logs? Screenshots? Yes, please.
+      placeholder: If the issue happens during build-time, include terminal logs. For run-time errors, include browser logs which you can view in the Dev Tools (F12), under the Console tab. Take care to blank out any personal info.
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: user-check
+    attributes:
+      label: Please tick the boxes
+      description: Before submitting, please ensure that you have completed the following checklist
+      options:
+        - label: I have explained the issue clearly, and I included all relevant info
+          required: true
+        - label: I have checked that this [issue hasn't already been raised](https://github.com/SillyTavern/SillyTavern/issues?q=is%3Aissue)
+          required: true
+        - label: I have checked the [docs](https://docs.sillytavern.app/) ![important](https://img.shields.io/badge/Important!-F6094E)
+          required: true
+        - label: I confirm that my issue is not related to third-party content, unofficial extension or patch. If in doubt, check with a new [user account](https://docs.sillytavern.app/administration/multi-user/) and with extensions disabled
+          required: true
+
+  - type: markdown
+    attributes:
+      value: |-
+        ## Thanks 🙏
+        Thank you for raising this ticket - in doing so you are helping to make SillyTavern better for everyone.
+    validations:
+      required: false

jiuguan2025cc/.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,92 @@
+name: Feature Request ✨
+type: Feature
+description: Suggest an idea for future development of this project. Please use English only.
+title: '[FEATURE_REQUEST] <title>'
+labels: ['🦄 Feature Request']
+
+body:
+
+  # Field 1 - Did the user searched for similar requests
+  - type: dropdown
+    id: similarRequest
+    attributes:
+      label: Have you searched for similar requests?
+      description:
+      options:
+        - 'No'
+        - 'Yes'
+    validations:
+      required: true
+
+  # Field 2 - Is it bug-related
+  - type: textarea
+    id: issue
+    attributes:
+      label: Is your feature request related to a problem? If so, please describe.
+      description:
+      placeholder: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: false
+
+  # Field 3 - Describe feature
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      placeholder: An outline of how you would like this to be implemented, include as much details as possible
+    validations:
+      required: true
+
+  # Field 4 - Describe alternatives
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Describe alternatives you've considered
+      placeholder: A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: false
+
+  # Field 5 - Additional context
+  - type: textarea
+    id: addcontext
+    attributes:
+      label: Additional context
+      placeholder: Add any other context or screenshots about the feature request here.
+    validations:
+      required: false
+
+  # Field 6 - Priority
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: How urgent is the development of this feature
+      options:
+        - Low (Nice-to-have)
+        - Medium (Would be very useful)
+        - High (The app does not function without it)
+    validations:
+      required: true
+
+  # Field 7 - Can the user user test in staging
+  - type: dropdown
+    id: canTestStaging
+    attributes:
+      label: Are you willing to test this on staging/unstable branch if this is implemented?
+      description: Otherwise you'll need to wait until the next stable release after the feature is developed.
+      options:
+        - 'No'
+        - 'Maybe'
+        - 'Yes'
+    validations:
+      required: false
+
+  # Final text
+  - type: markdown
+    attributes:
+      value: |-
+        ## Thanks 🙏
+        Thank you for your feature suggestion.
+        Please note that there is no guarantee that your idea will be implemented.
+    validations:
+      required: false

jiuguan2025cc/.github/issues-auto-comments.yml

@@ -0,0 +1,69 @@
+labels:
+  - name: ✖️ Invalid
+    labeled:
+      issue:
+        action: close
+        body: >
+          Hey @{{ issue.user.login }}, this issue has been marked as invalid.
+
+          Please double-check that you've followed the issue template, included all necessary details, and reviewed the docs & previous issues before submitting.
+          If provided, follow the instructions given by maintainers.
+
+  - name: 👩‍💻 Good First Issue
+    labeled:
+      issue:
+        body: >
+          🏆 This issue has been marked as a good first issue for contributors to implement!
+          This is a great way to support the project. While also improving your skills, you'll also be credited as a contributor once your PR is merged.
+
+          If you're new to SillyTavern [here is the official documentation](https://docs.sillytavern.app/). The official contribution guide can be found [here](https://github.com/SillyTavern/SillyTavern/blob/release/CONTRIBUTING.md).
+          If you need any support, feel free to reach out via [Discord](https://discord.gg/sillytavern), or let us know in this issue or via [discussions](https://github.com/SillyTavern/SillyTavern/discussions).
+
+  - name: ❌ wontfix
+    labeled:
+      issue:
+        action: close
+        body: >
+          ❌ This issue has been marked as 'wontfix', which usually means it is out-of-scope, not feasible at this time or will not be implemented for various reasons.
+          If you have any questions about this, feel free to reach out.
+
+  - name: 🛑 Out of Scope
+    labeled:
+      issue:
+        action: close
+        body: >
+          🛑 This issue has been marked as 'out of scope', as this can't or won't be implemented.
+          If you have any questions about this, feel free to reach out.
+
+  - name: ✅ Done (staging)
+    labeled:
+      issue:
+        body: >
+          ✅ It looks like all or part of this issue has now been implemented as part of the `staging` branch.
+          If you currently are on the `release` branch, you can switch to `staging` to test this right away.
+
+          Note that `staging` is considered less stable than the official releases. To switch, follow existing instructions,
+          or simply enter the following command: `git switch staging`
+
+  - name: ✅ Done
+    labeled:
+      issue:
+        body: >
+          ✅ It looks like all or part of this issue has now been implemented as part of the latest release.
+
+  - name: ‼️ High Priority
+    labeled:
+      issue:
+        body: >
+          🚨 This issue has been marked high priority, meaning it's important to the maintainers or community.
+          While we can't promise immediate changes, it is on our radar and will be addressed whenever possible. Thanks for your patience!
+
+  - name: 💀 Spam
+    labeled:
+      issue:
+        action: close
+        locking: lock
+        lock_reason: spam
+        body: >
+          💀 This issue has been flagged as spam and is now locked.
+          Please avoid posting spam - it disrupts the community and wastes everyone's time.

jiuguan2025cc/.github/issues-auto-labels.yml

@@ -0,0 +1,20 @@
+🪟 Windows:
+    - '(🪟 Windows)'
+
+🍎 Mac:
+    - '(🍎 Mac)'
+
+🐋 Docker:
+    - '(🐋 Docker)'
+
+📱 Termux:
+    - '(📱 Termux)'
+
+🐧 Linux:
+    - '(🐧 Linux)'
+
+🦊 Firefox:
+    - '(firefox|mozilla)'
+
+📱 Mobile:
+    - '(iphone|ios|android|📱 Termux)'

jiuguan2025cc/.github/pr-auto-comments.yml

@@ -0,0 +1,51 @@
+labels:
+  - name: ✖️ Invalid
+    labeled:
+      pr:
+        action: close
+        body: >
+          Hey @{{ pull_request.user.login }}, thanks for your contribution!
+          Unfortunately, this PR has been marked as invalid.
+
+          Please check that you've followed the PR template, included all relevant details, and are targeting the correct branch (`staging` for regular contributions, `release` only for hotfixes).
+
+          If you need help, feel free to ask!
+
+  - name: ⛔ Don't Merge
+    labeled:
+      pr:
+        body: >
+          🚨 This PR has been temporarily blocked from merging.
+
+  - name: 💥💣 Breaking Changes
+    labeled:
+      pr:
+        body: >
+          ⚠️ Heads up! This PR introduces breaking changes.
+
+          Make sure these changes are well-documented and that users will be properly informed when this is released.
+
+  - name: ⛔ Waiting For External/Upstream
+    labeled:
+      pr:
+        body: >
+            ⛔ This PR is awaiting external or upstream changes or approval.
+            It can only be merged once those changes have been implemented and approved.
+
+            Please inform us of any progress on the upstream changes or approval.
+
+  - name: 🔬 Needs Testing
+    labeled:
+      pr:
+        body: >
+          🔬 This PR needs testing!
+          Any contributor can test and leave reviews, so feel free to help us out!
+
+  - name: 🟥 ⬤⬤⬤⬤⬤
+    labeled:
+      pr:
+        body: >
+            ⚠️ This PR is over 1000 lines, which is larger than recommended.
+
+            Please make sure that it only addresses a single issue - PRs this large are hard to test and may be rejected.
+

jiuguan2025cc/.github/pr-auto-labels-by-branch.yml

@@ -0,0 +1,77 @@
+####################################
+# Label PRs against 'release'      #
+####################################
+❗ Against Release Branch:
+- base-branch: 'release'
+
+####################################
+# Labels based on PR branch name   #
+####################################
+🦋 Bug Fix:
+- head-branch: ['^fix[/-]', '\bfixes\b']
+
+🚑 Hot Fix:
+- head-branch: ['^hotfix[/-]']
+
+✨ New Feature:
+- head-branch: ['^feat(ure)?[/-].*?\badd', '^add-']
+
+✨ Feature Changes:
+- head-branch: ['^feat(ure)?[/-](?!.*\badd\b)', '\bchanges?\b']
+
+🤖 API / Model:
+- head-branch: ['\bapi\b', '\bmodels?\b']
+
+🏭 Backend Changes:
+- head-branch: ['\bbackend\b', '\bendpoints?\b']
+
+🐋 Docker:
+- head-branch: ['\bdocker\b']
+
+➕ Extension:
+- head-branch: ['\bextension\b', '\bext\b']
+
+🦊 Firefox:
+- head-branch: ['\bfirefox\b']
+
+🖼️ Image Gen:
+- head-branch: ['\bimage-gen\b']
+
+🌐 Language:
+- head-branch: ['\btranslations?\b', '\blanguages?\b']
+
+🐧 Linux:
+- head-branch: ['\blinux\b']
+
+🧩 Macros:
+- head-branch: ['\bmacros?\b']
+
+📱 Mobile:
+- head-branch: ['\bmobile\b', '\bios\b', '\bandroid\b']
+
+🚄 Performance:
+- head-branch: ['\bperformance\b']
+
+⚙️ Preset:
+- head-branch: ['\bpresets?\b']
+
+📜 Prompt:
+- head-branch: ['\bprompt\b']
+
+🚚 Refactor:
+- head-branch: ['\brefactor(s|ed)?\b']
+
+📜 STscript:
+- head-branch: ['\bstscript\b', '\bslash-commands\b']
+
+🏷️ Tags / Folders:
+- head-branch: ['\btags\b']
+
+🎙️ TTS / Voice:
+- head-branch: ['\btts\b', '\bvoice\b']
+
+🌟 UX:
+- head-branch: ['\bux\b']
+
+🗺️ World Info:
+- head-branch: ['\bworld-info\b', '\bwi\b']

jiuguan2025cc/.github/pr-auto-labels-by-files.yml

@@ -0,0 +1,46 @@
+####################################
+# Labels based on changed files    #
+####################################
+🏭 Backend Changes:
+- changed-files:
+  - any-glob-to-any-file:
+    - "src/**"
+    - "default/config.yaml"
+    - "server.js"
+    - "plugins.js"
+    - "recover.js"
+    - "webpack.config.js"
+    - "Start.bat"
+    - "start.sh"
+    - "UpdateAndStart.bat"
+    - "UpdateForkAndStart.bat"
+
+⚙️ config.yaml:
+- changed-files:
+  - any-glob-to-any-file:
+    - "default/config.yaml"
+
+🛠️ Build Changes:
+- changed-files:
+  - any-glob-to-any-file:
+    - ".github/workflows/**"
+    - "docker/**"
+    - ".dockerignore"
+    - "Dockerfile"
+    - "webpack.config.js"
+
+🌐 Language:
+- changed-files:
+  - any-glob-to-any-file:
+    - "public/locales/**"
+
+📥 Dependencies:
+- changed-files:
+  - any-glob-to-any-file:
+    - "public/lib/**" # Every frontend lib counts as a dependency as well
+    - "package.json"
+    - "package-lock.json"
+    - "tests/package.json"
+    - "tests/package-lock.json"
+    - "src/electron/package.json"
+    - "src/electron/package-lock.json"

jiuguan2025cc/.github/pull_request_template.md

@@ -0,0 +1,5 @@
+<!-- Put X in the box below to confirm -->
+
+## Checklist:
+
+- [ ] I have read the [Contributing guidelines](https://github.com/SillyTavern/SillyTavern/blob/release/CONTRIBUTING.md).

jiuguan2025cc/.github/readme-de_de.md

@@ -0,0 +1,383 @@
+> [!IMPORTANT]  
+> Die hier veröffentlichten Informationen sind möglicherweise veraltet oder unvollständig. Für aktuelle Informationen nutzen Sie bitte die englische Version.
+> Letztes Update dieser README: 28.9.2024
+
+<a name="readme-top"></a>
+
+![][cover]
+
+<div align="center">
+
+[English](readme.md) | German | [中文](readme-zh_cn.md) | [繁體中文](readme-zh_tw.md) | [日本語](readme-ja_jp.md) | [Русский](readme-ru_ru.md) | [한국어](readme-ko_kr.md)
+
+[![GitHub Stars](https://img.shields.io/github/stars/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/stargazers)
+[![GitHub Forks](https://img.shields.io/github/forks/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/network)
+[![GitHub Issues](https://img.shields.io/github/issues/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/issues)
+[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/pulls)
+
+</div>
+
+---
+
+SillyTavern bietet eine einheitliche Benutzeroberfläche für viele LLM-APIs (KoboldAI/CPP, Horde, NovelAI, Ooba, Tabby, OpenAI, OpenRouter, Claude, Mistral und mehr), ein mobilfreundliches Layout, einen Visual-Novel-Modus, die Integration von Automatic1111 & ComfyUI API zur Bilderzeugung, TTS, WorldInfo (Lorebooks), anpassbare UI, automatische Übersetzung, mehr Eingabeaufforderungsoptionen, als du jemals wolltest oder brauchst, und unendliches Wachstumspotenzial durch Drittanbietererweiterungen.
+
+Wir haben eine [Dokumentationswebsite](https://docs.sillytavern.app/), um die meisten deiner Fragen zu beantworten und dir den Einstieg zu erleichtern.
+
+## Was ist SillyTavern?
+
+SillyTavern (oder ST abgekürtz) ist eine lokal installierte Benutzeroberfläche, die es dir ermöglicht, mit Textgenerations-LLMs, Bildgenerierungsmaschinen und TTS-Sprachmodellen zu interagieren.
+
+Angefangen im Februar 2023 als Fork von TavernAI 1.2.8 hat SillyTavern nun über 100 Mitwirkende und 2 Jahre unabhängiger Entwicklung hinter sich und dient weiterhin als führende Software für versierte KI-Hobbyisten.
+
+## Unsere Vision
+
+1. Wir möchten die Nutzer mit so viel Nutzen und Kontrolle über ihre LLM-Prompts wie möglich ausstatten. Die steile Lernkurve ist Teil des Spaßes!
+2. Wir bieten weder Online- oder gehosteten Dienste an, noch verfolgen wir programmgesteuert Benutzerdaten.
+3. SillyTavern ist ein Herzensprojekt, das von einer engagierten Community von LLM-Enthusiasten unterstützt wird, und wird immer kostenlos und Open Source sein.
+
+## Branches
+
+SillyTavern wird mit einem Branchsystem entwickelt, um ein reibungsloses Erlebnis für alle Nutzer zu gewährleisten.
+
+* `release` -🌟 **Empfohlen für die meisten Nutzer.** Dies ist der stabilste und empfohlene Branch, der nur aktualisiert wird, wenn wichtige Versionen veröffentlicht werden. Er ist für die Mehrheit der Nutzer geeignet. Typischerweise einmal im Monat aktualisiert.
+* `staging` - ⚠️ **Nicht für den gelegentlichen Gebrauch empfohlen.** Dieser Branch enthält die neuesten Funktionen, kann jedoch jederzeit instabil sein. Nur für Power-User und Enthusiasten. Mehrmals täglich aktualisiert.
+
+Wenn du nicht vertraut mit der Verwendung der git CLI bist oder nicht verstehst, was ein Branch ist, mach dir keine Sorgen! Der Release-Branch ist immer die bevorzugte Option für dich.
+
+## Was brauche ich zusätzlich zu SillyTavern?
+
+Da SillyTavern nur eine Benutzeroberfläche ist, benötigst du Zugriff auf ein LLM-Backend, um Inferenz bereitzustellen. Du kannst AI Horde für sofortiges Chatten ohne weitere Einrichtung verwenden. Darüber hinaus unterstützen wir viele andere lokale und cloudbasierte LLM-Backends: OpenAI-kompatible API, KoboldAI, Tabby und viele mehr. Du kannst mehr über unsere unterstützten APIs in [der FAQ](https://docs.sillytavern.app/usage/api-connections/) lesen.
+
+### Brauche ich einen leistungsstarken PC, um SillyTavern auszuführen?
+
+Die Hardwareanforderungen sind minimal: Es läuft auf allem, was NodeJS 18 oder höher ausführen kann. Wenn du LLM-Inferenz auf deinem lokalen Rechner durchführen möchtest, empfehlen wir eine NVIDIA-Grafikkarte der 3000er-Serie mit mindestens 6 GB VRAM. Überprüfe die Dokumentation deines Backends für weitere Einzelheiten.
+
+### Vorgeschlagene Backends (keine Partnerschaft oder Werbebeziehung)
+
+* [AI Horde](https://aihorde.net/) - verwende Modelle, die von Freiwilligen gehostet werden. Erfordert keine weitere Einrichtung
+* [KoboldCpp](https://github.com/LostRuins/koboldcpp) - ein Favorit der Community, um GGUF-Modelle lokal auszuführen
+* [tabbyAPI](https://github.com/theroyallab/tabbyAPI) - eine beliebte, portable, speicherplatzoptimierte und lokal gehostete exl2 Inferenz-API
+* [OpenRouter](https://openrouter.ai) - eine einzige API für viele Cloud-Anbieter (OpenAI, Claude, Meta Llama usw.) sowie beliebte Community-Modelle.
+
+## Fragen oder Vorschläge?
+
+### Discord-Server
+
+| [![][discord-shield-badge]][discord-link] | [Tritt unserer Discord-Community bei!](https://discord.gg/sillytavern) Erhalte Unterstützung, teile deine Lieblingscharaktere und Prompts. |
+| :---------------------------------------- | :----------------------------------------------------------------------------------------------------------------- |
+
+Oder nimm direkt Kontakt mit den Entwicklern auf:
+
+* Discord: cohee, rossascends, wolfsblvt
+* Reddit: [/u/RossAscends](https://www.reddit.com/user/RossAscends/), [/u/sillylossy](https://www.reddit.com/user/sillylossy/), [u/Wolfsblvt](https://www.reddit.com/user/Wolfsblvt/)
+* [Erstelle ein GitHub-Issue](https://github.com/SillyTavern/SillyTavern/issues)
+
+### Ich mag dieses Projekt! Wie kann ich beitragen?
+
+1. Sende Pull-Requests. Lerne, wie du beitragen kannst: [CONTRIBUTING.md](../CONTRIBUTING.md)
+2. Sende Feature Requests und Issues unter Verwendung der bereitgestellten Vorlagen.
+3. Lies diese gesamte README-Datei und überprüfe zuerst die Dokumentationswebsite, um doppelte Issues zu vermeiden.
+
+## Screenshots
+
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/9b5f32f0-c3b3-4102-b3f5-0e9213c0f50f">
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/913fdbaa-7d33-42f1-ae2c-89dca41c53d1">
+
+## Charakterkarten
+
+SillyTavern basiert auf dem Konzept der "Charakterkarten". Eine Charakterkarte ist eine Sammlung von Prompts, die das Verhalten des LLM festlegen und erforderlich sind, um persistente Gespräche in SillyTavern zu führen. Sie funktionieren ähnlich wie ChatGPT's GPTs oder Poe's Bots. Der Inhalt einer Charakterkarte kann alles sein: ein abstraktes Szenario, ein Assistent, der für eine bestimmte Aufgabe maßgeschneidert ist, eine berühmte Persönlichkeit oder ein fiktiver Charakter.
+
+Das Namensfeld ist der einzige erforderliche Eingabewert für die Charakterkarte. Um ein neutrales Gespräch mit dem LLM zu beginnen, erstelle eine neue Karte, die einfach "Assistent" genannt wird, und lasse die restlichen Felder leer. Für einen thematischeren Chat kannst du dem LLM verschiedene Hintergrundinformationen, Verhaltensweisen und Schreibmuster sowie ein Szenario geben, um das Gespräch zu beginnen.
+
+Um ein schnelles Gespräch zu führen, ohne eine Charakterkarte auszuwählen, oder um einfach die LLM-Verbindung zu testen, gib einfach dein Prompt in die Eingabezeile auf dem Willkommensbildschirm ein, nachdem du SillyTavern geöffnet hast. Bitte beachte, dass solche Chats vorübergehend sind und nicht gespeichert werden.
+
+Um eine allgemeine Vorstellung davon zu bekommen, wie man Charakterkarten definiert, sieh dir die mitgelieferte Charakterkarte (Seraphina) an oder lade ausgewählte von der Community erstellte Karten im Menü "Erweiterungen & Assets herunterladen" herunter.
+
+## Wichtigste Features
+
+* Erweiterte Text-Generierungs-Einstellungen mit vielen von der Community erstellten mitgelieferten Einstellungen (Presets)
+* Unterstützung für World Info: Erstelle reichhaltige Lore oder reduziere die Tokens in deiner Charakterkarte
+* Gruppenchats: Multi-Bot-Räume für Charaktere, die mit dir und/oder untereinander sprechen
+* Reichhaltige UI-Anpassungsoptionen: Themes zur Farbenwahl, Hintergrundbilder, benutzerdefiniertes CSS und mehr
+* Benutzer-Personas: Lass die KI ein wenig über dich wissen, um die Immersion zu erhöhen
+* Eingebaute RAG-Unterstützung: Füge Dokumente zu deinen Chats hinzu, auf die die KI verweisen kann
+* Umfangreiches "Chat-Befehle"-System und eigene [Scripting-Engine](https://docs.sillytavern.app/usage/st-script/)
+
+## Erweiterungen
+
+SillyTavern unterstützt Erweiterungen.
+
+* Emotionale Ausdrucksformen von Charakteren (Sprites)
+* Automatische Zusammenfassung des Chatverlaufs
+* Automatische UI- und Chat-Übersetzung
+* Bildgenerierung mit Stable Diffusion/FLUX/DALL-E
+* Text-to-Speech für KI-Antwortnachrichten (über ElevenLabs, Silero oder die TTS-Funktion des Betriebssystems)
+* Websuchfunktionen zum Hinzufügen zusätzlicher realer Kontexte zu deinen Eingabeaufforderungen
+* Viele weitere sind im Menü "Erweiterungen & Assets herunterladen" verfügbar.
+
+Tutorials zur Nutzung findest du in der [Dokumentation](https://docs.sillytavern.app/).
+
+# ⌛ Installation
+
+> \[!WARNING]
+>
+> * INSTALLIERE NICHT IN EINEM VON WINDOWS KONTROLLIERTEN ORDNER (Programme, System32 usw.).
+> * FÜHRE START.BAT NICHT MIT ADMIN-BERECHTIGUNGEN AUS.
+> * DIE INSTALLATION AUF WINDOWS 7 IST UNMÖGLICH, DA ES NODEJS 18.16 NICHT AUSFÜHREN KANN.
+
+## 🪟 Windows
+
+### Installation über Git
+
+1. Installiere [NodeJS](https://nodejs.org/en) (die neueste LTS-Version wird empfohlen).
+2. Installiere [Git für Windows](https://gitforwindows.org/).
+3. Öffne den Windows-Explorer (`Win+E`).
+4. Gehe zu oder erstelle einen Ordner, der nicht von Windows kontrolliert oder überwacht wird. (z.B.: C:\MySpecialFolder\)
+5. Öffne ein Eingabeaufforderungsfenster in diesem Ordner, indem du in die 'Adressleiste' oben klickst, `cmd` eingibst und Enter drückst.
+6. Sobald das schwarze Fenster (Eingabeaufforderung) erscheint, gib EINE der folgenden Optionen ein und drücke Enter:
+
+* für den Release-Branch: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+* für den Staging-Branch: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+7. Sobald alles geklont ist, doppelklicke auf `Start.bat`, damit NodeJS seine Anforderungen installiert.
+8. Der Server wird dann gestartet, und SillyTavern wird in deinem Browser geöffnet.
+
+### Installation über GitHub Desktop
+
+(Dies ermöglicht die Nutzung von git **nur** in GitHub Desktop. Wenn du `git` auch in der Eingabeaufforderung verwenden möchtest, musst du auch [Git für Windows](https://gitforwindows.org/) installieren.)
+
+1. Installiere [NodeJS](https://nodejs.org/en) (die neueste LTS-Version wird empfohlen).
+2. Installiere [GitHub Desktop](https://central.github.com/deployments/desktop/desktop/latest/win32).
+3. Klicke nach der Installation von GitHub Desktop auf `Ein Repository aus dem Internet klonen....` (Hinweis: Du **musst kein** GitHub-Konto für diesen Schritt erstellen).
+4. Klicke im Menü auf den Tab URL, gib diese URL ein `https://github.com/SillyTavern/SillyTavern` und klicke auf Klonen. Du kannst den lokalen Pfad ändern, um festzulegen, wohin SillyTavern heruntergeladen werden soll.
+5. Um SillyTavern zu öffnen, durchsuche mit dem Windows-Explorer den Ordner, in den du das Repository geklont hast. Standardmäßig wird das Repository hier hin geklont: `C:\Users\[Dein Windows-Benutzername]\Documents\GitHub\SillyTavern`.
+6. Doppelklicke auf die Datei `start.bat`. (Hinweis: Der Teil `.bat` des Dateinamens könnte von deinem Betriebssystem verborgen sein. In diesem Fall sieht es aus wie eine Datei namens "`Start`". Dies ist die Datei, auf die du doppelklickst, um SillyTavern auszuführen.)
+7. Nach dem Doppelklicken sollte ein großes schwarzes Konsolenfenster erscheinen, und SillyTavern beginnt, das zu installieren, was es zum Betrieb benötigt.
+8. Nach dem Installationsprozess sollte das Konsolenfenster so aussehen, und ein SillyTavern-Tab sollte in deinem Browser geöffnet sein.
+9. Verbinde dich mit einer der [unterstützten APIs](https://docs.sillytavern.app/usage/api-connections/) und beginne zu chatten!
+
+## 🐧 Linux & 🍎 MacOS
+
+Für MacOS/Linux werden all diese Schritte in einem Terminal durchgeführt.
+
+1. Installiere git und nodeJS (die Methode zur Durchführung hängt von deinem Betriebssystem ab).
+2. Klone das Repository.
+
+* für den Release-Branch: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+* für den Staging-Branch: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+3. `cd SillyTavern`, um in den Installationsordner zu navigieren.
+4. Führe das Skript `start.sh` mit einem dieser Befehle aus:
+
+* `./start.sh`
+* `bash start.sh`
+
+## ⚡ Installation über SillyTavern Launcher
+
+Der SillyTavern Launcher ist ein Installationsassistent, der dir bei der Einrichtung mit vielen Optionen helfen wird, einschließlich der Installation eines Backends für lokale Inferenz.
+
+### Für Windows-Nutzer
+
+1. Drücke auf deiner Tastatur **`WINDOWS + R`**, um das Ausführen-Dialogfeld zu öffnen. Führe dann den folgenden Befehl aus, um git zu installieren:
+
+```shell
+cmd /c winget install -e --id Git.Git
+```
+
+2. Drücke auf deiner Tastatur **`WINDOWS + E`**, um den Datei-Explorer zu öffnen, und navigiere dann zu dem Ordner, in dem du den Launcher installieren möchtest. Gib im gewünschten Ordner in die Adressleiste `cmd` ein und drücke Enter. Führe dann den folgenden Befehl aus:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher && start installer.bat
+```
+
+### Für Linux-Nutzer
+
+1. Öffne dein bevorzugtes Terminal und installiere git.
+2. Klone den SillyTavern-Launcher mit:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+3. Starte die installer.sh mit:
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+4. Nach der Installation starte die launcher.sh mit:
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+### Für Mac-Nutzer
+
+1. Öffne ein Terminal und installiere brew mit:
+
+```shell
+/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+```
+
+2. Installiere git mit:
+
+```shell
+brew install git
+```
+
+3. Klone den SillyTavern-Launcher mit:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+4. Starte die installer.sh mit:
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+5. Nach der Installation starte die launcher.sh mit:
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+## 🐋 Installation über Docker
+
+Diese Anweisungen setzen voraus, dass du Docker installiert hast, auf deine Befehlszeile für die Installation von Containern zugreifen kannst und mit deren allgemeiner Funktionsweise vertraut bist.
+
+### Image selbst bauen
+
+Wir haben einen umfassenden Leitfaden zur Nutzung von SillyTavern in Docker [hier](http://docs.sillytavern.app/installation/docker/) der die Installationen auf Windows, macOS und Linux abdeckt! Lies ihn, wenn du das Image selbst bauen möchtest.
+
+### Verwendung der GitHub Container Registry (am einfachsten)
+
+Du benötigst zwei zwingende Verzeichniszuordnungen und eine Portzuordnung, um SillyTavern funktionsfähig zu machen. Ersetze in dem Befehl deine Auswahl an den folgenden Stellen:
+
+#### Container-Variablen
+
+##### Volumen-Zuordnungen
+
+* [config] - Das Verzeichnis, in dem die SillyTavern-Konfigurationsdateien auf deinem Host-Computer gespeichert werden
+* [data] - Das Verzeichnis, in dem die Benutzerdaten von SillyTavern (einschließlich Charaktere) auf deinem Host-Computer gespeichert werden
+* [plugins] - (optional) Das Verzeichnis, in dem die SillyTavern-Server-Plugins auf deinem Host-Computer gespeichert werden
+
+##### Port-Zuordnungen
+
+* [PublicPort] - Der Port, über den der Datenverkehr ausgegeben werden soll. Dies ist zwingend erforderlich, da du auf die Instanz von außerhalb des virtuellen Maschinencontainers zugreifst. EXPOSIERE DIES NICHT IM INTERNET, OHNE EINEN GETRENNTEN SERVICE FÜR DIE SICHERHEIT ZU IMPLEMENTIEREN.
+
+##### Zusätzliche Einstellungen
+
+* [DockerNet] - Das Docker-Netzwerk, mit dem der Container erstellt werden soll. Wenn du nicht weißt, was das ist, sieh dir die [offizielle Docker-Dokumentation](https://docs.docker.com/reference/cli/docker/network/) an.
+* [version] - Auf der rechten Seite dieser GitHub-Seite siehst du "Packages". Wähle das Paket "sillytavern" und du siehst die Imageversionen. Das Image-Tag "latest" hält dich auf dem Laufenden mit dem aktuellen Release. Du kannst auch "staging" und "release" Tags nutzen, die auf die nightly images der jeweiligen Branche verweisen, aber das könnte unangemessen sein, wenn du Erweiterungen verwendest, die möglicherweise kaputt sind und Zeit benötigen, um aktualisiert zu werden.
+
+#### Installationsbefehl
+
+1. Öffne deine Befehlszeile.
+2. Führe den folgenden Befehl aus:
+
+`docker create --name='sillytavern' --net='[DockerNet]' -p '8000:8000/tcp' -v '[plugins]':'/home/node/app/plugins':'rw' -v '[config]':'/home/node/app/config':'rw' -v '[data]':'/home/node/app/data':'rw' 'ghcr.io/sillytavern/sillytavern:[version]'`
+
+> Beachte, dass 8000 ein Standard-Listening-Port ist. Vergiss nicht, einen geeigneten Port zu verwenden, wenn du ihn in der Konfiguration änderst.
+
+## 📱 Installation über Termux auf Android OS
+
+> \[!HINWEIS]
+> **SillyTavern kann nativ auf Android-Geräten über Termux ausgeführt werden, aber wir bieten keine offizielle Unterstützung für diesen Anwendungsfall.**
+>
+> **Bitte beziehe dich auf diesen Leitfaden von ArroganceComplex#2659:**
+>
+> * <https://rentry.org/STAI-Termux>
+
+**Nicht unterstützte Plattform: android arm LEtime-web.** 32-Bit-Android benötigt eine externe Abhängigkeit, die nicht mit npm installiert werden kann. Verwende den folgenden Befehl, um sie zu installieren: `pkg install esbuild`. Führe dann die üblichen Installationsschritte aus.
+
+## API-Schlüsselverwaltung
+
+SillyTavern speichert deine API-Schlüssel in einer Datei `secrets.json` im Benutzerdatenverzeichnis (`/data/default-user/secrets.json` ist der Standardpfad).
+
+Standardmäßig sind API-Schlüssel nach dem Speichern und Aktualisieren der Seite nicht mehr über die Benutzeroberfläche sichtbar.
+
+Um die Ansicht deiner Schlüssel zu aktivieren:
+
+1. Setze den Wert von `allowKeysExposure` auf `true` in der Datei `config.yaml`.
+2. Starte den SillyTavern-Server neu.
+3. Klicke auf den Link 'Verborgene API-Schlüssel anzeigen' in der unteren rechten Ecke des API-Verbindungsfeldes.
+
+## Befehlszeilenargumente
+
+Sie können Befehlszeilenargumente an den Start des SillyTavern-Servers übergeben, um einige Einstellungen in `config.yaml` zu überschreiben.
+
+### Beispiele
+
+```shell
+node server.js --port 8000 --listen false
+# oder
+npm run start -- --port 8000 --listen false
+# oder (nur Windows)
+Start.bat --port 8000 --listen false
+```
+
+### Unterstützte Argumente
+
+| Option | Beschreibung | Typ |
+|-------------------------|----------------------------------------------------------------------------------------------------|----------|
+| `--version` | Versionsnummer anzeigen | boolean |
+| `--enableIPv6` | Aktiviert IPv6. | boolean |
+| `--enableIPv4` | Aktiviert IPv4. | boolean |
+| `--port` | Legt den Port fest, unter dem SillyTavern ausgeführt wird. Wenn nicht angegeben, wird auf YAML-Konfiguration „Port“ zurückgegriffen. | number |
+| „--dnsPreferIPv6“ | Bevorzugt IPv6 für DNS. Wenn nicht angegeben, wird auf YAML-Konfiguration „preferIPv6“ zurückgegriffen. | boolean |
+| „--autorun“ | Startet SillyTavern automatisch im Browser. Wenn nicht angegeben, wird auf YAML-Konfiguration „autorun“ zurückgegriffen.| boolean |
+| „--autorunHostname“ | Der Autorun-Hostname, am besten auf „auto“ belassen. | string |
+| „--autorunPortOverride“ | Überschreibt den Port für Autorun. | string |
+| „--listen“ | SillyTavern lauscht auf allen Netzwerkschnittstellen. Wenn nicht angegeben, wird auf YAML-Konfiguration „listen“ zurückgegriffen.| boolean |
+| „--corsProxy“ | Aktiviert CORS-Proxy. Wenn nicht angegeben, wird auf YAML-Konfiguration „enableCorsProxy“ zurückgegriffen. | boolean |
+| `--disableCsrf` | Deaktiviert CSRF-Schutz | boolean |
+| `--ssl` | Aktiviert SSL | boolean |
+| `--certPath` | Pfad zu Ihrer Zertifikatsdatei. | string |
+| `--keyPath` | Pfad zu Ihrer privaten Schlüsseldatei. | string |
+| `--whitelist` | Aktiviert den Whitelist-Modus | boolean |
+| `--dataRoot` | Stammverzeichnis für Datenspeicherung | string |
+| `--avoidLocalhost` | Vermeidet die Verwendung von „localhost“ für Autorun im Auto-Modus. | boolean |
+| `--basicAuthMode` | Aktiviert die grundlegende Authentifizierung | boolean |
+| `--requestProxyEnabled` | Aktiviert die Verwendung eines Proxys für ausgehende Anfragen | boolean |
+| `--requestProxyUrl` | Proxy-URL anfordern (HTTP- oder SOCKS-Protokolle) | string |
+| `--requestProxyBypass` | Proxy-Bypass-Liste anfordern (durch Leerzeichen getrennte Liste von Hosts) | Array |
+
+## Remoteverbindungen
+
+Dies ist in den meisten Fällen für Personen gedacht, die SillyTavern auf ihren Mobiltelefonen verwenden möchten, während ihr PC den ST-Server im selben WLAN-Netzwerk betreibt. Es kann jedoch auch verwendet werden, um Remoteverbindungen von überall her zu ermöglichen.
+
+Lies die ausführliche Anleitung zum Einrichten von Remoteverbindungen in den [Docs](https://docs.sillytavern.app/usage/remoteconnections/).
+
+Möglicherweise möchtest du SillyTavern-Benutzerprofile auch mit (optionalem) Kennwortschutz konfigurieren: [Benutzer](https://docs.sillytavern.app/installation/st-1.12.0-migration-guide/#users).
+
+## Leistungsprobleme?
+
+1. Deaktiviere den Unschärfeeffekt und aktiviere "Verringerte Bewegung" im Bedienfeld "Benutzereinstellungen" (UI-Design schaltet Kategorie um).
+2. Wenn du Response Streaming verwendest, stelle die Streaming-FPS auf einen niedrigeren Wert ein (10-15 FPS werden empfohlen).
+3. Stelle sicher, dass der Browser die GPU-Beschleunigung zum Rendern verwenden kann.
+
+## Lizenz und Danksagungen
+
+**Dieses Programm wird in der Hoffnung verbreitet, dass es nützlich ist,  
+aber OHNE JEGLICHE GARANTIE; nicht einmal die stillschweigende Garantie der  
+MARKTFÄHIGKEIT oder EIGNUNG FÜR EINEN BESTIMMTEN ZWECK. Siehe die  
+GNU Affero General Public License für weitere Details.**
+
+* [TavernAI](https://github.com/TavernAI/TavernAI) 1.2.8 von Humi: MIT-Lizenz
+* Teile von CncAnons TavernAITurbo-Mod werden mit Genehmigung verwendet
+* Visual Novel-Modus inspiriert von der Arbeit von PepperTaco (<https://github.com/peppertaco/Tavern/>)
+* Noto Sans-Schriftart von Google (OFL-Lizenz)
+* Symboldesign von Font Awesome <https://fontawesome.com> (Symbole: CC BY 4.0, Schriftarten: SIL OFL 1.1, Code: MIT-Lizenz)
+* Standardinhalt von @OtisAlejandro (Seraphina-Charakter und Lorebook) und @kallmeflocc (10.000 Discord-Benutzer-Feierhintergrund)
+* Docker-Anleitung von [@mrguymiah](https://github.com/mrguymiah) und [@Bronya-Rand](https://github.com/Bronya-Rand)
+
+## Top Contributors
+
+[![Contributors](https://contrib.rocks/image?repo=SillyTavern/SillyTavern)](https://github.com/SillyTavern/SillyTavern/graphs/contributors)
+
+<!-- LINK GROUP -->
+[cover]: https://github.com/user-attachments/assets/01a6ae9a-16aa-45f2-8bff-32b5dc587e44
+[discord-link]: https://discord.gg/sillytavern
+[discord-shield-badge]: https://img.shields.io/discord/1100685673633153084?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge

jiuguan2025cc/.github/readme-ja_jp.md

@@ -0,0 +1,330 @@
+> [!IMPORTANT]  
+> ここに掲載されている情報は、古かったり不完全であったりする可能性があります。最新の情報は英語版をご利用ください。
+
+![][cover]
+
+<div align="center">
+
+[English](readme.md) | [German](readme-de_de.md) | [中文](readme-zh_cn.md) | [繁體中文](readme-zh_tw.md) | 日本語 | [Русский](readme-ru_ru.md) | [한국어](readme-ko_kr.md)
+
+[![GitHub Stars](https://img.shields.io/github/stars/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/stargazers)
+[![GitHub Forks](https://img.shields.io/github/forks/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/network)
+[![GitHub Issues](https://img.shields.io/github/issues/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/issues)
+[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/pulls)
+
+</div>
+
+---
+
+モバイルデバイスにも適したレイアウト・マルチAPI（KoboldAI/CPP、Horde、NovelAI、Ooba、OpenAI、OpenRouter、Claude、Scale）、VN ライクな Waifu モード、Stable Diffusion、TTS、WorldInfo（伝承本）、カスタマイズ可能なUI、自動翻訳、大量のプロンプトオプション＋サードパーティの拡張機能をインストールする機能
+
+[TavernAI](https://github.com/TavernAI/TavernAI) v.1.2.8 のフォークに基づいています。
+
+## 重要事項
+
+1. 私たちは[ドキュメントウェブサイト](https://docs.sillytavern.app/) を作成し、ほとんどの質問にお答えしています。
+
+2. アップデートしたら使っていた拡張機能を見失いましたか？リリースバージョン 1.10.6 以降、これまで内蔵されていた拡張機能のほとんどがダウンロード可能なアドオンに変更されました。ダウンロードは、拡張機能パネル（トップバーのスタックドブロックアイコン）にある内蔵の "Download Extensions and Assets" メニューから行えます。
+
+### Cohee、RossAscends、SillyTavern コミュニティがお届けします
+
+### SillyTavern または TavernAI とは何ですか？
+
+SillyTavern は、あなたのコンピュータ（および Android スマホ）にインストールできるユーザーインターフェイスで、テキスト生成 AI と対話したり、あなたやコミュニティが作成したキャラクターとチャットやロールプレイをすることができます。
+
+SillyTavern は TavernAI 1.2.8 のフォークで、より活発な開発が行われており、多くの主要な機能が追加されています。現時点では、これらは完全に独立したプログラムと考えることができます。
+
+### ブランチ
+
+SillyTavern は、すべてのユーザーにスムーズな体験を保証するために、2 つのブランチシステムを使用して開発されています。
+
+* release -🌟 **ほとんどのユーザーにお勧め。** これは最も安定した推奨ブランチで、メジャーリリースがプッシュされた時のみ更新されます。大半のユーザーに適しています。
+* staging - ⚠️ **カジュアルな使用にはお勧めしない。** このブランチには最新の機能がありますが、いつ壊れるかわからないので注意してください。パワーユーザーとマニア向けです。
+
+git CLI の使い方に慣れていなかったり、ブランチが何なのかわからなかったりしても、心配はいりません！releaseブランチが良い選択肢となります。
+
+### Tavern 以外に何が必要ですか？
+
+Tavern は単なるユーザーインターフェイスなので、それだけでは何もできません。ロールプレイキャラクターとして機能する AI システムのバックエンドにアクセスする必要があります。様々なバックエンドがサポートされています。リストはこちらです： OpenAPI API (GPT)、KoboldAI (ローカルまたは Google Colab 上で動作)、その他。詳しくは [FAQ](https://docs.sillytavern.app/usage/faq/) をご覧ください。
+
+### Tavern を実行するには、ハイスペックなPCが必要ですか？
+
+Tavern は単なるフロントエンドのUIであり、必要なハードウェアはごくわずかです。パワフルである必要があるのは、AI システムのバックエンドです。
+
+## モバイルサポート
+
+> **注**
+
+> **このフォークは Termux を使って Android スマホで実行できます。ArroganceComplex#2659 のガイドを参照してください:**
+
+<https://rentry.org/STAI-Termux>
+
+## ご質問やご提案
+
+### コミュニティ Discord サーバーを開設しました
+
+サポートを受けたり、作成したキャラを共有したり、コミュニティの作ったキャラと遊びたいですか？:
+
+### [参加](https://discord.gg/RZdyAEUPvj)
+
+***
+
+開発者と直接連絡:
+
+* Discord: cohee または rossascends
+* Reddit: /u/RossAscends または /u/sillylossy
+* [GitHub issue を投稿](https://github.com/SillyTavern/SillyTavern/issues)
+
+## このバージョンには以下のコードが含まれます
+
+* 大幅に修正された TavernAI 1.2.8 (コードの 50% 以上が書き換えまたは最適化されています)
+* スワイプ
+* グループチャット: キャラクター同士が会話できるマルチボットルーム
+* チャットチェックポイント / ブランチ
+* 高度なKoboldAI / TextGen生成設定と、コミュニティが作成した多くのプリセット
+* ワールド情報サポート: 豊富な伝承を作成したり、キャラクターカードにトークンを保存したりできます
+* [OpenRouter](https://openrouter.ai) 各種 API(Claude、GPT-4/3.5 など)の接続
+* [Oobabooga's TextGen WebUI](https://github.com/oobabooga/text-generation-webui) API 接続
+* [AI Horde](https://aihorde.net/) 接続
+* プロンプト生成フォーマットの調整
+
+## 拡張機能
+
+SillyTavern は拡張できるようになっており。
+
+* キャラクターの感情表現（スプライト）
+* チャット履歴の自動サマリー
+* チャットに画像を送り、AI が内容を解釈する
+* Stable Diffusion 画像生成 (5 つのチャット関連プリセットと 'free mode')
+* AI 応答メッセージの音声合成（ElevenLabs、Silero、または OS のシステム TTS 経由）
+
+含まれている拡張機能の完全なリストとその使い方のチュートリアルは [Docs](https://docs.sillytavern.app/) にあります。
+
+## RossAscends による UI/CSS/クオリティオブライフの調整
+
+* iOS 用に最適化されたモバイル UI で、ホーム画面へのショートカット保存とフルスクリーンモードでの起動をサポート。
+* ホットキー
+  * Up = チャットの最後のメッセージを編集する
+  * Ctrl+Up = チャットで最後のユーザーメッセージを編集する
+  * Left = 左スワイプ
+  * Right = 右スワイプ (注: チャットバーに何か入力されている場合、スワイプホットキーが無効になります)
+  * Ctrl+Left = ローカルに保存された変数を見る（ブラウザのコンソールウィンドウにて）
+  * Enter (チャットバー選択時) = AI にメッセージを送る
+  * Ctrl+Enter = 最後の AIのレスポンスを再生成する
+
+* ユーザー名の変更と文字の削除でページが更新されなくなりました。
+
+* ページロード時に API に自動的に接続するかどうかを切り替えます。
+* ページの読み込み時に、最近見た文字を自動的に読み込むかどうかを切り替えます。
+* より良いトークンカウンター - 保存されていないキャラクターに対して機能し、永続的なトークンと一時的なトークンの両方を表示する。
+
+* より良い過去のチャット
+  * 新しいチャットのファイル名は、"(文字) - (作成日)" という読みやすい形式で保存されます
+  * チャットのプレビューが 40 文字から 300 文字に増加。
+  * 文字リストの並べ替えに複数のオプション（名前順、作成日順、チャットサイズ順）があります。
+
+* デフォルトでは、左右の設定パネルはクリックすると閉じます。
+* ナビパネルのロックをクリックすると、パネルが開いたままになり、この設定はセッションをまたいで記憶されます。
+* ナビパネルの開閉状態もセッションをまたいで保存されます。
+
+* カスタマイズ可能なチャット UI:
+  * 新しいメッセージが届いたときにサウンドを再生する
+  * 丸型、長方形のアバタースタイルの切り替え
+  * デスクトップのチャットウィンドウを広くする
+  * オプションの半透明ガラス風パネル
+  * 'メインテキスト'、'引用テキスト'、'斜体テキスト'のページカラーをカスタマイズ可能。
+  * カスタマイズ可能な UI 背景色とぼかし量
+
+## インストール
+
+*注: このソフトウェアはローカルにインストールすることを目的としており、colab や他のクラウドノートブックサービス上では十分にテストされていません。*
+
+> **警告**
+
+> WINDOWS が管理しているフォルダ（Program Files、System32 など）にはインストールしないでください
+
+> START.BAT を管理者権限で実行しないでください
+
+### Windows
+
+Git 経由でのインストール（更新を容易にするため推奨）
+
+写真付きのわかりやすいガイドはこちらです:
+<https://docs.sillytavern.app/installation/windows/>
+
+  1. [NodeJS](https://nodejs.org/en) をインストール(最新の LTS 版を推奨)
+  2. [GitHub Desktop](https://central.github.com/deployments/desktop/desktop/latest/win32) をインストールする
+  3. Windows エクスプローラーを開く (`Win+E`)
+  4. Windows によって制御または監視されていないフォルダを参照または作成する。（例: C:\MySpecialFolder\）
+  5. 上部のアドレスバーをクリックし、`cmd` と入力して Enter キーを押し、そのフォルダーの中にコマンドプロンプトを開きます。
+  6. 黒いボックス（コマンドプロンプト）がポップアップしたら、そこに以下のいずれかを入力し、Enter を押します:
+
+* Release ブランチの場合: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+* Staging ブランチの場合: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+  7. すべてをクローンしたら、`Start.bat` をダブルクリックして、NodeJS に要件をインストールさせる。
+  8. サーバーが起動し、SillyTavern がブラウザにポップアップ表示されます。
+
+ZIP ダウンロードによるインストール（推奨しない）
+
+  1. [NodeJS](https://nodejs.org/en) をインストールする(最新の LTS 版を推奨)
+  2. GitHub のリポジトリから zip をダウンロードする。(`ソースコード(zip)` は [Releases](https://github.com/SillyTavern/SillyTavern/releases/latest) から入手)
+  3. お好きなフォルダに解凍してください
+  4. `Start.bat` をダブルクリックまたはコマンドラインで実行する。
+  5. サーバーが準備できれば、ブラウザのタブを開きます。
+
+### Linux
+
+  1. `node -v` を実行して、Node.js v18 以上（最新の [LTS バージョン](https://nodejs.org/en/download/) を推奨）がインストールされていることを確認してください。
+または、[Node Version Manager](https://github.com/nvm-sh/nvm#installing-and-updating) スクリプトを使用して、迅速かつ簡単に Node のインストールを管理します。
+  2. `start.sh` スクリプトを実行する。
+  3. お楽しみください。
+
+## API キー管理
+
+SillyTavern は API キーをサーバーディレクトリの `secrets.json` ファイルに保存します。
+
+デフォルトでは、入力後にページをリロードしても、フロントエンドには表示されません。
+
+API ブロックのボタンをクリックして、キーを閲覧できるようにする:
+
+1. ファイル `config.yaml` で `allowKeysExposure` の値を `true` に設定する。
+2. SillyTavern サーバを再起動します。
+
+## リモート接続
+
+SillyTavern をスマホで使用しながら、同じ Wifi ネットワーク上で ST サーバーを PC で実行したい場合に使用します。
+
+しかし、これはどこからでもリモート接続を許可するために使用することができます。
+
+**重要: SillyTavern はシングルユーザーのプログラムなので、ログインすれば誰でもすべてのキャラクターとチャットを見ることができ、UI 内で設定を変更することができます。**
+
+### 1. ホワイトリスト IP の管理
+
+* SillyTavern のベースインストールフォルダ内に `whitelist.txt` という新しいテキストファイルを作成します。
+* テキストエディタでこのファイルを開き、接続を許可したい IP のリストを追加します。
+
+*個々の IP とワイルドカード IP 範囲の両方が受け入れられる。例:*
+
+```txt
+192.168.0.1
+192.168.0.20
+```
+
+または
+
+```txt
+192.168.0.*
+```
+
+(上記のワイルドカード IP 範囲は、ローカルネットワーク上のどのデバイスでも)
+
+CIDR マスクも受け付ける（例：10.0.0.0/24）。
+
+* `whitelist.txt` ファイルを保存する。
+* TAI サーバーを再起動する。
+
+これでファイルに指定された IP を持つデバイスが接続できるようになります。
+
+*注: `config.yaml` にも `whitelist` 配列があり、同じように使うことができるが、`whitelist.txt` が存在する場合、この配列は無視される。*
+
+### 2. ST ホストマシンの IP の取得
+
+ホワイトリストの設定後、ST ホストデバイスの IP が必要になります。
+
+ST ホストデバイスが同じ無線 LAN ネットワーク上にある場合、ST ホストの内部無線 LAN IP を使用します:
+
+* Windows の場合: ウィンドウズボタン > 検索バーに `cmd.exe` と入力 > コンソールに `ipconfig` と入力して Enter > `IPv4` のリストを探す。
+
+同じネットワーク上にいない状態で、ホストしているSTに接続したい場合は、STホスト機器のパブリックIPが必要です。
+
+* ST ホストデバイスを使用中に、[このページ](https://whatismyipaddress.com/)にアクセスし、`IPv4` を探してください。これはリモートデバイスからの接続に使用するものです。
+
+### 3. リモートデバイスを ST ���ストマシンに接続します。
+
+最終的に使用する IP が何であれ、その IP アドレスとポート番号をリモートデバイスのウェブブラウザに入力します。
+
+同じ無線 LAN ネットワーク上の ST ホストの典型的なアドレスは以下のようになります:
+
+`http://192.168.0.5:8000`
+
+http:// を使用し、https:// は使用しないでください
+
+### ST をすべての IP に開放する
+
+これはお勧めしませんが、`config.yaml` を開き、`whitelistMode` を `false` に変更してください。
+
+SillyTavern のベースインストールフォルダにある `whitelist.txt` が存在する場合は削除（または名前の変更）する必要があります。
+
+これは通常安全ではないので、これを行う際にはユーザー名とパスワードを設定する必要があります。
+
+ユーザー名とパスワードは `config.yaml` で設定します。
+
+ST サーバを再起動すると、ユーザ名とパスワードさえ知っていれば、IP に関係なくどのデバイスでも ST サーバに接続できるようになる。
+
+### まだ接続できませんか？
+
+* `config.yaml` で見つかったポートに対して、インバウンド/アウトバウンドのファイアウォールルールを作成します。これをルーターのポートフォワーディングと間違えないでください。そうしないと、誰かがあなたのチャットログを見つける可能性があり、それはマジで止めましょう。
+* 設定 > ネットワークとインターネット > イーサネットで、プライベートネットワークのプロファイルタイプを有効にします。そうしないと、前述のファイアウォールルールを使っても接続できません。
+
+## パフォーマンスに問題がありますか？
+
+ユーザー設定パネルでブラー効果なし（高速 UI）モードを有効にしてみてください。
+
+## このプロジェクトが気に入りました！どうすれば貢献できますか？
+
+### やるべきこと
+
+1. プルリクエストを送る
+2. 確立されたテンプレートを使って機能提案と課題レポートを送る
+3. 何か質問する前に、readme ファイルや組み込みのドキュメントを読んでください
+
+### やるべきではないこと
+
+1. 金銭の寄付を申し出る
+2. 何の脈絡もなくバグ報告を送る
+3. すでに何度も回答されている質問をする
+
+## 古い背景画像はどこにありますか？
+
+100％ オリジナルコンテンツのみのポリシーに移行しているため、古い背景画像はこのリポジトリから削除されました。
+
+アーカイブはこちら:
+
+<https://files.catbox.moe/1xevnc.zip>
+
+## スクリーンショット
+
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/9b5f32f0-c3b3-4102-b3f5-0e9213c0f50f">
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/913fdbaa-7d33-42f1-ae2c-89dca41c53d1">
+
+## ライセンスとクレジット
+
+**このプログラムは有用であることを願って配布されていますが、いかなる保証もありません;
+また、商品性または特定目的への適合性についての黙示の保証もありません。
+詳細は GNU Affero General Public License をご覧ください。**
+
+* Humi によるTAI Base: 不明ライセンス
+* Cohee の修正と派生コード: AGPL v3
+* RossAscends の追加: AGPL v3
+* CncAnon の TavernAITurbo 改造の一部: 不明ライセンス
+* kingbri のさまざまなコミットと提案 (<https://github.com/bdashore3>)
+* city_unit の拡張機能と様々な QoL 機能 (<https://github.com/city-unit>)
+* StefanDanielSchwarz のさまざまなコミットとバグ報告 (<https://github.com/StefanDanielSchwarz>)
+* PepperTaco の作品にインスパイアされた Waifu モード (<https:/fugithub.com/peppertaco/Tavern/>)
+* ピグマリオン大学の皆さん、素晴らしいテスターとしてクールな機能を提案してくれてありがとう！
+* TextGen のプリセットをコンパイルしてくれた obabooga に感謝
+* KAI Lite の KoboldAI プリセット: <https://lite.koboldai.net/>
+* Google による Noto Sans フォント（OFLライセンス）
+* Font Awesome によるアイコンテーマ <https://fontawesome.com> (アイコン: CC BY 4.0、フォント: SIL OFL 1.1、コード: MIT License)
+* ZeldaFan0225 による AI Horde クライアントライブラリ: <https://github.com/ZeldaFan0225/ai_horde>
+* AlpinDale による Linux 起動スクリプト
+* FAQ を提供してくれた paniphons に感謝
+* 10K ディスコード・ユーザー記念背景 by @kallmeflocc
+* デフォルトコンテンツ（キャラクターと伝承書）の提供: @OtisAlejandro、@RossAscends、@kallmeflocc
+* @doloroushyeonse による韓国語翻訳
+* k_euler_a による Horde のサポート <https://github.com/Teashrock>
+* [@XXpE3](https://github.com/XXpE3) による中国語翻訳、中国語 ISSUES の連絡先は @XXpE3
+
+<!-- LINK GROUP -->
+[cover]: https://github.com/user-attachments/assets/01a6ae9a-16aa-45f2-8bff-32b5dc587e44

jiuguan2025cc/.github/readme-ko_kr.md

@@ -0,0 +1,394 @@
+> [!IMPORTANT]
+> 이곳에 게재된 정보는 오래되거나 불완전할 수 있습니다. 최신 정보는 영어 버전을 이용하십시오.
+
+<a name="readme-top"></a>
+
+![][cover]
+
+<div align="center">
+
+[English](readme.md) | [German](readme-de_de.md) | [中文](readme-zh_cn.md) | [繁體中文](readme-zh_tw.md) | [日本語](readme-ja_jp.md) | [Русский](readme-ru_ru.md) | 한국어
+
+[![GitHub Stars](https://img.shields.io/github/stars/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/stargazers)
+[![GitHub Forks](https://img.shields.io/github/forks/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/network)
+[![GitHub Issues](https://img.shields.io/github/issues/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/issues)
+[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/pulls)
+
+</div>
+
+---
+
+SillyTavern은 많은 LLM API(KoboldAI/CPP, Horde, NovelAI, Ooba, Tabby, OpenAI, OpenRouter, Claude, Mistral 등)에 대한 단일 통합 인터페이스, 모바일 친화적 레이아웃, 비주얼 노벨 모드, Automatic1111 & ComfyUI API 이미지 생성 통합, TTS, 월드 인포 (로어북), 커스텀 가능한 UI, 자동 번역, 필요 이상의 프롬프트 옵션, 그리고 서드파티 확장을 통한 무궁무진한 성장 가능성을 제공합니다.
+
+또한, 자주 묻는 질문에 대한 답변과, 시작하는 데 도움을 주기 위한 [문서 웹사이트](https://docs.sillytavern.app/)가 있습니다.
+
+## SillyTavern이 무엇인가요?
+
+SillyTavern(짧게는 ST)은 텍스트 생성 LLM, 이미지 생성 엔진, TTS 음성 모델 등과 상호작할 수 있는 로컬 설치형 UI 입니다.
+
+2023년 2월, TavernAI 1.2.8의 포크로 시작한 SillyTavern은 현재 100명이 넘는 기여자를 보유하고 있으며, 2년간의 독자적인 개발을 거쳐 숙련된 AI 애호가들을 위한 선도적인 소프트웨어로 자리매김하고 있습니다.
+
+
+## 우리의 비전
+
+1. 저희는 사용자가 LLM 프롬프트에 대한 최대한의 유용성과 제어 능력을 갖도록 하는 것을 목표로 합니다. 빠르게 배우는 것 역시 재미의 일부입니다!
+2. 저희는 어떠한 온라인 및 호스팅 서브시도 제공하지 않으며, 프로그래밍으로 사용자의 데이터를 추적하지 않습니다.
+3. SillyTavern은 헌신적인 LLM 커뮤니티가 여러분에게 제공하는 열정적인 프로젝트이며, 언제나 무료이며 오픈소스로 제공될 것입니다.
+
+## 브랜치
+
+SillyTavern은 모든 사용자가 원활한 경험을 할 수 있도록 두 개의 브랜치를 활용하여 개발되고 있습니다.
+
+
+* `release` -🌟 **대부분의 사용자에게 추천됨.** 가장 안정적이고 권장되는 브랜치이며, 주요 릴리스가 배포될 때만 업데이트됩니다. 대부분의 사용자에게 적합합니다. 일반적으로 한달에 한번 업데이트됩니다.
+* `staging` - ⚠️ **일반적인 사용에 추천되지 않음.** 최신 기능을 가지고 있지만, 언제든지 문제가 발생할 수 있습니다. 고급 사용자 및 숙련자 전용입니다. 하루에 여러번 업데이트됩니다.
+
+만약 git CLI 사용에 익숙하지 않거나 브랜치가 무엇인지 모르겠다면 release 브랜치가 더 나은 선택입니다.
+
+## SillyTavern 외에 무엇이 필요한가요?
+
+SillyTavern은 인터페이스 역할만 하기 때문에, 실제로 채팅하려면 LLM 백엔드에 대한 액세스 권한이 필요합니다. 즉시 사용 가능한 채팅을 위해 AI Horde를 사용할 수 있습니다. 그 외에도 OpenAI 호환 API, KoboldAI, Tabby 등 많은 로컬 및 클라우드 기반 LLM 백엔드를 지원합니다. 지원되는 API에 대한 자세한 내용은 [FAQ](https://docs.sillytavern.app/usage/api-connections/)에서 확인할 수 있습니다.
+
+### SillyTavern을 위해서 좋은 성능의 PC가 필요한가요?
+
+하드웨어 요구 사항은 거의 없습니다: NodeJS 18 이상을 실행할 수 있는 모든 환경에서 작동합니다. 다만 로컬 LLM 모델을 사용할 경우, 최소 6GB VRAM 이상의 3000번대 NVIDIA 그래픽 카드를 권장합니다. 자세한 내용은 백엔드 문서를 참고하세요.
+
+### 추천되는 백엔드 (제휴 없음)
+
+* [AI Horde](https://aihorde.net/) - 자원 봉사자들이 호스팅하는 모델을 사용합니다. 추가 설정이 필요하지 않습니다.
+* [KoboldCpp](https://github.com/LostRuins/koboldcpp) - 로컬에서 GGUF 모델을 실행하기 위한 커뮤니티에서 선호하는 옵션입니다.
+* [tabbyAPI](https://github.com/theroyallab/tabbyAPI) - 인기 있는 경량 로컬  exl2 추론 API입니다.
+* [OpenRouter](https://openrouter.ai) - OpenAI, Claude, Meta Llama 등 다양한 클라우드 제공업체와 인기 있는 커뮤니티 모델을 위한 단일 API입니다.
+
+## 질문이나 제안이 있으신가���?
+
+### 디스코드 서버
+
+| [![][discord-shield-badge]][discord-link] | [저희의 디스코드에 참여하세요!](https://discord.gg/sillytavern) 지원을 받고, 좋아하는 캐릭터와 프롬프트를 공유하세요. |
+| :---------------------------------------- | :----------------------------------------------------------------------------------------------------------------- |
+
+혹은 저희의 개발자들과 직접 연락할 수 있습니다:
+
+* 디스코드: cohee, rossascends, wolfsblvt
+* 레딧: [/u/RossAscends](https://www.reddit.com/user/RossAscends/), [/u/sillylossy](https://www.reddit.com/user/sillylossy/), [u/Wolfsblvt](https://www.reddit.com/user/Wolfsblvt/)
+* [GitHub issue를 작성하세요](https://github.com/SillyTavern/SillyTavern/issues)
+
+### 이 프로젝트가 마음에 들어요! 어떻게 기여할 수 있을까요?
+
+1. PULL REQUEST를 생성하세요. 기여 방법에 대해서는 [CONTRIBUTING.md](../CONTRIBUTING.md)를 참고하세요.
+2. 제공된 탬플릿에 따라 기능 제안이나 이슈 리포트를 생성하세요.
+3. 중복된 이슈를 생성하지 않도록 이 README 파일 전체를 읽고 문서 웹사이트를 먼저 확인하세요.
+
+## 스크린샷
+
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/9b5f32f0-c3b3-4102-b3f5-0e9213c0f50f">
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/913fdbaa-7d33-42f1-ae2c-89dca41c53d1">
+
+
+## 캐릭터 카드
+
+SillyTavern은 "캐릭터 카드"라는 개념을 중심으로 구축되었습니다. 캐릭터 카드는 LLM의 동작을 설정하는 프롬프트 모음이며, SillyTavern에서 지속적인 대화를 하려면 필수적입니다. 이는 ChatGPT의 GPT 또는 Poe의 봇과 유사하게 작동합니다. 캐릭터 카드의 내용은 추상적인 시나리오, 특정 작업에 맞춰진 도우미, 유명 인사 또는 가상 인물 등 무엇이든 될 수 있습니다.
+
+이름 필드는 유일한 필수 캐릭터 카드 입력 항목입니다. 언어 모델과 중립적인 대화를 시작하려면 "도우미"라고 간단히 이름 지은 새 카드를 만들고 나머지 상자는 비워 두세요. 더 주제가 있는 채팅을 원한다면 언어 모델에 다양한 배경 정보, 행동 및 작문 패턴, 그리고 채팅을 바로 시작할 시나리오를 제공할 수 있습니다.
+
+캐릭터 카드를 선택하지 않고 빠른 대화를 하거나 LLM 연결을 테스트하려면 SillyTavern을 연 후 시작 화면의 입력 창에 프롬프트 입력을 입력하기만 하면 됩니다. 이러한 채팅은 임시적이며 저장되지 않습니다.
+
+캐릭터 카드를 정의하는 방법에 대한 일반적인 아이디어를 얻으려면 기본 캐릭터(Seraphina)를 보거나 "확장 프로그램 및 에셋 다운로드" 메뉴에서 선택된 커뮤니티 제작 카드를 다운로드하세요.
+
+
+## 핵심 기능
+
+* 고급 텍스트 생성 설정과 다양한 커뮤니티 제작 프리셋
+* 월드 인포 지원: 풍부한 설정을 만들거나 캐릭터 카드에 토큰 저장
+* 그룹 채팅: 캐릭터가 사용자 혹은 다른 캐릭터와 대화할 수 있는 방
+* 다양한 UI 커스텀 옵션: 테마 색, 뱌경 이미지, 커스텀 CSS 등
+* 유저 페르소나: AI에게 사용자에 대한 정보를 주어 더욱 몰입감을 높임
+* 내장 RAG 지원: AI가 참조할 수 있도록 채팅에 문서를 추가
+* 광범위한 채팅 명령어 시스템 및 자체 [스크립트](https://docs.sillytavern.app/usage/st-script/)
+
+## 확장
+
+SillyTavern은 확장(익스텐션)을 지원합니다.
+
+* 캐릭터 감정 표현 (스프라이트)
+* 채팅 기록 자동 요약
+* 자동 UI 및 채팅 번역
+* Stable Diffusion/FLUX/DALL-E 이미지 생성
+* AI 응답 메시지 텍스트 음성 변환 (ElevenLabs, Silero 또는 OS 시스템 TTS 사용)
+* 프롬프트에 추가적인 현실 세계 맥락을 추가하기 위한 웹 검색 기능
+* "확장 프로그램 및 에셋 다운로드" 메뉴에서 더 많은 기능을 다운로드할 수 있습니다.
+
+
+사용 방법에 대한 튜토리얼은 [Docs](https://docs.sillytavern.app/)에서 확인할 수 있습니다.
+
+# ⌛ Installation
+
+> \[!WARNING]
+>
+> * **윈도우 제어 폴더에는 설치하지 마십시오 (Program Files, System32 등).**
+> * **권리자 권한으로 START.BAT을 실행하지 마십시오.**
+> * **Windows 7에서는 NodeJS 18.16을 실행할 수 없으므로 설치가 불가능합니다.**
+
+## 🪟 Windows
+
+### Git을 통해 설치하기
+
+1. [NodeJS](https://nodejs.org/ko) 설치 (최신 LTS 버전 권장)
+2. [Git for Windows](https://gitforwindows.org/) 설치
+3. 파일 탐색기 열기 (`Win+E`)
+4. Windows에서 제어하거나 모니터하지 않는 폴더를 찾거나 만드세요. (ex: C:\MySpecialFolder\)
+5. 상단의 주소 표시줄을 클릭하고 `cmd`를 입력한 후 Enter 키를 눌러 해당 폴더 내에서 명령 프롬프트를 여세요.
+6. 검은색 창(명령 프롬프트)이 나타나면 다음 중 하나를 입력하고 Enter 키를 누르세요.
+
+* Release 브랜치: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+* Staging 브랜치: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+7. clone이 완료되면, `Start.bat`을 더블 클릭하여 NodeJS가 필요한 구성요소를 설치하도록 하세요.
+8. 그러면 서버가 시작하고, SillyTavern이 브라우저에 나타납니다.
+
+### GitHub Desktop을 통해 설치하기
+
+(이 방법은 **오직** GitHub Desktop에서만 git 사용이 가능합니다. 명령 프롬프트에서 git을 사용하려면 [Git for Windows](https://gitforwindows.org/)를 설치해야 합니다.)
+
+ 
+
+  1. [NodeJS](https://nodejs.org/ko) 설치 (최신 LTS 버전 권장)
+  2. [GitHub Desktop](https://central.github.com/deployments/desktop/desktop/latest/win32) 설치
+  3. GitHub Desktop을 설치했으면, `Clone a repository from the internet....`를 클릭하세요. (참고: 이 과정에서는 Github 계정이 **필요하지 않습니다**.)
+  4. 메뉴에서 URL 탭을 클릭하고, 다음 URL을 입력한 후 복제를 클릭합니다: `https://github.com/SillyTavern/SillyTavern` 리포지토리가 다운로드될 위치를 변경하려면 로컬 경로를 변경할 수 있습니다.
+  5. SillyTavern을 열려면 파일 탐색기를 사용하여 리포지토리를 복제한 폴더로 이동합니다. 기본적으로 리포지토리는 다음 위치에 복제됩니다: `C:\Users\[사용자 Windows 사용자 이름]\Documents\GitHub\SillyTavern`
+  6. `start.bat` 파일을 더블 클릭 하세요. (참고: `.bat` 확장자 명은 OS 설정에 따라 보이지 않을 수 있습니다, 그럴 때는 파일 이름이 "`Start`" 처럼 보일 수 있습니다. 이 파일을 더블 클릭해 SillyTavern을 실행하세요.)
+  7. 더블 클릭하면, 검고 큰 명령 프롬프트 창이 열리고 SillyTavern이 작동하는데 필요한 항목을 설치하기 시작합니다.
+  8. 설치 과정이 끝나고 모든 것이 잘 작동한다면, 브라우저에 SillyTavern 탭이 열려 있어야 하고, 명령 프롬프트 창에 다음과 같이 표시되어야 합니다:
+  9. Connect to any of the [supported APIs](https://docs.sillytavern.app/usage/api-connections/) and start chatting!
+
+## 🐧 Linux & 🍎 MacOS
+
+MacOS / Linux 에서는 이 모든 작업이 터미널에서 수행됩니다.
+
+1. git과 nodeJS 설치 (이 작업은 OS에 따라 달라집니다.)
+2. 리포지토리 clone하기
+
+* Release 브랜치: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+*  Staging 브랜치: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+3. `cd SillyTavern` 를 입력해 설치 폴더로 이동하기
+4. `start.sh` 스크립트를 아래의 명령어 중 하나로 실행하기:
+
+* `./start.sh`
+* `bash start.sh`
+
+## ⚡ SillyTavern Launcher를 통해 설치하기
+
+SillyTavern 런처는 로컬 LLM 사용을 위한 백엔드 설치를 포함하여 다양한 설정을 도와주는 설치 마법사입니다.
+
+
+### Windows 사용자
+
+1. 키보드에서 **`WINDOWS + R`** 키를 눌러 실행 창을 여세요. 그리고 아래의 명령어를 입력해 git을 설치하세요.
+
+```shell
+cmd /c winget install -e --id Git.Git
+```
+
+2. 키보드에서 **`WINDOWS + E`** 키를 눌러 파일 탐색기를 열고 런처를 설치할 폴더로 이동합니다. 원하는 폴더에 도착하면 주소 표시줄에 `cmd`를 입력하고 Enter 키를 누릅니다. 그 후 아래의 명령어를 입력합니다.
+
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher && start installer.bat
+```
+
+### Linux 사용자
+
+1. 선호하는 터미널을 열고 git을 설치하세요.
+2. SillyTavern-Launcher를 clone 하세요:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+3. installer.sh를 실행하세요:
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+4. 설치가 끝나면 launcher.sh를 실행하세요:
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+### Mac 사용자
+
+1. 터미널을 열고 Brew를 설치하세요:
+
+```shell
+/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+```
+
+2. git을 설치하세요:
+
+```shell
+brew install git
+```
+
+3. SillyTavern-Launcher를 clone 하세요:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+4. installer.sh를 실행하세요:
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+5. 설치가 끝나면 launcher.sh를 실행하세요:
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+## 🐋 Docker를 통해 설치하기
+
+이 방법은 Docker가 설치되어 있고, Docker 설치를 위해 커맨드 라인에 접근할 수 있으며, Docker의 일반적인 작동 방식에 익숙하다고 가정합니다.
+
+### 이미지 직접 빌드하기
+
+SillyTavern을 Docker에서 사용���는 방법에 대한 포괄적인 가이드는 [여기서](http://docs.sillytavern.app/installation/docker/) 확인할 수 있습니다. 이 가이드는 Windows, macOS 및 Linux에서의 설치를 다룹니다! 직접 이미지를 빌드하려면 이 가이드를 읽어보세요.
+
+### GitHub Container Registry 사용하기 (가장 쉬움)
+
+SillyTavern이 작동하려면 두 개의 필수 디렉터리 매핑과 하나의 포트 매핑이 필요합니다. 명령에서 다음 위치의 선택 항목을 바꿔주세요.
+
+
+#### Container Variables
+
+##### Volume Mappings
+
+* [config] - SillyTavern 구성 파일이 호스트 컴퓨터에 저장될 디렉터리
+* [data] - 캐릭터를 포함한 SillyTavern 사용자 데이터가 호스트 컴퓨터에 저장될 디렉터리
+* [plugins] - (선택 사항) SillyTavern 서버 플러그인이 호스트 컴퓨터에 저장될 디렉터리
+
+##### Port Mappings
+
+* [PublicPort] - 트래픽을 노출할 포트입니다. 가상 머신 컨테이너 외부에서 인스턴스에 접근하므로 필수 사항입니다. 보안을 위한 별도의 서비스를 구현하지 않고는 인터넷에 노출하지 마십시오.
+
+
+##### Additional Settings
+
+* [DockerNet] - 컨테이너가 연결되어 생성되어야 하는 Docker 네트워크입니다. 해당 내용을 모르는 경우 [공식 Docker 문서](https://docs.docker.com/reference/cli/docker/network/)를 참조하세요.
+* [version] - 이 GitHub 페이지의 오른쪽에서 "Packages"를 선택하면 "sillytavern" 패키지를 볼 수 있습니다. "latest" 이미지 태그는 현재 릴리스와 함께 최신 상태를 유지합니다. 각 브랜치의 야간 이미지를 가리키는 "staging" 및 "release" 태그를 사용할 수도 있지만, 업데이트에 시간이 걸릴 수 있고 중단될 수 있는 확장 프로그램을 사용하는 경우에는 적합하지 않을 수 있습니다.
+
+
+#### 설치 명령어
+
+1. 커맨드 라인 열기
+2. 아래의 명령어 실행
+
+`docker create --name='sillytavern' --net='[DockerNet]' -p '8000:8000/tcp' -v '[plugins]':'/home/node/app/plugins':'rw' -v '[config]':'/home/node/app/config':'rw' -v '[data]':'/home/node/app/data':'rw' 'ghcr.io/sillytavern/sillytavern:[version]'`
+
+> 8000은 기본 리스닝 포트입니다. 구성에서 포트를 변경한 경우 적절한 포트를 사용하는 것을 잊지 마세요.
+## 📱 Termux를 통해 Android OS에 설치하기
+
+> \[!NOTE]
+> **SillyTavern은 Termux를 사용하여 Android 기기에서 기본적으로 실행할 수 있지만, 이러한 사용 사례에 대한 공식적인 지원은 제공하지 않습니다.**
+>
+> **ArroganceComplex#2659의 가이드를 참조하세요:**
+>
+> * <https://rentry.org/STAI-Termux>
+
+**지원되지 않는 플랫폼: android arm LEtime-web.** 32비트 Android는 npm으로 설치할 수 없는 외부 종속성이 필요합니다. 다음 명령어를 사용하여 설치하세요: pkg install esbuild. 그런 다음 일반적인 설치 단계를 진행하세요.
+
+
+## API 키 관리
+
+SillyTavern은 API 키를 사용자 데이터 디렉터리의 `secrets.json` 파일에 저장합니다 (`/data/default-user/secrets.json`이 기본 경로입니다).
+
+
+
+기본적으로 API 키는 저장하고 페이지를 새로 고침한 후에는 인터페이스에서 보이지 않습니다.
+
+키 보기 기능을 활성화하려면 다음 단계를 따르세요:
+
+1. `config.yaml` 파일에서 `allowKeysExposure` 값을 `true로` 설정합니다.
+2. SillyTavern 서버를 다시 시작합니다.
+3. API 연결 패널 오른쪽 하단에 있는 '숨겨진 API 키 보기' 링크를 클릭합니다.
+
+## 커맨드 라인 인수
+
+`config.yaml`의 일부 설정을 덮어쓰기 위해 SillyTavern 서버 시작 시 커맨드 라인 인수를 전달할 수 있습니다.
+
+
+### 예시
+
+```shell
+node server.js --port 8000 --listen false
+# 혹은
+npm run start -- --port 8000 --listen false
+# 혹은 (Windows 전용)
+Start.bat --port 8000 --listen false
+```
+
+### 지원되는 인수
+
+| 옵션                  | 설명                                                                                          | 타입     |
+|-------------------------|------------------------------------------------------------------------------------------------------|----------|
+| `--version`             | 버전 표시                                                                                              | boolean  |
+| `--enableIPv6`          | IPv6 활성화                                                                                            | boolean  |
+| `--enableIPv4`          | IPv4 활성화                                                                                            | boolean  |
+| `--port`                | SillyTavern이 실행될 포트를 설정합니다. 설정되지 않은 경우 yaml config 'port'를 불러옵니다.                    | number   |
+| `--dnsPreferIPv6`       | DNS에 IPv6를 우선으로 할당합니다. 설정되지 않은 경우 yaml config�� 불러옵니다.                                 | boolean  |
+| `--autorun`             | 브라우저에서 SillyTavern을 자동으로 실행합니다. 설정되지 않은 경우 yaml config 'autorun'를 불러옵니다. | boolean  |
+| `--autorunHostname`     | 자동 실행 호스트 이름, 'auto'가 최적의 설정일 것입니다.                                                  | string   |
+| `--autorunPortOverride` | 자동 실행 포트 덮어쓰기                                                                      | string   |
+| `--listen`              | SillyTavern이 모든 네트워크 인터페이스에서 수신 대기합니다. 설정되지 않은 경우 yaml 구성 'listen'을 불러옵니다.	| boolean  |
+| `--corsProxy`           | CORS 프록시 활성화. 설정되지 않은 경우 yaml 구성 'enableCorsProxy'을 불러옵니다.	                     | boolean  |
+| `--disableCsrf`         | CSRF 보호 비활성화                                                                             | boolean  |
+| `--ssl`                 | SSL 활성화                                                                                          | boolean  |
+| `--certPath`            | 인증서 파일 경로                                                                       | string   |
+| `--keyPath`             | 프라이빗 키 파일 경로                                                                       | string   |
+| `--whitelist`           | 화이트리스트 모드 활성화                                                                               | boolean  |
+| `--dataRoot`            | 데이터 스토리지의 루트 디렉토리                                                                       | string   |
+| `--avoidLocalhost`      | 자동 모드에서 자동 실행 시 'localhost' 사용 방지                                                   | boolean  |
+| `--basicAuthMode`       | 기본 인증 활성화                                                                         | boolean  |
+| `--requestProxyEnabled` | 외부 리퀘스트 프록시 활성화                                                         | boolean  |
+| `--requestProxyUrl`     | 프록시 URL 리퀘스트 (HTTP 혹은 SOCKS 프로토콜)                                                          | string   |
+| `--requestProxyBypass`  | 프록시 바이패스 리스트 리퀘스트 (공백으로 구분된 호스트 목록)                                            | array    |
+
+## 원격 연결
+
+대부분의 경우 이는 PC에서 ST 서버를 실행하는 동안 모바일 장치에서 SillyTavern을 사용하려는 사람들을 위한 것입니다. 그러나 원격 연결을 다른 곳에서도 허용하도록 사용할 수 있습니다.
+
+원격 연결 설정 방법에 대한 자세한 가이드는 [Docs](https://docs.sillytavern.app/usage/remoteconnections/)에서 확인할 수 있습니다.
+
+또한 암호 보호 기능이 포함된 SillyTavern 사용자 프로필을 구성할 수 있습니다 (선택 사항): [Users](https://docs.sillytavern.app/installation/st-1.12.0-migration-guide/#users).
+
+## 성능 이슈가 발생하나요?
+
+1. 사용자 설정 패널(UI 테마 전환 카테고리)에서 흐림 효과를 비활성화하고 동작 줄이기를 활성화합니다.
+2. 응답 스트리밍을 사용하는 경우 스트리밍 FPS를 더 낮은 값(10-15 FPS 권장)으로 설정합니다.
+3. 브라우저에서 렌더링에 GPU 가속을 사용하도록 설정되어 있는지 확인합니다.
+
+## 라이센스 및 크레딧
+
+**이 프로그램은 유용할 것이라는 희망으로 배포되지만, 어떠한 보증도 제공하지 않습니다. 상품성 또는 특정 목적에의 적합성에 대한 묵시적인 보증조차도 제공하지 않습니다. 자세한 내용은 GNU Affero 일반 공중 사용 허가서를 참조하십시오.**
+
+* Humi의 [TavernAI](https://github.com/TavernAI/TavernAI) 1.2.8: MIT 라이선스
+* CncAnon의 TavernAITurbo 모드의 일부는 허가를 받아 사용됨
+* PepperTaco의 작업(<https://github.com/peppertaco/Tavern/>)에 영감을 받은 비주얼 노벨 모드
+* Noto Sans Font by Google (OFL 라이선스)
+* Font Awesome의 아이콘 테마 <https://fontawesome.com> (아이콘: CC BY 4.0, 폰트: SIL OFL 1.1, 코드: MIT 라이선스)
+* 기본 콘텐츠는 @OtisAlejandro (Seraphina 캐릭터 및 로어북)와 @kallmeflocc (10K 디스코드 사용자 축전 배경화면)가 제공함
+* [@mrguymiah](https://github.com/mrguymiah)와 [@Bronya-Rand](https://github.com/Bronya-Rand)의 Docker 가이드
+
+## 상위 기여자
+
+[![Contributors](https://contrib.rocks/image?repo=SillyTavern/SillyTavern)](https://github.com/SillyTavern/SillyTavern/graphs/contributors)
+
+<!-- LINK GROUP -->
+[cover]: https://github.com/user-attachments/assets/01a6ae9a-16aa-45f2-8bff-32b5dc587e44
+[discord-link]: https://discord.gg/sillytavern
+[discord-shield-badge]: https://img.shields.io/discord/1100685673633153084?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge

jiuguan2025cc/.github/readme-ru_ru.md

@@ -0,0 +1,450 @@
+> [!IMPORTANT]  
+> Приведенная здесь информация может быть устаревшей или неполной и предоставляется только для вашего удобства. Пожалуйста, используйте английскую версию для получения наиболее актуальной информации.
+
+<a name="readme-top"></a>
+
+![][cover]
+
+<div align="center">
+
+[English](readme.md) | [German](readme-de_de.md) | [中文](readme-zh_cn.md) | [繁體中文](readme-zh_tw.md) | [日本語](readme-ja_jp.md) | Русский | [한국어](readme-ko_kr.md)
+
+[![GitHub Stars](https://img.shields.io/github/stars/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/stargazers)
+[![GitHub Forks](https://img.shields.io/github/forks/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/network)
+[![GitHub Issues](https://img.shields.io/github/issues/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/issues)
+[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/pulls)
+
+</div>
+
+---
+
+Мобайл-френдли интерфейс, поддержка множества API (KoboldAI/CPP, Horde, NovelAI, Ooba, OpenAI, OpenRouter, Claude, Scale), ВН-образный режим Вайфу, Stable Diffusion, TTS, поддержка миров (лорбуков), кастомизируемый UI, автоперевод, тончайшая настройка промптов + возможность устанавливать расширения.
+
+Основано на форке [TavernAI](https://github.com/TavernAI/TavernAI) версии 1.2.8
+
+## Важные новости!
+
+1. Чтобы помочь вам быстрее разобраться в SillyTavern, мы создали [сайт с документацией](https://docs.sillytavern.app/). Ответы на большинство вопросов можно найти там.
+
+2. Почему пропали расширения после апдейта? Начиная с версии 1.10.6, большинство встроенных расширений были конвертированы в формат загружаемых аддонов. Их можно установить обратно через меню "Download Extensions and Assets" на панели расширений (значок с тремя кубиками сверху).
+
+3. Не поддерживается следующая платформа: android arm LEtime-web. 32-битный Android требует внешнюю зависимость, которую нельзя установить посредством npm. Для её установки потребуется следующая команда: `pkg install esbuild`. После этого продолжайте установку по общей инструкции.
+
+### Разрабатывается Cohee, RossAscends и всем сообществом SillyTavern
+
+### Что такое SillyTavern и TavernAI?
+
+SillyTavern — это интерфейс, который устанавливается на ПК (и на Android), который даёт возможность общаться с генеративным ИИ и чатиться/ролеплеить с вашими собственными персонажами или персонажами других пользователей.
+
+SillyTavern — это форк версии TavernAI 1.2.8, который разрабатывается более активно и имеет множество новых функций. Сейчас уже можно сказать, что это две отдельные и абсолютно самостоятельные программы.
+
+## Скриншоты
+
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/9b5f32f0-c3b3-4102-b3f5-0e9213c0f50f">
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/913fdbaa-7d33-42f1-ae2c-89dca41c53d1">
+
+### Ветки
+
+SillyTavern разрабатывается в двух ветках, чтобы всем категориям пользователей было удобно.
+
+* release -🌟 **Рекомендовано для большинства пользователей.** Самая стабильная ветка, рекомендуем именно её. Обновляется только в момент крупных релизов. Подходит для большей части пользователей.
+* staging - ⚠️ **Не рекомендуется для повседневного использования.** В этой ветке весь самый свежий и новый функционал, но будьте аккуратны, поскольку сломаться может в любом месте и в люб��е время. Только для продвинутых пользователей и энтузиастов.
+
+Если вы не умеете обращаться с git через командную строку, или не знаете, что такое ветка, то не переживайте! Наилучшим вариантом всегда остаётся ветка release.
+
+### Что ещё нужно, кроме SillyTavern?
+
+Сама по себе SillyTavern бесполезна, ведь это просто интерфейс. Вам потребуется доступ к бэкенду с ИИ, который и будет отыгрывать выбранного вами персонажа. Поддерживаются разные виды бэкендов: OpenAPI API (GPT), KoboldAI (локально или на Google Colab), и многое другое. Больше информации в [FAQ](https://docs.sillytavern.app/usage/faq/).
+
+### Требуется ли для SillyTavern мощный ПК?
+
+SillyTavern — это просто интерфейс, поэтому запустить его можно на любой картошке. Мощным должен быть бэкенд с ИИ.
+
+## Есть вопросы или предложения?
+
+### У нас появился сервер в Discord
+
+| [![][discord-shield-badge]][discord-link] | [Вступайте в наше Discord-сообщество!](https://discord.gg/sillytavern) Задавайте вопросы, делитесь любимыми персонажами и промптами. |
+| :---------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------- |
+
+Также можно написать разработчикам напрямую:
+
+* Discord: cohee или rossascends
+* Reddit: [/u/RossAscends](https://www.reddit.com/user/RossAscends/) или [/u/sillylossy](https://www.reddit.com/user/sillylossy/)
+* [Запостить issue на GitHub](https://github.com/SillyTavern/SillyTavern/issues)
+
+## Эта версия включает
+
+* Глубоко переработанную TavernAI 1.2.8 (переписано и оптимизировано более 50% кода)
+* Свайпы
+* Групповые чаты: комнаты для нескольких ботов, где персонажи могут говорить друг с другом и с вами
+* Чекпоинты и ветки для чатов
+* Продвинутые настройки для KoboldAI / TextGen со множеством созданных сообществом пресетов
+* Поддержка миров (функция "Информация о мире" / WorldInfo): создавайте свой богатый лор, или экономьте токены для карточек персонажей
+* Соединение через [OpenRouter](https://openrouter.ai) для разных API (Claude, GPT-4/3.5 и других)
+* Соединение с API [Oobabooga's TextGen WebUI](https://github.com/oobabooga/text-generation-webui)
+* Соединение с [AI Horde](https://aihorde.net/)
+* Настройку форматирования промптов
+
+## Расширения
+
+SillyTavern поддерживает расширения.
+
+* Эмоции для персонажей (спрайты)
+* Автоматический саммарайз (краткий пересказ) истории чата
+* Возможность отправить в чат картинку, которую ИИ сможет рассмотреть и понять
+* Генерация картинок в Stable Diffusion (5 пресетов для чата, плюс свободный режим)
+* Text-to-speech для сообщений ИИ (с помощью ElevenLabs, Silero, или родной TTS вашей ОС)
+
+Полный список расширений и инструкций к ним можно найти в [документации](https://docs.sillytavern.app/).
+
+## Улучшения от RossAscends для UI/CSS/общего удобства
+
+* Мобильный интерфейс адаптирован для iOS, добавлена возможность сохранить ярлык на главный экран и открыть приложение в полноэкранном режиме.
+* Горячие клавиши
+  * Up = Редактировать последнее сообщение в чате
+  * Ctrl+Up = Редактировать ВАШЕ последнее сообщение в чате
+  * Left = свайп влево
+  * Right = свайп вправо (ОБРАТИТЕ ВНИМАНИЕ: когда в окне ввода что-то напечатано, клавиши для свайпа не работают)
+  * Ctrl+Left = посмотреть локальные переменные (в консоли бр��узера)
+  * Enter (при нахождении внутри окна ввода) = отправить ваше сообщение ИИ
+  * Ctrl+Enter = Повторная генерация последнего ответа ИИ
+
+* Страница больше не перезагружается при смене имени пользователя или удалении персонажа
+
+* Отключаемая возможность автоматически соединяться с API при загрузке страницы.
+* Отключаемая возможность автоматически загружать последнего открытого персонажа при загрузке страницы.
+* Улучшенный счётчик токенов - работает с несохранёнными персонажами, отображает и перманентные, и временные токены
+
+* Улучшенный менеджер чатов
+  * Файлы с новыми чатами получают читабельные названия вида "(персонаж) - (когда создано)"
+  * Увеличен размер превью чата с 40 символов до 300.
+  * Несколько вариантов сортировки списка персонажей (по имени, дате создания, размеру чата).
+
+* Панели настроек слева и справа автоматически скрываются, если щёлкнуть за их пределы.
+* При нажатии на значок замка навигационная панель будет закреплена на экране, и эта настройка сохранится между сессиями
+* Сам статус панели (открыта или закрыта) также сохраняется между сессиями
+
+* Кастомизируемый интерфейс чата:
+  * Настройте звук при получении нового ответа
+  * Переключайтесь между круглыми и прямоугольными аватарками
+  * Увеличенное вширь окно чата для стационарных ПК
+  * Возможность включать полупрозрачные панели, стилизованные под стекло
+  * Настраиваемые цвета для обычного текста, курсива, цитат
+  * Настраиваемый цвет фона и интенсивность размытия
+
+# ⌛ Установка
+
+> **Внимание!**
+> * НЕ УСТАНАВЛИВАЙТЕ В ПАПКИ, КОТОРЫЕ КОНТРОЛИРУЕТ WINDOWS (Program Files, System32 и т.п.).
+> * НЕ ЗАПУСКАЙТЕ START.BAT С ПРАВАМИ АДМИНИСТРАТОРА
+> * УСТАНОВКА НА WINDOWS 7 НЕВОЗМОЖНА ИЗ-ЗА ОТСУТСТВИЯ NODEJS 18.16
+
+## 🪟 Windows
+
+## Установка через Git
+  1. Установите [NodeJS](https://nodejs.org/en) (рекомендуется последняя LTS-версия)
+  2. Установите [Git for Windows](https://gitforwindows.org/)
+  3. Откройте Проводник (`Win+E`)
+  4. Перейдите в папку, которую не контролирует Windows, или создайте её. (пример: C:\MySpecialFolder\)
+  5. Откройте командную строку. Для этого нажмите на адресную строку (сверху), введите `cmd` и нажмите Enter.
+  6. Когда появится чёрное окошко (командная строка), введите ОДНУ из перечисленных ниже команд:
+
+- для ветки release: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+- для ветки staging: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+  7. Когда клонирование закончится, дважды щёлкните по `Start.bat`, чтобы установить зависимости для NodeJS.
+  8. После этого сервер запустится, и SillyTavern откроется в вашем браузере.
+
+## Установка с помощью SillyTavern Launcher
+ 1. Установите [Git for Windows](https://gitforwindows.org/)
+ 2. Откройте Проводник (`Win+E`) и создайте или выберите папку, в которую будет установлен лаунчер
+ 3. Откройте командную строку. Для этого нажмите на адресную строку (сверху), введите `cmd` и нажмите Enter.
+ 4. Когда появится чёрное окошко, введите следующую команду: `git clone https://github.com/SillyTavern/SillyTavern-Launcher.git`
+ 5. Дважды щёлкните по `installer.bat` и выберите, что именно хотите установить
+ 6. После завершения установки дважды щёлкните по `launcher.bat`
+
+## Установка с помощью GitHub Desktop
+(Тут речь про git **только** в рамках GitHub Desktop, если хотите использовать `git` в командной строке, вам также понадобится [Git for Windows](https://gitforwindows.org/))
+  1. Установите [NodeJS](https://nodejs.org/en) (latest LTS version is recommended)
+  2. Установите [GitHub Desktop](https://central.github.com/deployments/desktop/desktop/latest/win32)
+  3. После завершения установки GitHub Desktop, нажмите `Clone a repository from the internet....` (обратите внимание: для этого шага **НЕ требуется** аккаунт на GitHub)
+  4. В меню перейдите на вкладку URL, введите адрес `https://github.com/SillyTavern/SillyTavern`, и нажмите Clone. В поле Local path можно изменить директорию, в которую будет загружена SillyTavern.
+  6. Чтобы запустить SillyTavern, откройте Проводник и перейдите в выбранную на предыдущем шаге папку. По умолчанию репозиторий будет склонирован сюда: `C:\Users\[Имя пользователя]\Documents\GitHub\SillyTavern`
+  7. Дважды щёлкните по файлу `start.bat`. (обратите внимание: окончание `.bat` может быть скрыто настройками вашей ОС. Таким образом, имя файла будет выглядеть как "`Start`". Дважды щёлкните по нему, чтобы запустить SillyTavern)
+  8. После того, как вы дважды щёлкнули по файлу, должно открыться чёрное окошко, и SillyTavern начнёт устанавливать свои зависимости.
+  9. Если установка прошла успешно, то в командной строке будет вот такое, а в браузере откроется вкладка с SillyTavern:
+  10. Подключайтесь к любому из [поддерживаемых API](https://docs.sillytavern.app/usage/api-connections/) и начинайте переписку!
+
+## 🐧 Linux и 🍎 MacOS
+
+В MacOS и Linux всё это делается через Терминал.
+
+1. Установите git и nodeJS (как именно - зависит от вашей ОС)
+2. Клонируйте репозиторий
+
+- для ветки release: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+- для ветки staging: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+3. Перейдите в папку установки с помощью `cd SillyTavern`.
+4. Запустите скрипт `start.sh` с помощью одной из команд:
+
+- `./start.sh`
+- `bash start.sh`
+
+## Установка с помощью SillyTavern Launcher
+
+### Для пользователей Linux
+1. Откройте любимый терминал и установите git
+2. Загрузите Sillytavern Launcher с помощью команды: `git clone https://github.com/SillyTavern/SillyTavern-Launcher.git`
+3. Перейдите в SillyTavern-Launcher: `cd SillyTavern-Launcher`
+4. Запустите лаунчер установки: `chmod +x install.sh && ./install.sh`, затем выберите, что конкретно хотите установить
+5. После завершения установки, запустите лаунчер следующей командой: `chmod +x launcher.sh && ./launcher.sh`
+
+### Для пользователей Mac
+1. Откройте терминал и установите brew: `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"`
+2. Затем установите git: `brew install git`
+3. Загрузите Sillytavern Launcher: `git clone https://github.com/SillyTavern/SillyTavern-Launcher.git`
+4. Перейдите в SillyTavern-Launcher: `cd SillyTavern-Launcher`
+5. Запустите лаунчер установки: `chmod +x install.sh && ./install.sh` and choose what you wanna install
+6. После завершения установки, запустите лаунчер следующей командой: `chmod +x launcher.sh && ./launcher.sh`
+
+## 🐋 Установка с помощью Docker
+
+Предполагается, что вы уже установили Docker, имеете доступ к командной строке для установки контейнеров и знакомы с их базовым управлением.
+
+### Сборка образа самостоятельно
+
+У нас есть подробное руководство по использованию SillyTavern в Docker [здесь](http://docs.sillytavern.app/installation/docker/), которое охватывает установку на Windows, macOS и Linux! Ознакомьтесь с ним, если хотите создать образ самостоятельно.
+
+### Использование реестра контейнеров GitHub (самый простой способ)
+
+Для работы SillyTavern вам понадобятся две обязательные настройки каталогов и одна настройка порта. В команде замените указанные значения на свои:
+
+#### Переменные контейнера
+
+##### Маппинг томов
+
+* [config] - директория, где на вашем хосте будут храниться файлы конфигурации SillyTavern.
+* [data] - директория, где на вашем хосте будут храниться пользовательские данные SillyTavern (включая персонажей).
+* [plugins] - (необязательно) директория, где на вашем хосте будут храниться плагины сервера SillyTavern.
+
+##### Маппинг портов
+
+* [PublicPort] - Порт, через который будет передаваться трафик. Это обязательно, так как вы будете обращаться к контейнеру извне его виртуальной машины. НЕ ОТКРЫВАЙТЕ этот порт в интернет без реализации дополнительного уровня безопасности.
+
+##### Дополнительные настройки
+
+* [DockerNet] - Docker сеть, к которой контейнер должен быть подключен. Если вы не знаете, что это, обратитесь к [официальной документации Docker](https://docs.docker.com/reference/cli/docker/network/).
+* [version] - на правой части этой страницы GitHub вы найдете раздел "Packages". Выберите пакет "sillytavern", чтобы увидеть версии образов. Тег "latest" позволит вам обновляться до текущего релиза. Также доступны теги "staging" и "release", которые соответствуют ночным сборкам соответствующих веток. Однако это может быть нецелесообразно, если вы используете расширения, которые могут ломаться и требуют времени для обновления.
+
+#### Команда установки
+
+1. Откройте командную строку
+2. Выполните следующую команду
+
+`docker create --name='sillytavern' --net='[DockerNet]' -p '8000:8000/tcp' -v '[plugins]':'/home/node/app/plugins':'rw' -v '[config]':'/home/node/app/config':'rw' -v '[data]':'/home/node/app/data':'rw' 'ghcr.io/sillytavern/sillytavern:[version]'`
+
+> Заметьте, что 8000 является портом по умолчанию. Не забудьте использовать соответствующий порт, если вы измените его в конфиге.
+
+## 📱 Мобильные устройства - Установка при помощи termux
+
+> **ОБРАТИТЕ ВНИМАНИЕ!**
+> 
+> **На Android-телефонах SillyTavern можно запускать нативно посредством Termux. Обратитесь к гайду, написанному ArroganceComplex#2659:**
+> 
+> * <https://rentry.org/STAI-Termux>
+
+
+## Управление ключами от API
+
+SillyTavern сохраняет ключи от ваших API в файле `secrets.json` в папке на сервере.
+
+По умолчанию, ключи не будут отображаться на фронте после их ввода и перезагрузки страницы.
+
+Чтобы включить возможность отображения ключей путём нажатия кнопки в блоке API:
+
+1. Зайдите в файл `config.yaml` и установите `allowKeysExposure` в положение `true`.
+2. Перезапустите сервер SillyTavern.
+
+## Аргументы командной строки
+
+Вы можете передавать аргументы командной строки при запуске сервера SillyTavern, чтобы переопределять настройки из `config.yaml`.
+
+### Примеры
+
+```shell
+node server.js --port 8000 --listen false
+# или
+npm run start -- --port 8000 --listen false
+# или (только на Windows)
+Start.bat --port 8000 --listen false
+```
+
+### Поддерживаемые аргументы
+
+| Аргумент                | Описание                                                                                                       | Тип      |
+|-------------------------|----------------------------------------------------------------------------------------------------------------|----------|
+| `--version`             | Показывает номер версии.                                                                                       | boolean  |
+| `--enableIPv6`          | Включает IPv6.                                                                                                 | boolean  |
+| `--enableIPv4`          | Включает IPv4.                                                                                                 | boolean  |
+| `--port`                | Устанавливает порт, котрый будет использовать SillyTavern. Если не указан, то используется yaml-конфиг 'port'. | number   |
+| `--dnsPreferIPv6`       | Отдает предпочтение IPv6 для dns. Если не указан, то используется yaml-конфиг 'preferIPv6'.                    | boolean  |
+| `--autorun`             | Автоматический запуск SillyTavern в браузере. Если не указан, то используется yaml-конфиг 'autorun'.           | boolean  |
+| `--autorunHostname`     | Имя хоста автозапуска, лучше оставить на 'auto'.                                                               | string   |
+| `--autorunPortOverride` | Переопределяет порт для автозапуска.                                                                           | string   |
+| `--listen`              | SillyTavern будет прослушивать все сетевые интерфейсы. Если не указан, то используется yaml-конфиг 'listen'.   | boolean  |
+| `--corsProxy`           | Включает CORS-прокси. Если не указан, то используется yaml-конфиг 'enableCorsProxy'.                           | boolean  |
+| `--disableCsrf`         | Отключает защиту от CSRF.                                                                                      | boolean  |
+| `--ssl`                 | Включает SSL.                                                                                                  | boolean  |
+| `--certPath`            | Путь к файлу c сертификатом.                                                                                   | string   |
+| `--keyPath`             | Путь к файлу с закрытым ключом.                                                                                | string   |
+| `--whitelist`           | Включает режим белого списка.                                                                                  | boolean  |
+| `--dataRoot`            | Корневой каталог для хранения данных.                                                                          | string   |
+| `--avoidLocalhost`      | Избегает использования 'localhost' для автозапуска в режиме 'auto'.                                            | boolean  |
+| `--basicAuthMode`       | Включает простую аутентификацию.                                                                               | boolean  |
+| `--requestProxyEnabled` | Разрешает использование прокси для исходящих запросов.                                                         | boolean  |
+| `--requestProxyUrl`     | URL-адрес прокси (протоколы HTTP или SOCKS).                                                                   | string   |
+| `--requestProxyBypass`  | Bypass список прокси (список хостов, разделенных пробелами).                                                   | array    |
+
+## Удалённое подключение
+
+В основном этим пользуются тогда, когда хотят использовать SillyTavern с телефона, запустив сервер SillyTavern на стационарном ПК в той же Wi-Fi-сети.
+
+Однако это позволит подключаться откуда угодно, а не только вам.
+
+**ВАЖНО: в SillyTavern не предусмотрена возможность использования программы несколькими людьми. Поэтому любой, кто подключится к вашему серверу, получит доступ ко всем вашим персонажам и ч��там, а также сможет менять настройки через UI.**
+
+### 1. Заведение "белого списка" IP-адресов
+
+* Создайте в корневой папке SillyTavern файл с названием `whitelist.txt`.
+* Откройте файл в текстовом редакторе и внесите список IP-адресов, с которых хотите разрешить подключение.
+
+*Принимаются как обычные IP-адреса, так и целые диапазоны, размеченные с помощью астериска. Примеры:*
+
+```txt
+192.168.0.1
+192.168.0.20
+```
+
+или
+
+```txt
+192.168.0.*
+```
+
+(диапазон из примера сверху позволит подключаться всем устройствам в локальной сети)
+
+Также принимаются маски CIDR (вида 10.0.0.0/24).
+
+* Сохраните файл `whitelist.txt`.
+* Перезапустите сервер ST.
+
+После этого устройства из белого списка смогут подключаться к вашему серверу.
+
+*Обратите внимание: в файле `config.yaml` также имеется массив `whitelist`, который работает по тому же принципу. Однако если существует файл `whitelist.txt`, то этот массив игнорируется.*
+
+### 2. Получение IP хост-машины с ST
+
+После настройки белого списка адресов, следующим шагом будет получение IP-адреса хост-машины, на которой запущена SillyTavern.
+
+Если хост-машина находится в той же Wi-Fi-сети, то можно воспользоваться её внутренним Wi-Fi-IP-адресом:
+
+* На Windows: нажмите Пуск > введите `cmd.exe` в поиске > в консоли введите команду `ipconfig` и нажмите Enter > найдите пункт `IPv4-адрес`.
+
+Если вы (или кто-то другой) хотите подключаться к хост-машине из другой сети, то вам понадобится ваш публичный IP-адрес.
+
+* Откройте [эту страницу](https://whatismyipaddress.com/) с вашей хост-машины и найдите пункт `IPv4`. На этот адрес и будет подключаться удалённое устройство.
+
+### 3. Соединить удалённое устройство с хост-машиной ST
+
+Какой бы IP-адрес вы ни выбрали, вам нужно будет вводить его в адресной строке браузера вашего удалённого устройства.
+
+Обычный адрес хост-машины, находящейся в той же Wi-Fi-сети, выглядит примерно так:
+
+`http://192.168.0.5:8000`
+
+НЕ используйте https://
+Только http://
+
+### Открытие доступа до ST для всех IP-адресов
+
+Мы не рекомендуем так делать, но вы можете открыть файл `config.yaml` и изменить `whitelistMode` на `false`.
+
+Обязательно нужно удалить (или переименовать) файл `whitelist.txt`, если такой файл есть в корневой директории SillyTavern.
+
+Эта практика считается небезопасной, поэтому, если вы решите так сделать, мы попросим вас установить логин и пароль.
+
+Оба этих параметра настраиваются в `config.yaml` (username и password).
+
+Останется только перезапустить сервер ST, и после этого к вам сможет подключиться любой пользователь вне зависимости от IP-адреса его устройства. Главное, чтобы он знал логин и пароль.
+
+### Не получается соединиться?
+
+* Создайте входящее/исходящее правило в вашем фаерволле для порта, указанного в `config.yaml`. НЕ ПУТАЙТЕ этот процесс с пробросом портов на роутере. Если по ошибке перепутаете, то на ваш сервер сможет забраться посторонний человек и украсть ваши логи, этого следует избегать.
+* Переключите Сетевой профиль на значение "Частные". Для этого зайдите в Параметры > Сеть и Интернет > Ethernet. КРАЙНЕ важно для Windows 11, без этого не получится подключиться даже с правилом фаервола.
+
+## Проблемы с производительностью?
+
+Попробуйте включить опцию "Отключить эффект размытия" в меню "Пользовательские настройки".
+
+## Нравится ваш проект! Как помочь?
+
+### ЧТО ДЕЛАТЬ
+
+1. Присылайте пулл реквесты
+2. Присылайте идеи и баг-репорты, оформленные по установленным шаблонам
+3. Прежде чем задавать вопросы, прочтите readme и документацию
+
+### ЧЕГО НЕ ДЕЛАТЬ
+
+1. Предлагать донаты
+2. Присылать баг-репорты безо всякого контекста
+3. Задавать вопросы, на которые уже отвечали
+
+## Где найти старые фоны?
+
+Мы двигаемся в сторону 100% уникальности всего используемого контента, поэтому старые фоны были убраны из репозитория.
+
+Они отправлены в архив, скачать их можно здесь:
+
+<https://files.catbox.moe/1xevnc.zip>
+
+
+
+
+## Авторы и лицензии
+
+**Мы надеемся, что эта программа принесёт людям пользу,
+но мы не даём НИКАКИХ ГАРАНТИЙ; мы ни в коем случае не гарантируем того,
+что программа СООТВЕТСТВУЕТ КАКИМ-ЛИБО КРИТЕРИЯМ или ПРИГОДНА ДЛЯ КАКОЙ-ЛИБО ЦЕЛИ.
+Подробнее можно узнать в GNU Affero General Public License.**
+
+* Базовая TAI от Humi: Лицензия неизвестна
+* Модификации от Cohee и производная кодовая база: AGPL v3
+* Дополнения RossAscends: AGPL v3
+* Кусочки TavernAITurbo мода от CncAnon: Лицензия неизвестна
+* Различные коммиты и предложения от kingbri (<https://github.com/bdashore3>)
+* Расширения и внедрение разного рода удобств - city_unit (<https://github.com/city-unit>)
+* Различные коммиты и баг-репорты от StefanDanielSchwarz (<https://github.com/StefanDanielSchwarz>)
+* Режим Вайфу вдохновлён работой PepperTaco (<https://github.com/peppertaco/Tavern/>)
+* Благодарность Pygmalion University за прекрасную работу по тестированию и за все предлагаемые крутые фичи!
+* Благодарность oobabooga за компиляцию пресетов для TextGen
+* Пресеты для KoboldAI из KAI Lite: <https://lite.koboldai.net/>
+* Шрифт Noto Sans от Google (OFL license)
+* Тема Font Awesome <https://fontawesome.com> (Иконки: CC BY 4.0, Шрифты: SIL OFL 1.1, Код: MIT License)
+* Клиентская библиотека для AI Horde от ZeldaFan0225: <https://github.com/ZeldaFan0225/ai_horde>
+* Пусковой скрипт для Linux от AlpinDale
+* Благодарность paniphons за оформление документа с FAQ
+* Фон в честь 10 тысяч пользователей в Discord от @kallmeflocc
+* Стандартный контент (персонажи и лорбуки) предоставлен пользователями @OtisAlejandro, @RossAscends и @kallmeflocc
+* Корейский перевод от @doloroushyeonse
+* Поддержка k_euler_a для Horde от <https://github.com/Teashrock>
+* Китайский перевод от [@XXpE3](https://github.com/XXpE3), 中文 ISSUES 可以联系 @XXpE3
+
+<!-- LINK GROUP -->
+[back-to-top]: https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square
+[cover]: https://github.com/user-attachments/assets/01a6ae9a-16aa-45f2-8bff-32b5dc587e44
+[discord-link]: https://discord.gg/sillytavern
+[discord-shield]: https://img.shields.io/discord/1100685673633153084?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=flat-square
+[discord-shield-badge]: https://img.shields.io/discord/1100685673633153084?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge

jiuguan2025cc/.github/readme-zh_cn.md

@@ -0,0 +1,322 @@
+> [!IMPORTANT]  
+> 这里的信息可能已经过时或不完整，仅供您参考。请使用英文版本获取最新信息。
+
+![][cover]
+
+<div align="center">
+
+[English](readme.md) | [German](readme-de_de.md) | 中文 | [繁體中文](readme-zh_tw.md) | [日本語](readme-ja_jp.md) | [Русский](readme-ru_ru.md) | [한국어](readme-ko_kr.md)
+
+[![GitHub Stars](https://img.shields.io/github/stars/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/stargazers)
+[![GitHub Forks](https://img.shields.io/github/forks/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/network)
+[![GitHub Issues](https://img.shields.io/github/issues/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/issues)
+[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/pulls)
+
+</div>
+
+---
+
+移动设备界面友好，多种人工智能服务或模型支持（KoboldAI/CPP, Horde, NovelAI, Ooba, OpenAI, OpenRouter, Claude, Scale），类似 Galgame 的 老 婆 模 式，Horde SD，文本系统语音生成，世界信息（Lorebooks），可定制的界面，自动翻译，和比你所需要的更多的 Prompt。附带扩展服务，支持文本绘画生成与语音生成和基于向量数据库 的聊天信息总结。
+
+基于 TavernAI 1.2.8 的分叉版本
+
+### 由 Cohee、RossAscends 和 SillyTavern 社区为您呈现
+
+注意：我们创建了一个 [帮助文档](https://docs.sillytavern.app/) 网站来回答各类问题与帮助您开始使用。
+
+### SillyTavern 或 TavernAI 是什么？
+
+SillyTavern 是一个可以安装在电脑（和安卓手机）上的用户界面，让您可以与文本生成的人工智能互动，并与您或社区创建的角色聊天/玩角色扮演游戏。
+
+SillyTavern 是 TavernAI 1.2.8 的一个分支，正在进行更积极地开发，并添加了许多重要功能。在这一点上，它可以被视为完全独立的程序。
+
+### 分支
+
+SillyTavern 采用双分支进行开发，以确保所有用户都能获得流畅的使用体验。
+
+* release -🌟 **推荐给大多数用户。** 这是最稳定、最推荐的分支，只有在重大版本推送时才会更新。适合大多数用户使用。
+* staging - ⚠️ **不建议随意使用。** 该分支拥有最新功能，但要谨慎，因为它随时可能崩溃。仅适用于高级用户和爱好者。
+
+如果你不熟悉使用 Git 命令，或者不了解什么是分支，别担心！release 分支始终是您的首选。
+
+### 除了 SillyTavern，我还需要什么？
+
+SillyTavern 本身并无用处，因为它只是一个用户聊天界面。你必须接入一个能充当角色扮演的人工智能系统。支持的人工智能系统有多种：OpenAPI API (GPT)、KoboldAI（可在本地或 Google Colab 上运行）等。您可以在 [常见问题](https://docs.sillytavern.app/usage/faq/) 中阅读更多相关信息。
+
+### 我需要一台性能强大的电脑来运行 SillyTavern 吗？
+
+由于 SillyTavern 只是一个用户聊天界面，它对硬件性能的要求很低，可以在任何电脑上运行。需要强大性能的是人工智能系统。
+
+### 移动设备支持
+
+> 注意
+
+> **此分叉可使用 Termux 在安卓手机上原生运行。请参考 ArroganceComplex#2659 编写的指南：**
+
+<https://rentry.org/STAI-Termux>
+
+## 有问题或建议？
+
+### 我们现在有了 Discord 社区
+
+获取支持，或分享喜爱的角色和 Prompt：
+
+### [加入 Discord 社区](https://discord.gg/sillytavern)
+
+***
+
+直接与开发人员联系：
+
+* Discord: cohee 或 rossascends
+* Reddit：/u/RossAscends 或 /u/sillylossy
+* [发布 GitHub 问题](https://github.com/SillyTavern/SillyTavern/issues)
+
+## 此版本包括
+
+* 经过大量修改的 TavernAI 1.2.8（超过 50% 的代码经过重写或优化）
+* 根据自定义规则自动重新生成消息
+* 群聊：多机器人房间，供角色与你或彼此交谈
+* 聊天书签/分支（复制当前状态下的对话）
+* 先进的 KoboldAI / TextGen 生成设置，包含大量社区预设
+* 支持世界信息（Lorebooks）：创建丰富的传说
+* 支持 Window AI 浏览器扩展（运行 Claude、GPT 4 等模型）：<https://windowai.io/>
+* [Oobabooga's TextGen WebUI](https://github.com/oobabooga/text-generation-webui) API 连接
+* 连接 [AI Horde](https://aihorde.net/)
+* Prompt 生成格式调整
+* Webp 角色卡支持（PNG 仍是内部格式）
+
+## 扩展
+
+SillyTavern 支持扩展服务。
+
+* 角色情绪识别
+* 聊天记录自动摘要
+* 在聊天窗口发送图片，并由人工智能解释图片内容
+* 文本图像生成（5 预设，以及 "自由模式"）
+* 聊天信息的文字转语音（通过 ElevenLabs、Silero 或操作系统的语音生成）
+
+扩展服务的完整功能介绍和使用教程，请参阅 [Docs](https://docs.sillytavern.app/)。
+
+## 界面/CSS/性能，由 RossAscends 调整并优化
+
+* 针对 iOS 系统优化了界面，并支持将快捷方式保存到主屏幕，在全屏模式下打开。
+* 热键
+  * 上 = 编辑聊天中的最后一条信息
+  * Ctrl+P = 编辑聊天中最后一条用户信息
+  * 左 = 向左滑动
+  * 右 = 向右滑动（注意：当聊天窗口输入内容时，轻扫快捷键将被禁用）
+  * Ctrl+左 = 查看本地存储的变量（在浏览器控制台窗口中）
+  * 回车（选择聊天栏）= 向人工智能发送信息
+  * Ctrl+Enter = 重新生成人工智能最后的回复
+
+* 用户名更改和角色删除不再强制重新刷新页面。
+
+* 增加在页面加载时自动连接 API 的选项。
+* 增加选项，在页面加载时自动加载最近的聊天信息。
+* 更好的 Tokens 计算器 - 适用于未保存的文字，并显示永久和临时 Tokens 数量
+
+* 更好的聊天历史查询窗口
+  * 聊天的文件名以"（角色卡名称）+（创建时间）"的可读格式保存
+  * 聊天历史预览从 40 个字符增加到 300 个字符。
+  * 聊天历史排序有多种选择（按名称、创建日期、聊天记录大小）。
+
+* 默认情况下，左侧和右侧弹出的设置面板会在点击其他区域时自动关闭。
+* 点击导航面板上的 "锁按钮" 将保持弹出面板打开，并在不同聊天中记住此设置。
+* 导航面板的打开或关闭状态也会跨聊天保存。
+
+* 自定义聊天界面：
+  * 收到新消息时播放提示音
+  * 切换圆形或长方形头像样式
+  * 在台式电脑上拥有更宽的聊天窗口
+  * 可选的半透明玻璃效果聊天窗口
+  * 可定制 "主文本"、"引用文本 "和 "斜体文本 "的字体颜色。
+  * 可定制聊天界面的背景颜色和透明模糊程度
+
+## 安装
+
+*注意：SillyTavern 用于本地安装，尚未在 Colab 或其他云服务上进行全面测试。
+
+> **警告**
+
+> 切勿安装到任何受 Windows 控制的系统文件夹（Program Files, System32, etc）中。
+
+> 不要以管理员权限运行 start.bat
+
+### Windows
+
+通过 Git 安装（推荐使用，便于更新）
+
+附有精美图片示例的简易指南：
+<https://docs.sillytavern.app/installation/windows/>
+
+  1. 安装 [NodeJS](https://nodejs.org/en)（建议使用最新的 LTS 版本）
+  2. 安装 [GitHub 客户端](https://central.github.com/deployments/desktop/desktop/latest/win32)
+  3. 打开 Windows 资源管理器 (`Win+E`)
+  4. 浏览或创建一个不受 Windows 控制或监控的文件夹。(例如：C:\MySpecialFolder\)
+  5. 点击顶部的 "地址栏"，在该文件夹内打开命令提示符，输入 `cmd`，然后按回车。
+  6. 弹出黑框（CMD 命令提示符）后，键入以下其中一项并按 Enter：
+
+* 稳定分支：`git clone https://github.com/SillyTavern/SillyTavern -b release`
+* 开发分支： `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+  7. 等待 Git 克隆完成后，双击文件夹中的 `Start.bat` 将启动 NodeJS 并开始自动安装需要的软件包。
+  8. 然后 SillyTavern 服务就会自动启动，同时在浏览器新标签页中自动打开。
+
+通过压缩包下载安装（不推荐）
+
+  1. 安装 [NodeJS](https://nodejs.org/en)（建议使用最新的 LTS 版本）
+  2. 从该 GitHub 仓库下载压缩包。(从 [Releases](https://github.com/SillyTavern/SillyTavern/releases/latest) 获取 "Source code（zip）"）。
+  3. 将压缩包解压到您选择的文件夹中
+  4. 双击或在命令行中运行 `Start.bat`。
+  5. SillyTavern 服务自动为你准备好一切后，会在你的浏览器中打开一个新标签页。
+
+### Linux
+
+  1.运行 `start.sh` 脚本。
+  2.等待自动完成，然后开始享受
+
+## API 密钥管理
+
+SillyTavern 会将 API 密钥保存在目录中的 `secrets.json` 文件内。
+
+默认情况下，输入密钥并重新加载页面后，密钥会自动隐藏以保证安全。
+
+如果要想通过点击 API 输入框旁边的按钮来查看密钥，请按照以下设置：
+
+1. 打开 `config.yaml` 文件，将里面的 `allowKeysExposure` 设置为 `true`。
+2. 然后重启 SillyTavern 服务。
+
+## 远程访问
+
+这通常是为那些想在手机上使用 SillyTavern 的人准备的，而他们的电脑和手机在同一个局域网中。
+
+不过，SillyTavern 也可以被设置为允许从任何地方进行远程访问。
+
+**重要提示：SillyTavern 是单用户程序，因此任何人登录后都能看到所有的角色卡和聊天内容，并能更改任何设置。
+
+### 1.管理白名单 IP
+
+* 在你的 SillyTavern 文件夹中新建一个文本文件，名为 `whitelist.txt`。
+* 用文本编辑器打开该文件，添加你希望允许连接的 IP 地址列表。
+* 接受单个 IP 地址和 IP 范围，示例：
+
+```
+192.168.0.1
+192.168.0.20
+```
+
+或者
+
+```
+192.168.0.*
+```
+
+(上述 IP 范围将允许局域网中的任何设备连接）
+
+也接受子网掩码设置（如 10.0.0.0/24）。
+
+* 保存`whitelist.txt`文件。
+* 重启 SillyTavern 服务。
+
+然后，文件中设置的 IP 就可以访�� SillyTavern 了。
+
+*注意："config.yaml" 文件内也有一个 "whitelist" 设置，你可以用同样的方法设置它，但如果 "whitelist.txt" 文件存在，这个设置将被忽略。
+
+### 2.获取 SillyTavern 服务的 IP 地址
+
+白名单设置完成后，您需要 SillyTavern 服务的 IP 地址。
+
+如果 SillyTavern 服务设备在同一个局域网上，则使用安装 SillyTavern 服务的电脑的局域网 IP 地址：
+
+* Windows：Windows 按钮 > 在搜索栏中输入 `cmd.exe` > 在打开的控制台中输入 `ipconfig`，回车 > 然后在输出中查找 `IPv4` 地址。
+
+如果您（或其他人）想在互联网中访问你自己的 SillyTavern 服务，则需要运行 SillyTavern 服务的设备的互联网 IP 地址。
+
+* 使用运行 SillyTavern 的设备，访问 [this page](https://whatismyipaddress.com/) 并查找 `IPv4`。这是您从互联网访问时要用到的。
+
+### 3. 使用其他设备访问 SillyTavern 服务
+
+无论你最终使用的是什么 IP 地址，都要将该 IP 地址和端口号输入其他设备网络浏览器。
+
+同一局域网中的 SillyTavern 服务的典型默认地址如下：
+
+`http://192.168.0.5:8000`
+
+使用 http:// 而不是 https://
+
+### 向所有 IP 开放您的 SillyTavern 服务
+
+我们不建议这样做，但您可以打开 `config.yaml` 并将里面的 `whitelistMode` 设置改为 `false`。
+
+你必须删除（或重命名）SillyTavern 文件夹中的 `whitelist.txt` 文件（如果有的话）。
+
+这通常是不安全的做法，所以我们要求在这样做时必须设置用户名和密码。
+
+用户名和密码在`config.yaml`文件中设置。
+
+重启 SillyTavern 服务后，只要知道用户名和密码，任何设备都可以访问。
+
+### 还是无法访问？
+
+* 为 `config.yaml` 文件中的端口创建一条入站/出站防火墙规则。切勿将此误认为是路由器上的端口转发，否则，有人可能会发现你的聊天隐私，那就大错特错了。
+* 在 "设置" > "网络和 Internet" > "以太网" 中启用 "专用网络" 配置。这对 Windows 11 非常重要，否则即使添加了上述防火墙规则也无法连接。
+
+### 性能问题？
+
+尝试在用户设置面板上关闭模糊效果（快速用户界面）模式。
+
+## 我喜欢你的项目！我该如何贡献自己的力量？
+
+### 应该
+
+1. 发送 Fork 请求
+2. 使用规定的模板发送功能建议和问题报告
+3. 在提出任何问题之前，请先阅读 Readme 文件和文档
+
+#### 不应该
+
+1. 提供金钱捐赠
+2. 发送错误报告而不提供任何详细信息
+3. 提出已经回答过无数次的问题
+
+## 我在哪里可以找到以前的聊天背景图片？
+
+我们正在实行 100% 原创内容的政策，因此旧的背景图片已从该资源库中删除。
+
+不过你可以在这里找到它们的存档：
+
+<https://files.catbox.moe/1xevnc.zip>
+
+## 屏幕截图
+
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/9b5f32f0-c3b3-4102-b3f5-0e9213c0f50f">
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/913fdbaa-7d33-42f1-ae2c-89dca41c53d1">
+
+## 许可证和贡献
+
+**发布本程序是希望它能有所帮助，但不做任何保证；甚至没有明示的性能、稳定性和其他任何特定用途的可用性保证。更多详情，请参阅 GNU Affero 通用公共许可证。**
+
+**This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.**
+
+* TAI Base by Humi: Unknown license
+* Cohee's modifications and derived code: AGPL v3
+* RossAscends' additions: AGPL v3
+* Portions of CncAnon's TavernAITurbo mod: Unknown license
+* kingbri's various commits and suggestions (<https://github.com/bdashore3>)
+* StefanDanielSchwarz's various commits and bug reports (<https://github.com/StefanDanielSchwarz>)
+* Waifu mode inspired by the work of PepperTaco (<https://github.com/peppertaco/Tavern/>)
+* Thanks Pygmalion University for being awesome testers and suggesting cool features!
+* Thanks oobabooga for compiling presets for TextGen
+* KoboldAI Presets from KAI Lite: <https://lite.koboldai.net/>
+* Noto Sans font by Google (OFL license)
+* Icon theme by Font Awesome <https://fontawesome.com> (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
+* AI Horde client library by ZeldaFan0225: <https://github.com/ZeldaFan0225/ai_horde>
+* Linux startup script by AlpinDale
+* Thanks paniphons for providing a FAQ document
+* 10K Discord Users Celebratory Background by @kallmeflocc
+* Default content (characters and lore books) provided by @OtisAlejandro, @RossAscends and @kallmeflocc
+* Korean translation by @doloroushyeonse
+* 中文翻译由 [@XXpE3](https://github.com/XXpE3) 完成，中文 ISSUES 可以联系 @XXpE3
+
+<!-- LINK GROUP -->
+[cover]: https://github.com/user-attachments/assets/01a6ae9a-16aa-45f2-8bff-32b5dc587e44

jiuguan2025cc/.github/readme-zh_tw.md

@@ -0,0 +1,381 @@
+> [!IMPORTANT]  
+> 此處資訊可能已經過時或不完整，僅供您參考。請使用英文版本以取得最新資訊。
+
+<a name="readme-top"></a>
+
+![][cover]
+
+<div align="center">
+
+[English](readme.md)  | [German](readme-de_de.md) | [中文](readme-zh_cn.md) | 繁體中文 | [日本語](readme-ja_jp.md) | [Русский](readme-ru_ru.md) | [한국어](readme-ko_kr.md)
+
+[![GitHub 星標](https://img.shields.io/github/stars/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/stargazers)
+[![GitHub 分支](https://img.shields.io/github/forks/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/network)
+[![GitHub 問題](https://img.shields.io/github/issues/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/issues)
+[![GitHub 拉取請求](https://img.shields.io/github/issues-pr/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/pulls)
+
+</div>
+
+---
+
+SillyTavern 提供一個統一的前端介面，整合多種大型語言模型的 API（包括：KoboldAI/CPP、Horde、NovelAI、Ooba、Tabby、OpenAI、OpenRouter、Claude、Mistral 等）。同時具備對行動裝置友善的佈局、視覺小說模式（Visual Novel Mode）、Automatic1111 與 ComfyUI 的影像生成 API 整合、TTS（語音合成）、世界資訊（Lorebook）、可自訂 UI、自動翻譯功能，以及強大的提示詞（prompt）設定選項和無限的第三方擴充潛力。
+
+我們擁有一個 [官方文件網站](https://docs.sillytavern.app/) 可以幫助解答絕大多數的使用問題，並幫助您順利入門。
+
+## SillyTavern 是什麼？
+
+SillyTavern（簡稱 ST）是一款本地安裝的使用者介面，讓您能與大型語言模型（LLM）、影像生成引擎以及語音合成模型互動的前端。
+
+SillyTavern 起源於 2023 年 2 月，作為 TavernAI 1.2.8 的分支版本發展至今。目前已有超過 100 位貢獻者，並擁有超過兩年的獨立開發歷史。如今，它已成為 AI 愛好者中備受推崇的軟體之一。
+
+## 我們的願景
+
+1. 我們致力於賦予使用者對 LLM 提示詞的最大控制權與實用性，並認為學習過程中的挑戰是樂趣的一部分。
+2. 我們不提供任何線上或託管服務，也不會程式化追蹤任何使用者數據。
+3. SillyTavern 是由一群熱衷於 LLM 的開發者社群所打造的專案，並將永遠保持免費與開源。
+
+## 分支介紹
+
+SillyTavern 採用雙分支開發模式，確保為所有使用者提供流暢的體驗。
+
+* `release`（穩定版）：🌟 **推薦給大部分的使用者使用。** 此分支最為穩定，僅在主要版本發布時更新。適合大多數人，通常每月更新一次。
+* `staging`（開發版）：⚠️ **不建議普通使用者使用。** 此分支包含最新功能，但可能隨時出現問題。適合進階使用者與愛好者，每日多次更新。
+
+如果您不熟悉 git CLI 或對分支概念不清楚，請放心，對您來說，`release`（穩定版）分支永遠是首選。
+
+## 使用 SillyTavern 需要什麼？
+
+由於 SillyTavern 僅是一個介面，您需要一個 LLM 後端來提供推理能力。您可以使用 AI Horde 以立即開始聊天。此外，我們支持許多其他本地和雲端 LLM 後端，例如 OpenAI 兼容 API、KoboldAI、Tabby 等。更多支持的 API 資訊，請參閱 [常見問題](https://docs.sillytavern.app/usage/api-connections/)。
+
+### 我需要高效能電腦才能運行 SillyTavern 嗎？
+
+SillyTavern 的硬體需求相當低。任何能夠運行 NodeJS 18 或更高版本的設備都可以執行。若您打算在本地機器上進行 LLM 推理，我們建議使用擁有至少 6GB VRAM 的 3000 系列 NVIDIA 顯示卡。更多詳細資訊，請參考您使用的後端文檔。
+
+### 推薦後端（僅為推薦，非官方合作和隸屬關係）
+
+* [AI Horde](https://aihorde.net/)：使用志願者託管的模型，無需進一步設定
+* [KoboldCpp](https://github.com/LostRuins/koboldcpp)：社群推崇的選擇，可在本地運行 GGUF 模型
+* [tabbyAPI](https://github.com/theroyallab/tabbyAPI)：一個流行且輕量的本地託管 exl2 推理 API
+* [OpenRouter](https://openrouter.ai)：提供多個雲端 LLM 提供商（如 OpenAI、Claude、Meta Llama 等）及熱門社群模型的單一 API
+
+## 有任何問題或建議？
+
+### 歡迎加入我們的 Discord 伺服器
+
+| [![][discord-shield-badge]][discord-link] | [加入我們的 Disocrd 伺服器](https://discord.gg/sillytavern) 以獲得技術支援、分享您喜愛的角色與提示詞。 |
+| :---------------------------------------- | :----------------------------------------------------------------------------------------------------------------- |
+
+或直接聯繫開發者：
+
+* Discord: cohee, rossascends, wolfsblvt
+* Reddit: [/u/RossAscends](https://www.reddit.com/user/RossAscends/), [/u/sillylossy](https://www.reddit.com/user/sillylossy/), [u/Wolfsblvt](https://www.reddit.com/user/Wolfsblvt/)
+* [提交 GitHub 問題](https://github.com/SillyTavern/SillyTavern/issues)
+
+### 我喜歡這個專案，我該如何貢獻呢？
+
+1. **提交拉取要求（Pull Request）**：想了解如何貢獻，請參閱 [CONTRIBUTING.md](../CONTRIBUTING.md)。 
+2. **提供功能建議與問題報告**：使用本專案所提供的模板提交建議或問題報告。
+3. **仔細閱讀此 README 文件及相關文檔**：請避免提出重複問題或建議。
+
+## 螢幕截圖
+
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/9b5f32f0-c3b3-4102-b3f5-0e9213c0f50f">
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/913fdbaa-7d33-42f1-ae2c-89dca41c53d1">
+
+## 角色卡
+
+SillyTavern 的核心概念是「角色卡」（Character Cards）。角色卡是一組設定 LLM 行為的提示詞，用於 SillyTavern 中進行持續性對話。功能類似於 ChatGPT 的 GPT 或 Poe 的聊天機器人。角色卡的內容可以是任何形式：抽象場景、針對特定任務設計的助手、知名人物，或者虛構角色。
+
+角色卡中唯一必填的項目是名稱欄位。若想與語言模型開始一般對話，您只需創建一個名稱為「Assistant」的新卡片，其餘欄位皆可保持空白。若希望進行更具主題性的對話，則可以提供語言模型背景資訊、行為模式、寫作風格以及特定情境來啟動聊天。
+
+如果僅想進行快速對話而不選擇角色卡片，或想測試 LLM 的連線，則可在開啟 SillyTavern 後，於歡迎頁面的輸入欄位中直接輸入您的提示內容。請注意，這類對話是暫時的，不會被永久保存。
+
+若想了解如何設定角色卡，可參考預設角色（如 Seraphina）或從「下載擴充功能 & 資源」（Download Extensions & Assets）選單中下載社群製作的角色卡。
+
+## 核心功能
+
+* 進階文本生成設定：內含許多社群製作的預設設定
+* 支援世界資訊（World Info）：創建豐富的背景故事，或節省角色卡中的 Token（符元）使用
+* 群組聊天：多角色聊天室，可讓角色與您或彼此對話
+* 豐富的 UI 自定義選項：主題顏色、背景圖片、自定義 CSS 等
+* 使用者設定：讓 AI 更了解您並提升沉浸感
+* 內建 RAG 支持：可將文檔加入對話，供 AI 參考
+* 強大的聊天指令子系統：內含 [腳本引擎（Scripting Engine）](https://docs.sillytavern.app/usage/st-script/)
+
+## 擴充功能
+
+SillyTavern 支持多種擴充功能。
+
+* 角色情感表達：使用視覺圖片（立繪）呈現情緒表達
+* 聊天記錄自動摘要
+* 自動化介面與聊天翻譯
+* 穩定擴散（Stable Diffusion）、FLUX 和 DALL-E 的影像生成整合
+* 語音合成：AI 回應的訊息可使用 ElevenLabs、Silero 或系統 TTS 語音合成
+* 網頁搜尋功能：為提示詞添加真實世界的上下文資訊
+* 更多擴展：可從「下載擴充功能 & 資源」（Download Extensions & Assets）選單中下載
+
+想了解如何使用這些擴充功能，請參考：[官方說明文件](https://docs.sillytavern.app/)
+
+# ⌛ 安裝指南
+
+> \[!WARNING]
+>
+> * 請勿將程式安裝到 Windows 的系統控制資料夾（如 Program Files、System32 等）
+> * 請勿以管理員權限執行 Start.bat
+> * 無法在 Windows 7 系統上安裝，因為它無法執行 NodeJS 18.16
+
+## 🪟 Windows
+
+### 使用 Git 安裝
+
+1. 安裝 [NodeJS](https://nodejs.org/en)（建議使用最新的 LTS 版本）
+2. 安裝 [Git for Windows](https://gitforwindows.org/)
+3. 打開 Windows 檔案總管（`Win+E`）
+4. 創建／使用一個不受 Windows 系統控制或監控的資料夾（例如：C:\MySpecialFolder\）
+5. 在該資料夾內開啟命令提示字元（Command Prompt）：點擊地址欄，輸入 `cmd` 並按下 Enter
+6. 當命令提示字元黑框彈出時，輸入以下其中一條指令後，按下 Enter：
+
+* 安裝 Release（穩定版）分支：`git clone https://github.com/SillyTavern/SillyTavern -b release`
+* 安裝 Staging（開發板）分支：`git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+7. 當程式碼下載完成後，雙擊 `Start.bat`，NodeJS 將自動安裝所需的依賴項
+8. 本地伺服器啟動後，SillyTavern 將自動在您的瀏覽器中打開
+
+### 使用 GitHub Desktop 安裝
+
+（此方式僅允許通過 GitHub Desktop 使用 git。如果您也希望在命令列中使用 `git`，則需額外安裝 [Git for Windows](https://gitforwindows.org/)）
+
+  1. 安裝 [NodeJS](https://nodejs.org/en)（建議使用最新的 LTS 版本）
+  2. 安裝 [GitHub Desktop](https://central.github.com/deployments/desktop/desktop/latest/win32)
+  3. 安裝完成後，打開 GitHub Desktop，點擊 `Clone a repository from the internet....` （注意：此步驟 **無需創建 GitHub 帳號**。）
+  4. 在彈出選單中，點擊「URL」選項，輸入此網址：`https://github.com/SillyTavern/SillyTavern`，然後點擊「Clone」。您可以更改「Local path」來選擇 SillyTavern 的下載位置
+  6. 若想開啟 SillyTavern，需使用 Windows 檔案總管以進入您複製儲存庫的資料夾。預設位置為：`C:\Users\[您的 Windows 使用者名稱]\Documents\GitHub\SillyTavern`
+  7. 雙擊 `start.bat` 文件。（請注意：若您的作業系統隱藏了 `.bat` 副檔名，該文件可能顯示為「`Start`」。這就是您需要雙擊運行的文件。）
+  8. 雙擊後，將會彈出一個大型黑色的命令提示字元視窗，SillyTavern 會開始安裝其運行所需的文件與依賴
+  9. 安裝完成後，若一切正常，命令提示字元視窗應顯示運行中的訊息，且您的瀏覽器會自動打開 SillyTavern 頁籤
+  10. 連接到任何 SillyTavern [支援的 APIs](https://docs.sillytavern.app/usage/api-connections/) 並開始聊天吧！
+
+## 🐧 Linux & 🍎 MacOS
+
+對於 MacOS 和 Linux 系統，所有操作都將在終端機（Terminal）中完成。
+
+1. 安裝 git 和 NodeJS（具體方法因操作系統而異）
+2. 複製儲存庫（Clone the repo）：
+
+* 安裝 Release（穩定版）分支：`git clone https://github.com/SillyTavern/SillyTavern -b release`
+* 安裝 Staging（開發板）分支：`git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+3. 使用命令 `cd SillyTavern` 以進入安裝資料夾
+4. 使用以下其中一條命令，以執行 `start.sh` 腳本：
+
+* `./start.sh`
+* `bash start.sh`
+
+## ⚡ 使用 SillyTavern Launcher 安裝
+
+SillyTavern Launcher 是一個安裝嚮導，協助您設定多種選項，包括安裝本地推理（inference）的後端。
+
+### 對於 Windows 使用者
+
+1. 在鍵盤上按下 **`WINDOWS + R`** 打開「執行」對話框，然後輸入以下指令以安裝 git：
+
+```shell
+cmd /c winget install -e --id Git.Git
+```
+
+2. 在鍵盤上按下 **`WINDOWS + E`** 打開檔案總管，導航至您想要安裝 Launcher 的資料夾。在目標資料夾的地址欄輸入 `cmd` 並按下 Enter。接著執行以下命令：
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher && start installer.bat
+```
+
+### 對於 Linux 使用者
+
+1. 打開您喜歡的終端機（Terminal），安裝 git
+2. 使用以下指令以複製 Sillytavern-Launcher：
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+3. 執行安裝腳本（installer.sh）：
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+4. 安裝完成後，執行啟動腳本（launcher.sh）：
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+### 對於 Mac 使用者
+
+1. 打開終端機（Terminal），並使用以下指令安裝 Homebrew：
+
+```shell
+/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+```
+
+2. 使用 Homebrew 以安裝 git：
+
+```shell
+brew install git
+```
+
+3. 使用以下指令以複製 Sillytavern-Launcher：
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+4. 執行安裝腳本（installer.sh）：
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+5. 安裝完成後，執行啟動腳本（launcher.sh）：
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+## 🐋 使用 Docker 安裝
+
+以下指南已假設您安裝 Docker，能夠訪問命令列進行容器安裝，並熟悉 Docker 的基本使用。
+
+### 自行構建映像
+
+我們提供了一份完整的 [SillyTavern Docker 使用指南](http://docs.sillytavern.app/installation/docker/)。該指南涵蓋了 Windows、macOS 和 Linux 的安裝過程。若您希望自行構建映像，建議先閱讀該文檔。
+
+### 使用 GitHub 容器註冊表（最簡易的方式）
+
+您需要設定兩個必要的目錄映射（directory mappings）和一個端口映射（port mapping）來使 SillyTavern 正常運行。在執行指令時，請將以下佔位符替換為您的實際配置：
+
+#### 容器變數
+
+##### 目錄映射（Volume Mappings）
+
+* [config]：用於存放 SillyTavern 設定文件的本地資料夾
+* [data]：用於存放 SillyTavern 使用者數據（包括角色）的本地資料夾
+* [plugins]（可選）：用於存放 SillyTavern 擴充功能的本地資料夾
+
+##### 端口映射（Port Mappings）
+
+* [PublicPort]：對外流量的訪問端口。這是必需的，因為您將從虛擬機容器外部訪問實例。除非實施了額外的安全服務，否則請勿將此端口暴露於網路
+
+##### 其他設定（Additional Settings）
+
+* [DockerNet]：容器應連接的 Docker 網路。如果您不熟悉此概念，請參閱 [Docker 官方說明文件](https://docs.docker.com/reference/cli/docker/network/)
+* [version]：在 GitHub 頁面的右側，您可以找到「Packages」。選擇「sillytavern」包，然後查看映像版本。「latest」標籤會使您保持與當前版本同步。您也可以選擇「staging」或「release」標籤，但這可能不適用於依賴擴充功能的使用者，因為擴充功能可能需要時間進行更新
+
+#### 安裝命令
+
+1. 打��命令列（Command Line）
+2. 執行以下指令：
+
+`docker create --name='sillytavern' --net='[DockerNet]' -p '8000:8000/tcp' -v '[plugins]':'/home/node/app/plugins':'rw' -v '[config]':'/home/node/app/config':'rw' -v '[data]':'/home/node/app/data':'rw' 'ghcr.io/sillytavern/sillytavern:[version]'`
+
+> 請注意：默認的監聽端口為 8000。如果您在設定文件中更改了此端口，請務必使用適當的端口號
+
+## 📱 於 Android 系統中使用 Termux 安裝
+
+> \[!NOTE]
+> **雖然您可以在 Android 設備上使用 Termux 直接運行 SillyTavern，但這不在我們的官方支持範圍內。**
+>
+> **請參閱 ArroganceComplex#2659 所提供的指南：**
+>
+> * <https://rentry.org/STAI-Termux>
+
+**不支援：Android ARM LEtime-web。** 32 位 Android 系統需要額外的依賴項，這無法通過 npm 安裝。請使用以下命令安裝：`pkg install esbuild`。完成後，請按照普通的安裝步驟進行操作
+
+## API 金鑰管理
+
+SillyTavern 將您的 API 金鑰（Keys）保存在使用者數據目錄中的 `secrets.json` 文件內（默認路徑為`/data/default-user/secrets.json`）
+
+默認情況下，API 金鑰在您保存並重新載入頁面後，將不會自介面中顯示
+
+如需啟用查看金鑰功能：
+
+1. 在 `config.yaml` 文件中，將 `allowKeysExposure` 的「值」設為 `true`
+2. 重新啟動 SillyTavern 伺服器
+3. 點擊 API 連線頁面右下角的「查看隱藏的 API 金鑰（View hidden API keys）」超連結
+
+## 命令列參數（Command-line Arguments）
+
+您可以在啟動 SillyTavern 伺服器時傳遞命令列參數，以覆蓋 `config.yaml` 文件中的某些設定。
+
+### 範例
+
+```shell
+node server.js --port 8000 --listen false
+# or
+npm run start -- --port 8000 --listen false
+# or（僅適用於 Windows）
+Start.bat --port 8000 --listen false
+```
+
+### Supported arguments
+
+| Option                  | Description                                                                                          | Type     |
+|-------------------------|------------------------------------------------------------------------------------------------------|----------|
+| `--version`             | 顯示版本序號                                                                                           | boolean  |
+| `--enableIPv6`          | 啟用 IPv6                                                                                             | boolean  |
+| `--enableIPv4`          | 啟用 IPv4                                                                                             | boolean  |
+| `--port`                | 設定 SillyTavern 運行的端口。若未提供，則預設使用 `config.yaml` 中的 'port'                                 | number
+| `--dnsPreferIPv6`       | 偏好使用 IPv6 解析 DNS。未提供則默認使用 `config.yaml` 中的 'preferIPv6'                                   | boolean  |
+| `--autorun`             | 自動在瀏覽器中啟動 SillyTavern。未提供則默認使用 `config.yaml` 中的 'autorun'                               | boolean  |
+| `--autorunHostname`     | 自動啟動時的主機名稱，通常建議保持為 'auto'                                                                | string   |
+| `--autorunPortOverride` | 覆蓋自動啟動的端口設定                                                                                   | string   |
+| `--listen`              | SillyTavern 是否可監聽所有網路接口。若未提供，則默認使用 `config.yaml` 中的 'listen'                         | boolean  |
+| `--corsProxy`           | 啟用 CORS 代理。若未提供，則默認使用 `config.yaml`  中的 'enableCorsProxy'                                 | boolean  |
+| `--disableCsrf`         | 停用 CSRF 保護                                                                                        | boolean  |
+| `--ssl`                 | 啟用 SSL                                                                                             | boolean  |
+| `--certPath`            | 設定您證書文件的路徑                                                                                    | string   |
+| `--keyPath`             | 設定您私人金鑰文件的路徑                                                                                 | string   |
+| `--whitelist`           | 啟用白名單模式                                                                                         | boolean  |
+| `--dataRoot`            | 設定數據儲存的根目錄                                                                                    | string   |
+| `--avoidLocalhost`      | 在自動模式下避免使用 'localhost'                                                                        | boolean  |
+| `--basicAuthMode`       | 啟用基本身份驗證模式                                                                                    | boolean  |
+| `--requestProxyEnabled` | 啟用代理以處理外部請求                                                                                  | boolean  |
+| `--requestProxyUrl`     | 設定請求代理的 URL（支持 HTTP 或 SOCKS 協議）                                                            | string   |
+| `--requestProxyBypass`  | 請求代理的例外主機清單（主機列表需以空格分隔）                                                              | array    |
+
+## 遠端連線
+
+遠端連線功能最常用於希望在手機上使用 SillyTavern 的使用者。此時伺服器將由同一 Wi-Fi 網路上的 PC 運行。不過，您也可以設定來自其他網路的遠端連線。
+
+詳細設定指南請參閱 [官方說明文件](https://docs.sillytavern.app/usage/remoteconnections/)。
+
+您還可以選擇設定 SillyTavern 的使用者檔案，並開啟密碼保護（可選）：[使用者設定指南](https://docs.sillytavern.app/installation/st-1.12.0-migration-guide/#users)。
+
+## 遇到任何效能問題？
+
+1. 在「使用者設定」選單（設定介面主題）中，禁用模糊效果（Blur Effect），並開啟「減少動畫效果」（Reduced Motion）
+2. 若使用響應串流傳輸，請將串流的 FPS 設定為較低的值（建議設定為 10-15 FPS）
+3. 確保瀏覽器已啟用 GPU 加速以進行渲染
+
+## 授權與致謝
+
+**本程式（SillyTavern）的發布是基於其可能對使用者有所幫助的期許，但不提供任何形式的保證；包括但不限於對可銷售性（marketability）或特定用途適用性的隱含保證。如需更多詳情，請參閱 GNU Affero 通用公共許可證。**
+
+This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
+
+* [TavernAI](https://github.com/TavernAI/TavernAI) 1.2.8 由 Humi 提供：MIT 許可
+* 經授權使用部分來自 CncAnon 的 TavernAITurbo 模組
+* 視覺小說模式（Visual Novel Mode）的靈感，來源於 PepperTaco 的貢獻（<https://github.com/peppertaco/Tavern/>）
+* Noto Sans 字體由 Google 提供（OFL 許可）
+* 主題圖示由 Font Awesome <https://fontawesome.com> 提供（圖示：CC BY 4.0，字體：SIL OFL 1.1，程式碼：MIT 許可）
+* 預設資源來源於 @OtisAlejandro（包含角色 Seraphina 與知識書）與 @kallmeflocc（SillyTavern 官方 Discord 伺服器成員突破 10K 的慶祝背景）
+* Docker 安裝指南由 [@mrguymiah](https://github.com/mrguymiah) 和 [@Bronya-Rand](https://github.com/Bronya-Rand) 編寫
+
+## 主要貢獻者
+
+[![Contributors](https://contrib.rocks/image?repo=SillyTavern/SillyTavern)](https://github.com/SillyTavern/SillyTavern/graphs/contributors)
+
+<!-- LINK GROUP -->
+[cover]: https://github.com/user-attachments/assets/01a6ae9a-16aa-45f2-8bff-32b5dc587e44
+[discord-link]: https://discord.gg/sillytavern
+[discord-shield-badge]: https://img.shields.io/discord/1100685673633153084?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge

jiuguan2025cc/.github/readme.md

@@ -0,0 +1,432 @@
+<a name="readme-top"></a>
+
+![][cover]
+
+<div align="center">
+
+English | [German](readme-de_de.md) | [中文](readme-zh_cn.md) | [繁體中文](readme-zh_tw.md) | [日本語](readme-ja_jp.md) | [Русский](readme-ru_ru.md) | [한국어](readme-ko_kr.md)
+
+[![GitHub Stars](https://img.shields.io/github/stars/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/stargazers)
+[![GitHub Forks](https://img.shields.io/github/forks/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/network)
+[![GitHub Issues](https://img.shields.io/github/issues/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/issues)
+[![GitHub Pull Requests](https://img.shields.io/github/issues-pr/SillyTavern/SillyTavern.svg)](https://github.com/SillyTavern/SillyTavern/pulls)
+
+</div>
+
+---
+
+SillyTavern provides a single unified interface for many LLM APIs (KoboldAI/CPP, Horde, NovelAI, Ooba, Tabby, OpenAI, OpenRouter, Claude, Mistral and more), a mobile-friendly layout, Visual Novel Mode, Automatic1111 & ComfyUI API image generation integration, TTS, WorldInfo (lorebooks), customizable UI, auto-translate, more prompt options than you'd ever want or need, and endless growth potential via third-party extensions.
+
+We have a [Documentation website](https://docs.sillytavern.app/) to answer most of your questions and help you get started.
+
+## What is SillyTavern?
+
+SillyTavern (or ST for short) is a locally installed user interface that allows you to interact with text generation LLMs, image generation engines, and TTS voice models.
+
+Beginning in February 2023 as a fork of TavernAI 1.2.8, SillyTavern now has over 200 contributors and 2 years of independent development under its belt, and continues to serve as a leading software for savvy AI hobbyists.
+
+## Our Vision
+
+1. We aim to empower users with as much utility and control over their LLM prompts as possible. The steep learning curve is part of the fun!
+2. We do not provide any online or hosted services, nor programmatically track any user data.
+3. SillyTavern is a passion project brought to you by a dedicated community of LLM enthusiasts, and will always be free and open sourced.
+
+## Branches
+
+SillyTavern is being developed using a two-branch system to ensure a smooth experience for all users.
+
+* `release` -🌟 **Recommended for most users.** This is the most stable and recommended branch, updated only when major releases are pushed. It's suitable for the majority of users. Typically updated once a month.
+* `staging` - ⚠️ **Not recommended for casual use.** This branch has the latest features, but be cautious as it may break at any time. Only for power users and enthusiasts. Updates several times daily.
+
+If you're not familiar with using the git CLI or don't understand what a branch is, don't worry! The release branch is always the preferable option for you.
+
+## What do I need other than SillyTavern?
+
+Since SillyTavern is only an interface, you will need access to an LLM backend to provide inference. You can use AI Horde for instant out-of-the-box chatting. Aside from that, we support many other local and cloud-based LLM backends: OpenAI-compatible API, KoboldAI, Tabby, and many more. You can read more about our supported APIs in [the FAQ](https://docs.sillytavern.app/usage/api-connections/).
+
+### Do I need a powerful PC to run SillyTavern?
+
+The hardware requirements are minimal: it will run on anything that can run NodeJS 18 or higher. If you intend to do LLM inference on your local machine, we recommend a 3000-series NVIDIA graphics card with at least 6GB of VRAM. Check your backend's documentation for more details.
+
+### Suggested Backends (not affiliated)
+
+* [AI Horde](https://aihorde.net/) - use models hosted by volunteers. Requires no further setup
+* [KoboldCpp](https://github.com/LostRuins/koboldcpp) - a community's favorite for running GGUF models locally
+* [tabbyAPI](https://github.com/theroyallab/tabbyAPI) - a popular, lightweight, locally-hosted exl2 inference API
+* [OpenRouter](https://openrouter.ai) - a single API for many cloud providers (OpenAI, Claude, Meta Llama, etc.) as well as popular community models.
+
+## Questions or suggestions?
+
+### Discord server
+
+| [![][discord-shield-badge]][discord-link] | [Join our Discord community!](https://discord.gg/sillytavern) Get support, share favorite characters and prompts. |
+| :---------------------------------------- | :----------------------------------------------------------------------------------------------------------------- |
+
+Or get in touch with the developers directly:
+
+* Discord: cohee, rossascends, wolfsblvt
+* Reddit: [/u/RossAscends](https://www.reddit.com/user/RossAscends/), [/u/sillylossy](https://www.reddit.com/user/sillylossy/), [u/Wolfsblvt](https://www.reddit.com/user/Wolfsblvt/)
+* [Post a GitHub issue](https://github.com/SillyTavern/SillyTavern/issues)
+
+### I like your project! How do I contribute?
+
+1. Send pull requests. Learn how to contribute: [CONTRIBUTING.md](../CONTRIBUTING.md)
+2. Send feature suggestions and issue reports using the provided templates.
+3. Read this entire readme file and check the documentation website first, to avoid sending duplicate issues.
+
+## Screenshots
+
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/9b5f32f0-c3b3-4102-b3f5-0e9213c0f50f">
+<img width="500" alt="image" src="https://github.com/user-attachments/assets/913fdbaa-7d33-42f1-ae2c-89dca41c53d1">
+
+## Character Cards
+
+SillyTavern is built around the concept of "character cards". A character card is a collection of prompts that set the behavior of the LLM and is required to have persistent conversations in SillyTavern. They function similarly to ChatGPT's GPTs or Poe's bots. The content of a character card can be anything: an abstract scenario, an assistant tailored for a specific task, a famous personality or a fictional character.
+
+The name field is the only required character card input. To start a neutral conversation with the language model, create a new card simply called "Assistant" and leave the rest of the boxes blank. For a more themed chat, you can provide the language model with various background details, behavior and writing patterns, and a scenario to jump start the chat.
+
+To have a quick conversation without selecting a character card or to just test the LLM connection, simply type your prompt input into the input bar on the Welcome Screen after opening SillyTavern. Please note that such chats are temporary and will not be saved.
+
+To get a general idea on how to define character cards, see the default character (Seraphina) or download selected community-made cards from the "Download Extensions & Assets" menu.
+
+## Key Features
+
+* Advanced text generation settings with many community-made presets
+* World Info support: create rich lore or save tokens on your character card
+* Group chats: multi-bot rooms for characters to talk to you and/or each other
+* Rich UI customization options: theme colors, background images, custom CSS, and more
+* User personas: let the AI know a bit about you for greater immersion
+* Built-in RAG support: add documents to your chats for the AI to reference
+* Extensive chat commands subsystem and own [scripting engine](https://docs.sillytavern.app/usage/st-script/)
+
+## Extensions
+
+SillyTavern has extensibility support.
+
+* Character emotional expressions (sprites)
+* Auto-Summary of the chat history
+* Automatic UI and chat translation
+* Stable Diffusion/FLUX/DALL-E image generation
+* Text-to-speech for AI response messages (via ElevenLabs, Silero, or the OS's System TTS)
+* Web Search capabilities for adding additional real world context to your prompts
+* Many more are available to download from the "Download Extensions & Assets" menu.
+
+Tutorials on how to use them can be found in the [Docs](https://docs.sillytavern.app/).
+
+## ⌛ Installation
+
+### 🪟 Windows
+
+> \[!WARNING]
+>
+> * DO NOT INSTALL INTO ANY WINDOWS CONTROLLED FOLDER (Program Files, System32, etc).
+> * DO NOT RUN START.BAT WITH ADMIN PERMISSIONS
+> * INSTALLATION ON WINDOWS 7 IS IMPOSSIBLE AS IT CAN NOT RUN NODEJS 18.16
+
+#### Installing via Git (recommended)
+
+1. Install [NodeJS](https://nodejs.org/en) (latest LTS version is recommended)
+2. Install [Git for Windows](https://gitforwindows.org/)
+3. Open Windows Explorer (`Win+E`)
+4. Browse to or Create a folder that is not controlled or monitored by Windows. (ex: C:\MySpecialFolder\)
+5. Open a Command Prompt inside that folder by clicking in the 'Address Bar' at the top, typing `cmd`, and pressing Enter.
+6. Once the black box (Command Prompt) pops up, type ONE of the following into it and press Enter:
+
+* for Release Branch: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+* for Staging Branch: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+7. Once everything is cloned, double-click `Start.bat` to make NodeJS install its requirements.
+8. The server will then start, and SillyTavern will pop up in your browser.
+
+#### Installing via GitHub Desktop
+
+(This allows git usage **only** in GitHub Desktop, if you want to use `git` on the command line too, you also need to install [Git for Windows](https://gitforwindows.org/))
+
+  1. Install [NodeJS](https://nodejs.org/en) (latest LTS version is recommended)
+  2. Install [GitHub Desktop](https://central.github.com/deployments/desktop/desktop/latest/win32)
+  3. After installing GitHub Desktop, click on `Clone a repository from the internet....` (Note: You **do NOT need** to create a GitHub account for this step)
+  4. On the menu, click the URL tab, enter this URL `https://github.com/SillyTavern/SillyTavern`, and click Clone. You can change the Local path to change where SillyTavern is going to be downloaded.
+  6. To open SillyTavern, use Windows Explorer to browse into the folder where you cloned the repository. By default, the repository will be cloned here: `C:\Users\[Your Windows Username]\Documents\GitHub\SillyTavern`
+  7. Double-click on the `start.bat` file. (Note: the `.bat` part of the file name might be hidden by your OS, in that case, it will look like a file called "`Start`". This is what you double-click to run SillyTavern)
+  8. After double-clicking, a large black command console window should open and SillyTavern will begin to install what it needs to operate.
+  9. After the installation process, if everything is working, the command console window should look like this and a SillyTavern tab should be open in your browser:
+  10. Connect to any of the [supported APIs](https://docs.sillytavern.app/usage/api-connections/) and start chatting!
+
+### 🐧 Linux & 🍎 MacOS
+
+For MacOS / Linux all of these will be done in a Terminal.
+
+1. Install git and nodeJS (the method for doing this will vary depending on your OS)
+2. Clone the repo
+
+* for Release Branch: `git clone https://github.com/SillyTavern/SillyTavern -b release`
+* for Staging Branch: `git clone https://github.com/SillyTavern/SillyTavern -b staging`
+
+3. `cd SillyTavern` to navigate into the install folder.
+4. Run the `start.sh` script with one of these commands:
+
+* `./start.sh`
+* `bash start.sh`
+
+## 🐋 Installing via Docker
+
+These instructions assume you have installed Docker, are able to access your command line for the installation of containers, and familiar with their general operation.
+
+### Using the GitHub Container Registry
+
+#### Docker Compose (easiest)
+
+Grab the `docker-compose.yml` file from the [GitHub Repository](https://github.com/SillyTavern/SillyTavern/blob/release/docker/docker-compose.yml) and run the following command in the directory where the file is located. This will pull the latest release image from the GitHub Container Registry and start the container, automatically creating the necessary volumes.
+
+```shell
+docker-compose up
+```
+
+Customize the `docker-compose.yml` file to your needs. The default port is 8000. If you want to adjust the server configuration using environment variables, read the documentation [here](https://docs.sillytavern.app/administration/config-yaml/#environment-variables).
+
+#### Docker CLI (advanced)
+
+You will need two mandatory directory mappings and a port mapping to allow SillyTavern to function. In the command, replace your selections in the following places:
+
+#### Container Variables
+
+##### Volume Mappings
+
+* `CONFIG_PATH` - The directory where SillyTavern configuration files will be stored on your host machine
+* `DATA_PATH` - The directory where SillyTavern user data (including characters) will be stored on your host machine
+* `PLUGINS_PATH` - (optional) The directory where SillyTavern server plugins will be stored on your host machine
+* `EXTENSIONS_PATH` - (optional) The directory where global UI extensions will be stored on your host machine
+
+##### Port Mappings
+
+* `PUBLIC_PORT` - The port to expose the traffic on. This is mandatory, as you will be accessing the instance from outside of its virtual machine container. DO NOT expose this to the internet without implementing a separate service for security.
+
+##### Additional Settings
+
+* `SILLYTAVERN_VERSION` - On the right-hand side of this GitHub page, you'll see "Packages". Select the "sillytavern" package and you'll see the image versions. The image tag "latest" will keep you up-to-date with the current release. You can also utilize "staging" that points to the nightly image of the respective branch.
+
+#### Running the container
+
+1. Open your Command Line
+2. Run the following command in a folder where you want to store the configuration and data files:
+
+```bash
+SILLYTAVERN_VERSION="latest"
+PUBLIC_PORT="8000"
+CONFIG_PATH="./config"
+DATA_PATH="./data"
+PLUGINS_PATH="./plugins"
+EXTENSIONS_PATH="./extensions"
+
+docker run \
+  --name="sillytavern" \
+  -p "$PUBLIC_PORT:8000/tcp" \
+  -v "$CONFIG_PATH:/home/node/app/config:rw" \
+  -v "$DATA_PATH:/home/node/app/data:rw" \
+  -v "$EXTENSIONS_PATH:/home/node/app/public/scripts/extensions/third-party:rw" \
+  -v "$PLUGINS_PATH:/home/node/app/plugins:rw" \
+  ghcr.io/sillytavern/sillytavern:"$SILLYTAVERN_VERSION"
+```
+
+> By default the container will run in the foreground. If you want to run it in the background, add the `-d` flag to the `docker run` command.
+
+### Building the image yourself
+
+We have a comprehensive guide on using SillyTavern in Docker [here](http://docs.sillytavern.app/installation/docker/) which covers installations on Windows, macOS and Linux! Give it a read if you wish to build the image yourself.
+
+## ⚡ Installing via SillyTavern Launcher
+
+SillyTavern Launcher is an installation wizard that will help you get setup with many options, including installing a backend for local inference.
+
+### For Windows users
+
+1. On your keyboard: press **`WINDOWS + R`** to open Run dialog box. Then, run the following command to install git:
+
+```shell
+cmd /c winget install -e --id Git.Git
+```
+
+2. On your keyboard: press **`WINDOWS + E`** to open File Explorer, then navigate to the folder where you want to install the launcher. Once in the desired folder, type `cmd` into the address bar and press enter. Then, run the following command:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher && start installer.bat
+```
+
+### For Linux users
+
+1. Open your favorite terminal and install git
+2. Git clone the Sillytavern-Launcher with:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+3. Start the installer.sh with:
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+4. After installation start the launcher.sh with:
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+### For Mac users
+
+1. Open a terminal and install brew with:
+
+```shell
+/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+```
+
+2. Install git with:
+
+```shell
+brew install git
+```
+
+3. Git clone the Sillytavern-Launcher with:
+
+```shell
+git clone https://github.com/SillyTavern/SillyTavern-Launcher.git && cd SillyTavern-Launcher
+```
+
+4. Start the installer.sh with:
+
+```shell
+chmod +x install.sh && ./install.sh
+```
+
+5. After installation start the launcher.sh with:
+
+```shell
+chmod +x launcher.sh && ./launcher.sh
+```
+
+## 📱 Installing via Termux on Android OS
+
+> \[!NOTE]
+> **SillyTavern can be run natively on Android devices using Termux, but we do not provide official support for this use case.**
+>
+> **Please refer to this guide by ArroganceComplex#2659:**
+>
+> * <https://rentry.org/STAI-Termux>
+
+**Unsupported platform: android arm LEtime-web.** 32-bit Android requires an external dependency that can't be installed with npm. Use the following command to install it: `pkg install esbuild`. Then run the usual installation steps.
+
+## API keys management
+
+SillyTavern saves your API keys to a `secrets.json` file in the user data directory (`/data/default-user/secrets.json` is the default path).
+
+By default, API keys will not be visible from the interface after you have saved them and refreshed the page.
+
+In order to enable viewing your keys:
+
+1. Set the value of `allowKeysExposure` to `true` in `config.yaml` file.
+2. Restart the SillyTavern server.
+3. Click the 'View hidden API keys' link at the bottom right of the API Connection Panel.
+
+## Command-line arguments
+
+You can pass command-line arguments to SillyTavern server startup to override some settings in `config.yaml`.
+
+### Examples
+
+```shell
+node server.js --port 8000 --listen false
+# or
+npm run start -- --port 8000 --listen false
+# or (Windows only)
+Start.bat --port 8000 --listen false
+```
+
+### Supported arguments
+
+> \[!TIP]
+> None of the arguments are required. If you don't provide them, SillyTavern will use the settings in `config.yaml`.
+
+| Option                  | Description                                                          | Type     |
+|-------------------------|----------------------------------------------------------------------|----------|
+| `--version`             | Show version number                                                  | boolean  |
+| `--dataRoot`            | Root directory for data storage                                      | string   |
+| `--port`                | Sets the port under which SillyTavern will run                       | number   |
+| `--listen`              | SillyTavern will listen on all network interfaces                    | boolean  |
+| `--whitelist`           | Enables whitelist mode                                               | boolean  |
+| `--basicAuthMode`       | Enables basic authentication                                         | boolean  |
+| `--enableIPv4`          | Enables IPv4 protocol                                                | boolean  |
+| `--enableIPv6`          | Enables IPv6 protocol                                                | boolean  |
+| `--listenAddressIPv4`   | Specific IPv4 address to listen to                                   | string   |
+| `--listenAddressIPv6`   | Specific IPv6 address to listen to                                   | string   |
+| `--dnsPreferIPv6`       | Prefers IPv6 for DNS                                                 | boolean  |
+| `--ssl`                 | Enables SSL                                                          | boolean  |
+| `--certPath`            | Path to your certificate file                                        | string   |
+| `--keyPath`             | Path to your private key file                                        | string   |
+| `--autorun`             | Automatically launch SillyTavern in the browser                      | boolean  |
+| `--autorunHostname`     | Autorun hostname                                                     | string   |
+| `--autorunPortOverride` | Overrides the port for autorun                                       | string   |
+| `--avoidLocalhost`      | Avoids using 'localhost' for autorun in auto mode                    | boolean  |
+| `--corsProxy`           | Enables CORS proxy                                                   | boolean  |
+| `--requestProxyEnabled` | Enables a use of proxy for outgoing requests                         | boolean  |
+| `--requestProxyUrl`     | Request proxy URL (HTTP or SOCKS protocols)                          | string   |
+| `--requestProxyBypass`  | Request proxy bypass list (space separated list of hosts)            | array    |
+| `--disableCsrf`         | Disables CSRF protection (NOT RECOMMENDED)                           | boolean  |
+
+## Remote connections
+
+Most often this is for people who want to use SillyTavern on their mobile phones while their PC runs the ST server on the same Wi-Fi network. However, it can be used to allow remote connections from anywhere as well.
+
+Read the detailed guide on how to set up remote connections in the [Docs](https://docs.sillytavern.app/usage/remoteconnections/).
+
+You may also want to configure SillyTavern user profiles with (optional) password protection: [Users](https://docs.sillytavern.app/installation/st-1.12.0-migration-guide/#users).
+
+## Performance issues?
+
+### General tips
+
+1. Disable the Blur Effect and enable Reduced Motion on the User Settings panel (UI Theme toggles category).
+2. If using response streaming, set the streaming FPS to a lower value (10-15 FPS is recommended).
+3. Make sure the browser is enabled to use GPU acceleration for rendering.
+
+### Input lag
+
+Performance degradation, particularly input lag, is most commonly attributed to browser extensions. Known problematic extensions include:
+
+* iCloud Password Manager
+* DeepL Translation
+* AI-based grammar correction tools
+* Various ad-blocking extensions
+
+If you experience performance issues and cannot identify the cause, or suspect an issue with SillyTavern itself, please:
+
+1. [Record a performance profile](https://developer.chrome.com/docs/devtools/performance/reference)
+2. Export the profile as a JSON file
+3. Submit it to the development team for analysis
+
+We recommend first testing with all browser extensions and third-party SillyTavern extensions disabled to isolate the source of the performance degradation.
+
+## License and credits
+
+**This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU Affero General Public License for more details.**
+
+* [TavernAI](https://github.com/TavernAI/TavernAI) 1.2.8 by Humi: MIT License
+* Portions of CncAnon's TavernAITurbo mod used with permission
+* Visual Novel Mode inspired by the work of PepperTaco (<https://github.com/peppertaco/Tavern/>)
+* Noto Sans font by Google (OFL license)
+* Icon theme by Font Awesome <https://fontawesome.com> (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
+* Default content by @OtisAlejandro (Seraphina character and lorebook) and @kallmeflocc (10K Discord Users Celebratory Background)
+* Docker guide by [@mrguymiah](https://github.com/mrguymiah) and [@Bronya-Rand](https://github.com/Bronya-Rand)
+* kokoro-js library by [@hexgrad](https://github.com/hexgrad) (Apache-2.0 License)
+
+## Top Contributors
+
+[![Contributors](https://contrib.rocks/image?repo=SillyTavern/SillyTavern)](https://github.com/SillyTavern/SillyTavern/graphs/contributors)
+
+<!-- LINK GROUP -->
+[cover]: https://github.com/user-attachments/assets/01a6ae9a-16aa-45f2-8bff-32b5dc587e44
+[discord-link]: https://discord.gg/sillytavern
+[discord-shield-badge]: https://img.shields.io/discord/1100685673633153084?color=5865F2&label=discord&labelColor=black&logo=discord&logoColor=white&style=for-the-badge

jiuguan2025cc/.github/workflows/docker-publish.yml

@@ -0,0 +1,94 @@
+# This workflow will publish a docker image for every full release to the GitHub package repository
+
+name: Create Docker Image (Release and Staging)
+
+on:
+  release:
+    # Allow pre-releases
+    types: [published]
+  schedule:
+    # Build the staging image everyday at 00:00 UTC
+    - cron: "0 0 * * *"
+  push:
+    # Temporary workaround
+    branches:
+      - release
+
+env:
+  # This should allow creation of docker images even in forked repositories
+  REPO: ${{ github.repository }}
+  REGISTRY: ghcr.io
+
+jobs:
+  build:
+    if: github.repository == 'SillyTavern/SillyTavern'
+    runs-on: ubuntu-latest
+
+    steps:
+      # Workaround for GitHub repo names containing uppercase characters
+      - name: Set lowercase repo name
+        run: |
+          echo "IMAGE_NAME=${REPO,,}" >> ${GITHUB_ENV}
+
+      # Using the following workaround because currently GitHub Actions
+      # does not support logical AND/OR operations on triggers
+      # It's currently not possible to have `branches` under the `schedule` trigger
+      - name: Checkout the release branch (on release)
+        if: ${{ github.event_name == 'release' || github.event_name == 'push' }}
+        uses: actions/[email protected]
+        with:
+          ref: "release"
+
+      - name: Checkout the staging branch
+        if: ${{ github.event_name == 'schedule' }}
+        uses: actions/[email protected]
+        with:
+          ref: "staging"
+
+      # Get current branch name
+      # This is also part of the workaround for Actions not allowing logical
+      # AND/OR operators on triggers
+      # Otherwise the action triggered by schedule always has ref_name = release
+      - name: Get the current branch name
+        run: |
+          echo "BRANCH_NAME=$(git rev-parse --abbrev-ref HEAD)" >> ${GITHUB_ENV}
+
+      # Setting up QEMU for multi-arch image build
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v3
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Extract metadata (tags, labels) for the image
+        uses: docker/[email protected]
+        id: metadata
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          # Release version tag if the workflow is triggered by a release
+          # Branch name tag if the workflow is triggered by a push
+          # Latest tag if the branch is release and the workflow is triggered by a push
+          tags: |
+            ${{ github.event_name == 'release' && github.ref_name || env.BRANCH_NAME }}
+            ${{ github.event_name == 'push' && env.BRANCH_NAME == 'release' && 'latest' || '' }}
+
+      # Login into package repository as the person who created the release
+      - name: Log in to the Container registry
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      # Build docker image using dockerfile for amd64 and arm64
+      # Tag it with branch name
+      # Assumes branch name is the version number
+      - name: Build and push
+        uses: docker/[email protected]
+        with:
+          context: .
+          platforms: linux/amd64,linux/arm64
+          file: Dockerfile
+          push: true
+          tags: ${{ steps.metadata.outputs.tags }}
+          labels: ${{ steps.metadata.outputs.labels }}

jiuguan2025cc/.github/workflows/issues-auto-manager.yml

@@ -0,0 +1,116 @@
+name: 🛠️ Issues Manager
+
+on:
+  issues:
+    types: [opened, edited, labeled, unlabeled]
+  # Re also listen to comments, to remove stale labels right away
+  issue_comment:
+    types: [created]
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  label-on-content:
+    name: 🏷️ Label Issues by Content
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Repository
+        # Checkout
+        # https://github.com/marketplace/actions/checkout
+        uses: actions/[email protected]
+
+      - name: Auto-Label Issues (Based on Issue Content)
+        # only auto label based on issue content once, on open (to prevent re-labeling removed labels)
+        if: github.event.action == 'opened'
+
+        # Issue Labeler
+        # https://github.com/marketplace/actions/regex-issue-labeler
+        uses: github/[email protected]
+        with:
+          configuration-path: .github/issues-auto-labels.yml
+          enable-versioned-regex: 0
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+
+  label-on-labels:
+    name: 🏷️ Label Issues by Labels
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: ✅ Add "👍 Approved" for relevant labels
+        if: contains(fromJSON('["👩‍💻 Good First Issue", "🙏 Help Wanted", "🪲 Confirmed", "⚠️ High Priority", "❕ Medium Priority", "💤 Low Priority"]'), github.event.label.name)
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: 'add-labels'
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          labels: '👍 Approved'
+
+      - name: ❌ Remove progress labels when issue is marked done or stale
+        if: contains(fromJSON('["✅ Done", "✅ Done (staging)", "⚰️ Stale", "❌ wontfix"]'), github.event.label.name)
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: 'remove-labels'
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          labels: '🧑‍💻 In Progress,🤔 Unsure,🤔 Under Consideration'
+
+      - name: ❌ Remove temporary labels when confirmed labels are added
+        if: contains(fromJSON('["❌ wontfix","👍 Approved","👩‍💻 Good First Issue"]'), github.event.label.name)
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: 'remove-labels'
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          labels: '🤔 Unsure,🤔 Under Consideration'
+
+      - name: ❌ Remove no bug labels when "🪲 Confirmed" is added
+        if: github.event.label.name == '🪲 Confirmed'
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: 'remove-labels'
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          labels: '✖️ Not Reproducible,✖️ Not A Bug'
+
+  remove-stale-label:
+    name: 🗑️ Remove Stale Label on Comment
+    runs-on: ubuntu-latest
+    # Only run this on new comments, to automatically remove the stale label
+    if: github.event_name == 'issue_comment' && github.actor != 'github-actions[bot]'
+
+    steps:
+      - name: Remove Stale Label
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: 'remove-labels'
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number }}
+          labels: '⚰️ Stale,🕸️ Inactive,🚏 Awaiting User Response,🛑 No Response'
+
+  write-auto-comments:
+    name: 💬 Post Issue Comments Based on Labels
+    needs: [label-on-content, label-on-labels]
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Repository
+        # Checkout
+        # https://github.com/marketplace/actions/checkout
+        uses: actions/[email protected]
+
+      - name: Post Issue Comments Based on Labels
+        # Label Commenter
+        # https://github.com/marketplace/actions/label-commenter
+        uses: peaceiris/[email protected]
+        with:
+          config_file: .github/issues-auto-comments.yml
+          github_token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}

jiuguan2025cc/.github/workflows/issues-updates-on-merge.yml

@@ -0,0 +1,45 @@
+name: 🔄 Update Issues on Push
+
+on:
+  push:
+    branches:
+      - staging
+      - release
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  # This runs commits to staging/release, reading the commit messages. Check `pr-auto-manager.yml`:`update-linked-issues` for PR-linked updates.
+  update-linked-issues:
+    name: 🔗 Mark Linked Issues Done on Push
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Repository
+        # Checkout
+        # https://github.com/marketplace/actions/checkout
+        uses: actions/[email protected]
+
+      - name: Extract Linked Issues from Commit Message
+        id: extract_issues
+        run: |
+          ISSUES=$(git log ${{ github.event.before }}..${{ github.event.after }} --pretty=%B | grep -oiE '(close|closes|closed|fix|fixes|fixed|resolve|resolves|resolved) #([0-9]+)' | awk '{print $2}' | tr -d '#' | jq -R -s -c 'split("\n")[:-1]')
+          echo "issues=$ISSUES" >> $GITHUB_ENV
+
+      - name: Label Linked Issues
+        id: label_linked_issues
+        env:
+          GH_TOKEN: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+        run: |
+            for ISSUE in $(echo $issues | jq -r '.[]'); do
+            if [ "${{ github.ref }}" == "refs/heads/staging" ]; then
+              LABEL="✅ Done (staging)"
+              gh issue edit $ISSUE -R ${{ github.repository }} --add-label "$LABEL"
+            elif [ "${{ github.ref }}" == "refs/heads/release" ]; then
+              LABEL="✅ Done"
+              gh issue edit $ISSUE -R ${{ github.repository }} --add-label "$LABEL"
+            fi
+            echo "Added label '$LABEL' to issue #$ISSUE"
+            done

jiuguan2025cc/.github/workflows/job-close-stale.yml

@@ -0,0 +1,100 @@
+name: 🕒 Close Stale Issues/PRs Workflow
+
+on:
+  # Run the workflow every day
+  workflow_dispatch:
+  schedule:
+    - cron: '0 0 * * *' # Runs every day at midnight UTC
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  mark-inactivity:
+    name: ⏳ Mark Issues/PRs without Activity
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Mark Issues/PRs without Activity
+        # Close Stale Issues and PRs
+        # https://github.com/marketplace/actions/close-stale-issues
+        uses: actions/[email protected]
+        with:
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          days-before-stale: 183
+          days-before-close: 7
+          operations-per-run: 30
+          remove-stale-when-updated: true
+          enable-statistics: true
+          stale-issue-message: >
+            ⏳ This issue has been inactive for 6 months. If it's still relevant, drop a comment below to keep it open.
+            Otherwise, it will be auto-closed in 7 days.
+          stale-pr-message: >
+            ⏳ This PR has been inactive for 6 months. If it's still relevant, update it or remove the stale label.
+            Otherwise, it will be auto-closed in 7 days.
+          close-issue-message: >
+            🔒 This issue was auto-closed due to inactivity for over 6 months.
+          close-pr-message: >
+            🔒 This PR was auto-closed due to inactivity for over 6 months.
+          stale-issue-label: '⚰️ Stale'
+          close-issue-label: '🕸️ Inactive'
+          stale-pr-label: '⚰️ Stale'
+          close-pr-label: '🕸️ Inactive'
+          exempt-issue-labels: '📌 Keep Open'
+          exempt-pr-labels: '📌 Keep Open'
+
+  await-user-response:
+    name: ⚠️ Mark Issues/PRs Awaiting User Response
+    runs-on: ubuntu-latest
+    needs: mark-inactivity
+
+    steps:
+      - name: Mark Issues/PRs Awaiting User Response
+        # Close Stale Issues and PRs
+        # https://github.com/marketplace/actions/close-stale-issues
+        uses: actions/[email protected]
+        with:
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          days-before-stale: 7
+          days-before-close: 7
+          operations-per-run: 30
+          remove-stale-when-updated: true
+          stale-issue-message: >
+            ⚠️ Hey! We need some more info to move forward with this issue.
+            Please provide the requested details in the next few days to keep this ticket open.
+          close-issue-message: >
+            🔒 This issue was auto-closed due to no response from user.
+          only-labels: '🚏 Awaiting User Response'
+          labels-to-remove-when-unstale: '🚏 Awaiting User Response'
+          stale-issue-label: '🛑 No Response'
+          close-issue-label: '🕸️ Inactive'
+          exempt-issue-labels: '🚧 Alternative Exists'
+
+  alternative-exists:
+    name: 🔄 Mark Issues with Alternative Exists
+    runs-on: ubuntu-latest
+    needs: await-user-response
+
+    steps:
+      - name: Mark Issues with Alternative Exists
+        # Close Stale Issues and PRs
+        # https://github.com/marketplace/actions/close-stale-issues
+        uses: actions/[email protected]
+        with:
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          days-before-stale: 7
+          days-before-close: 7
+          operations-per-run: 30
+          remove-stale-when-updated: true
+          stale-issue-message: >
+            🔄 An alternative solution has been provided for this issue.
+            Did this solve your problem? If so, we'll go ahead and close it.
+            If you still need help, drop a comment within the next 7 days to keep this open.
+          close-issue-message: >
+            ✅ Closing this issue due to no confirmation on the alternative solution.
+          only-labels: '🚧 Alternative Exists'
+          stale-issue-label: '🚏 Awaiting User Response'
+          close-issue-label: '🕸️ Inactive'
+          exempt-issue-labels: '📌 Keep Open'

jiuguan2025cc/.github/workflows/npm-publish.yml

@@ -0,0 +1,32 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+      - run: npm ci
+
+  publish-npm:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.npm_token}}

jiuguan2025cc/.github/workflows/on-close-handler.yml

@@ -0,0 +1,28 @@
+name: 🚪 Issues/PRs On Close Handler
+
+on:
+  issues:
+    types: [closed]
+  pull_request_target:
+    types: [closed]
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  remove-labels:
+    name: 🗑️ Remove Pending Labels on Close
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Remove Pending Labels on Close
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: remove-labels
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number || github.event.pull_request.number }}
+          labels: '🚏 Awaiting User Response,🧑‍💻 In Progress,📌 Keep Open,🚫 Merge Conflicts,🔬 Needs Testing,🔨 Needs Work,⚰️ Stale,⛔ Waiting For External/Upstream'

jiuguan2025cc/.github/workflows/on-open-handler.yml

@@ -0,0 +1,29 @@
+name: 📨 Issues/PRs Open Handler
+
+on:
+  issues:
+    types: [opened]
+  pull_request_target:
+    types: [opened]
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  label-maintainer:
+    name: 🏷️ Label if Author is a Repo Maintainer
+    runs-on: ubuntu-latest
+    if: contains(fromJson('["Cohee1207", "RossAscends", "Wolfsblvt"]'), github.actor)
+
+    steps:
+      - name: Label if Author is a Repo Maintainer
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: 'add-labels'
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.issue.number || github.event.pull_request.number }}
+          labels: '👷 Maintainer'

jiuguan2025cc/.github/workflows/pr-auto-manager.yml

@@ -0,0 +1,212 @@
+name: 🔀 Pull Request Manager
+
+on:
+  pull_request_target:
+    types: [opened, synchronize, reopened, edited, labeled, unlabeled, closed]
+  pull_request_review_comment:
+    types: [created]
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  label-by-size:
+    name: 🏷️ Label PR by Size
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Label PR Size
+        # Pull Request Size Labeler
+        # https://github.com/marketplace/actions/pull-request-size-labeler
+        uses: codelytv/[email protected]
+        with:
+          GITHUB_TOKEN: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          xs_label: '🟩 ⬤○○○○'
+          xs_max_size: '20'
+          s_label: '🟩 ⬤⬤○○○'
+          s_max_size: '100'
+          m_label: '🟨 ⬤⬤⬤○○'
+          m_max_size: '500'
+          l_label: '🟧 ⬤⬤⬤⬤○'
+          l_max_size: '1000'
+          xl_label: '🟥 ⬤⬤⬤⬤⬤'
+          fail_if_xl: 'false'
+          github_api_url: 'https://api.github.com'
+          files_to_ignore: |
+            "package-lock.json"
+            "public/lib/*"
+
+  label-by-branches:
+    name: 🏷️ Label PR by Branches
+    needs: [label-by-size]
+    runs-on: ubuntu-latest
+    # Run, even if the previous jobs were skipped/failed
+    # Only label once when PR is created or branches are changed, to allow manual label removal
+    if: |
+      always()
+      && github.event.action == 'opened' || (github.event.action == 'synchronize' && (github.event.changes.base || github.event.changes.head))
+
+    steps:
+      - name: Checkout Repository
+        # Checkout
+        # https://github.com/marketplace/actions/checkout
+        uses: actions/[email protected]
+
+      - name: Apply Labels Based on Branch Name and Target Branch
+        # Pull Request Labeler
+        # https://github.com/marketplace/actions/labeler
+        uses: actions/[email protected]
+        with:
+          configuration-path: .github/pr-auto-labels-by-branch.yml
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+
+  label-by-files:
+    name: 🏷️ Label PR by Files
+    needs: [label-by-branches]
+    runs-on: ubuntu-latest
+    # Run, even if the previous jobs were skipped/failed
+    if: always()
+
+    steps:
+      - name: Checkout Repository
+        # Checkout
+        # https://github.com/marketplace/actions/checkout
+        uses: actions/[email protected]
+
+      - name: Apply Labels Based on Changed Files
+        # Pull Request Labeler
+        # https://github.com/marketplace/actions/labeler
+        uses: actions/[email protected]
+        with:
+          configuration-path: .github/pr-auto-labels-by-files.yml
+          repo-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+
+  remove-stale-label:
+    name: 🗑️ Remove Stale Label on Comment
+    needs: [label-by-files]
+    runs-on: ubuntu-latest
+    # Only runs when this is not done by the github actions bot
+    if: |
+      always()
+      && github.event_name == 'pull_request_review_comment' && github.actor != 'github-actions[bot]'
+
+    steps:
+      - name: Remove Stale Label
+        # 🤖 Issues Helper
+        # https://github.com/marketplace/actions/issues-helper
+        uses: actions-cool/[email protected]
+        with:
+          actions: 'remove-labels'
+          token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          issue-number: ${{ github.event.pull_request.number }}
+          labels: '⚰️ Stale'
+
+  check-merge-blocking-labels:
+    name: 🚫 Check Merge Blocking Labels
+    needs: [label-by-size, label-by-branches, label-by-files, remove-stale-label]
+    runs-on: ubuntu-latest
+    # Run, even if the previous jobs were skipped/failed
+    if: always()
+
+    # Override permissions, as this needs to write a check
+    permissions:
+      checks: write
+      contents: read
+      pull-requests: read
+
+    steps:
+      - name: Check Merge Blocking
+        # GitHub Script
+        # https://github.com/marketplace/actions/github-script
+        id: label-check
+        uses: actions/[email protected]
+        with:
+          script: |
+            const prLabels = context.payload.pull_request.labels.map(label => label.name);
+            const blockingLabels = [
+              "⛔ Don't Merge",
+              "🔨 Needs Work",
+              "🔬 Needs Testing",
+              "⛔ Waiting For External/Upstream",
+              "❗ Against Release Branch",
+              "💥💣 Breaking Changes"
+            ];
+            const hasBlockingLabel = prLabels.some(label => blockingLabels.includes(label));
+
+            if (hasBlockingLabel) {
+              console.log("Blocking label detected. Setting warning status.");
+              await github.rest.checks.create({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                name: "PR Label Warning",
+                head_sha: context.payload.pull_request.head.sha,
+                status: "completed",
+                conclusion: "neutral",
+                output: {
+                  title: "Potential Merge Issue",
+                  summary: "This PR has a merge-blocking label. Proceed with caution."
+                }
+              });
+            } else {
+              console.log("No merge-blocking labels found.");
+            }
+
+  write-auto-comments:
+    name: 💬 Post PR Comments Based on Labels
+    needs: [label-by-size, label-by-branches, label-by-files, remove-stale-label]
+    runs-on: ubuntu-latest
+    # Run, even if the previous jobs were skipped/failed
+    if: always()
+
+    steps:
+      - name: Checkout Repository
+        # Checkout
+        # https://github.com/marketplace/actions/checkout
+        uses: actions/[email protected]
+
+      - name: Post PR Comments Based on Labels
+        # Label Commenter for PRs
+        # https://github.com/marketplace/actions/label-commenter
+        uses: peaceiris/[email protected]
+        with:
+          config_file: .github/pr-auto-comments.yml
+          github_token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+
+  # This runs on merged PRs to staging, reading the PR body and directly linked issues. Check `issues-updates-on-merge.yml`:`update-linked-issues` for commit-based updates.
+  update-linked-issues:
+    name: 🔗 Mark Linked Issues Done on Staging Merge
+    runs-on: ubuntu-latest
+    if: github.event.pull_request.merged == true && github.event.pull_request.base.ref == 'staging'
+
+    steps:
+      - name: Extract Linked Issues From PR Description
+        id: extract_issues
+        run: |
+            ISSUES=$(jq -r '.pull_request.body' "$GITHUB_EVENT_PATH" | grep -oiE '(close|closes|closed|fix|fixes|fixed|resolve|resolves|resolved) #([0-9]+)' | awk '{print $2}' | tr -d '#' | jq -R -s -c 'split("\n")[:-1]')
+            echo "issues=$ISSUES" >> $GITHUB_ENV
+
+      - name: Fetch Directly Linked Issues
+        id: fetch_linked_issues
+        run: |
+          PR_NUMBER=${{ github.event.pull_request.number }}
+          REPO=${{ github.repository }}
+          API_URL="https://api.github.com/repos/$REPO/pulls/$PR_NUMBER/issues"
+          ISSUES=$(curl -s -H "Authorization: token ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}" "$API_URL" | jq -r '.[].number' | jq -R -s -c 'split("\n")[:-1]')
+          echo "linked_issues=$ISSUES" >> $GITHUB_ENV
+
+      - name: Merge Issue Lists
+        id: merge_issues
+        run: |
+          ISSUES=$(jq -c -n --argjson a "$issues" --argjson b "$linked_issues" '$a + $b | unique')
+          echo "final_issues=$ISSUES" >> $GITHUB_ENV
+
+      - name: Label Linked Issues
+        id: label_linked_issues
+        env:
+          GH_TOKEN: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+        run: |
+          for ISSUE in $(echo $final_issues | jq -r '.[]'); do
+            gh issue edit $ISSUE -R ${{ github.repository }} --add-label "✅ Done (staging)"
+            echo "Added label '✅ Done (staging)' to issue #$ISSUE"
+          done

jiuguan2025cc/.github/workflows/pr-check-merge-conflicts.yaml

@@ -0,0 +1,28 @@
+name: ⚔️ Check Merge Conflicts
+
+on:
+  # So that PRs touching the same files as the push are updated
+  push:
+  # So that the `dirtyLabel` is removed if conflicts are resolved
+  pull_request_target:
+    types: [synchronize]
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  check-merge-conflicts:
+    name: ⚔️ Check Merge Conflicts
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check Merge Conflicts
+        # Label Conflicting Pull Requests
+        # https://github.com/marketplace/actions/label-conflicting-pull-requests
+        uses: eps1lon/[email protected]
+        with:
+          dirtyLabel: '🚫 Merge Conflicts'
+          repoToken: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
+          commentOnDirty: >
+            ⚠️ This PR has conflicts that need to be resolved before it can be merged.

jiuguan2025cc/.github/workflows/update-i18n.yaml

@@ -0,0 +1,32 @@
+name: Update i18n data
+
+on: workflow_dispatch
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:                # Job-level permissions configuration starts here
+      contents: write           # 'write' access to repository contents
+    steps:
+    - name: disable auto crlf
+      uses: steve02081504/disable-autocrlf@v1
+    - uses: actions/checkout@v4
+      with:
+        ref: ${{ github.head_ref }}
+        fetch-depth: 0 # otherwise, there would be errors pushing refs to the destination repository.
+    - name: Create local changes
+      run: |
+        aria2c https://raw.githubusercontent.com/SillyTavern/SillyTavern-i18n/main/generate.py
+        aria2c https://raw.githubusercontent.com/SillyTavern/SillyTavern-i18n/main/requirements.txt
+        pip install -r ./requirements.txt
+        python ./generate.py "" --sort-keys
+        rm -f ./generate.py ./requirements.txt
+    - name: add all
+      run: git add -A
+    - name: push
+      uses: actions-go/push@master
+      with:
+        author-email: 41898282+github-actions[bot]@users.noreply.github.com
+        author-name: github-actions[bot]
+        commit-message: 'i18n changes'
+        remote: origin

jiuguan2025cc/.gitignore

@@ -0,0 +1,57 @@
+node_modules/
+public/chats/
+public/characters/
+public/User Avatars/
+public/backgrounds/
+public/groups/
+public/group chats/
+public/worlds/
+public/user/
+public/css/bg_load.css
+public/themes/
+public/OpenAI Settings/
+public/KoboldAI Settings/
+public/NovelAI Settings/
+public/TextGen Settings/
+public/instruct/
+public/context/
+public/scripts/extensions/third-party/
+public/stats.json
+/uploads/
+*.jsonl
+/config.conf
+/config.yaml
+/config.conf.bak
+/docker/config
+/docker/user
+/docker/extensions
+/docker/data
+.DS_Store
+public/settings.json
+/thumbnails
+whitelist.txt
+.vscode/**
+!.vscode/extensions.json
+.idea/
+secrets.json
+/dist
+/backups/
+public/movingUI/
+public/QuickReplies/
+content.log
+cloudflared.exe
+public/assets/
+access.log
+/vectors/
+/cache/
+public/css/user.css
+public/error/
+/plugins/
+/data
+/default/scaffold
+public/scripts/extensions/third-party
+/certs
+.aider*
+.env
+/StartDev.bat
+

jiuguan2025cc/.npmignore

@@ -0,0 +1,14 @@
+node_modules/
+/uploads/
+.DS_Store
+/thumbnails
+secrets.json
+/dist
+/backups/
+/data
+/cache
+access.log
+.github
+.vscode
+.git
+/public/scripts/extensions/third-party

jiuguan2025cc/.replit

@@ -0,0 +1,81 @@
+
+hidden = [".config", "package-lock.json"]
+run = "chmod 755 ./start.sh && ./start.sh"
+entrypoint = "server.js"
+
+[[hints]]
+regex = "Error \\[ERR_REQUIRE_ESM\\]"
+message = "We see that you are using require(...) inside your code. We currently do not support this syntax. Please use 'import' instead when using external modules. (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import)"
+
+[nix]
+channel = "stable-22_11"
+
+[env]
+XDG_CONFIG_HOME = "/home/runner/$REPL_SLUG/.config"
+PATH = "/home/runner/$REPL_SLUG/.config/npm/node_global/bin:/home/runner/$REPL_SLUG/node_modules/.bin"
+npm_config_prefix = "/home/runner/$REPL_SLUG/.config/npm/node_global"
+
+[gitHubImport]
+requiredFiles = [".replit", "replit.nix", ".config", "package.json", "package-lock.json"]
+
+[packager]
+language = "nodejs"
+
+  [packager.features]
+  packageSearch = true
+  guessImports = true
+  enabledForHosting = false
+
+[unitTest]
+language = "nodejs"
+
+[debugger]
+support = true
+
+  [debugger.interactive]
+  transport = "localhost:0"
+  startCommand = [ "dap-node" ]
+
+    [debugger.interactive.initializeMessage]
+    command = "initialize"
+    type = "request"
+
+      [debugger.interactive.initializeMessage.arguments]
+      clientID = "replit"
+      clientName = "replit.com"
+      columnsStartAt1 = true
+      linesStartAt1 = true
+      locale = "en-us"
+      pathFormat = "path"
+      supportsInvalidatedEvent = true
+      supportsProgressReporting = true
+      supportsRunInTerminalRequest = true
+      supportsVariablePaging = true
+      supportsVariableType = true
+
+    [debugger.interactive.launchMessage]
+    command = "launch"
+    type = "request"
+    
+      [debugger.interactive.launchMessage.arguments]  
+      args = []
+      console = "externalTerminal"
+      cwd = "."
+      environment = []
+      pauseForSourceMap = false
+      program = "./server.js"
+      request = "launch"
+      sourceMaps = true
+      stopOnEntry = false
+      type = "pwa-node"
+
+[languages]
+
+[languages.javascript]
+pattern = "**/{*.js,*.jsx,*.ts,*.tsx,*.json}"
+
+[languages.javascript.languageServer]
+start = "typescript-language-server --stdio"
+
+[deployment]
+run = ["sh", "-c", "./start.sh"]

jiuguan2025cc/.vscode/extensions.json

@@ -0,0 +1,12 @@
+{
+    // See https://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
+    // Extension identifier format: ${publisher}.${name}. Example: vscode.csharp
+    // List of extensions which should be recommended for users of this workspace.
+    "recommendations": [
+        "dbaeumer.vscode-eslint",
+        "EditorConfig.EditorConfig",
+        "mrcrowl.easy-less"
+    ],
+    // List of extensions recommended by VS Code that should not be recommended for users of this workspace.
+    "unwantedRecommendations": []
+}

jiuguan2025cc/CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# How to contribute to SillyTavern
+
+## Setting up the dev environment
+
+1. Required software: git and node.
+2. Recommended editor: Visual Studio Code.
+3. You can also use GitHub Codespaces which sets up everything for you.
+
+## Getting the code ready
+
+1. Register a GitHub account.
+2. Fork this repository under your account. 
+3. Clone the fork onto your machine.
+4. Open the cloned repository in the code editor.
+5. Create a git branch (recommended).
+6. Make your changes and test them locally.
+7. Commit the changes and push the branch to the remote repo.
+8. Go to GitHub, and open a pull request, targeting the upstream branch.
+
+## Contribution guidelines
+
+1. Our standards are pretty low, but make sure the code is not too ugly:
+  - Run VS Code's autoformat when you're done.
+  - Check with ESLint by running `npm run lint`, then fix the errors.
+  - Use common sense and follow existing naming conventions.
+2. Create pull requests for the staging branch, 99% of contributions should go there. That way people could test your code before the next stable release.
+3. You can still send a pull request for release in the following scenarios:
+  - Updating README.
+  - Updating GitHub Actions.
+  - Hotfixing a critical bug.
+4. Project maintainers will test and can change your code before merging.
+5. Write at least somewhat meaningful PR descriptions. There's no "right" way to do it, but the following may help with outlining a general structure:
+  - What is the reason for a change?
+  - What did you do to achieve this?
+  - How would a reviewer test the change?
+6. Mind the license. Your contributions will be licensed under the GNU Affero General Public License. If you don't know what that implies, consult your lawyer.
+
+## Further reading
+
+1. [How to write UI extensions](https://docs.sillytavern.app/for-contributors/writing-extensions/)
+2. [How to write server plugins](https://docs.sillytavern.app/for-contributors/server-plugins)

jiuguan2025cc/Dockerfile

@@ -0,0 +1,51 @@
+FROM node:lts-alpine3.19
+
+# Arguments
+ARG APP_HOME=/home/node/app
+
+# Install system dependencies
+RUN apk add --no-cache gcompat tini git
+
+# Create app directory
+WORKDIR ${APP_HOME}
+
+# Set NODE_ENV to production
+ENV NODE_ENV=production
+
+# Install app dependencies
+COPY package*.json post-install.js ./
+RUN \
+  echo "*** Install npm packages ***" && \
+  npm i --no-audit --no-fund --loglevel=error --no-progress --omit=dev && npm cache clean --force
+
+# Bundle app source
+COPY . ./
+
+# Copy default chats, characters and user avatars to <folder>.default folder
+RUN \
+  rm -f "config.yaml" || true && \
+  ln -s "./config/config.yaml" "config.yaml" || true && \
+  mkdir "config" || true
+
+# Pre-compile public libraries
+RUN \
+  echo "*** Run Webpack ***" && \
+  node "./docker/build-lib.js"
+
+# Cleanup unnecessary files
+RUN \
+  echo "*** Cleanup ***" && \
+  mv "./docker/docker-entrypoint.sh" "./" && \
+  rm -rf "./docker" && \
+  echo "*** Make docker-entrypoint.sh executable ***" && \
+  chmod +x "./docker-entrypoint.sh" && \
+  echo "*** Convert line endings to Unix format ***" && \
+  dos2unix "./docker-entrypoint.sh"
+
+# Fix extension repos permissions
+RUN git config --global --add safe.directory "*"
+
+EXPOSE 8000
+
+# Ensure proper handling of kernel signals
+ENTRYPOINT ["tini", "--", "./docker-entrypoint.sh"]

jiuguan2025cc/LICENSE

@@ -0,0 +1,661 @@
+                    GNU AFFERO GENERAL PUBLIC LICENSE
+                       Version 3, 19 November 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+our General Public Licenses are intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+  A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate.  Many developers of free software are heartened and
+encouraged by the resulting cooperation.  However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+  The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community.  It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server.  Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+  An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals.  This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU Affero General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Remote Network Interaction; Use with the GNU General Public License.
+
+  Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software.  This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the work with which it is combined will remain governed by version
+3 of the GNU General Public License.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero General Public License from time to time.  Such new versions
+will be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU Affero General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU Affero General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero General Public License as published
+    by the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU Affero General Public License for more details.
+
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source.  For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code.  There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU AGPL, see
+<https://www.gnu.org/licenses/>.

jiuguan2025cc/Remote-Link.cmd

@@ -0,0 +1,18 @@
+@echo off
+echo ========================================================================================================================
+echo WARNING: Cloudflare Tunnel!
+echo ========================================================================================================================
+echo This script downloads and runs the latest cloudflared.exe from Cloudflare to set up an HTTPS tunnel to your SillyTavern!
+echo Using the randomly generated temporary tunnel URL, anyone can access your SillyTavern over the Internet while the tunnel
+echo is active. Keep the URL safe and secure your SillyTavern installation by setting a username and password in config.yaml!
+echo.
+echo See https://docs.sillytavern.app/usage/remoteconnections/ for more details about how to secure your SillyTavern install.
+echo.
+echo By continuing you confirm that you're aware of the potential dangers of having a tunnel open and take all responsibility
+echo to properly use and secure it!
+echo.
+echo To abort, press Ctrl+C or close this window now!
+echo.
+pause
+if not exist cloudflared.exe curl -Lo cloudflared.exe https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-amd64.exe
+cloudflared.exe tunnel --url localhost:8000

jiuguan2025cc/SECURITY.md

@@ -0,0 +1,25 @@
+# Security Policy
+
+We take the security of this project seriously. If you discover any security vulnerabilities or have concerns regarding the security of this repository, please reach out to us immediately. We appreciate your efforts in responsibly disclosing the issue and will make every effort to address it promptly.
+
+## Reporting a Vulnerability
+
+To report a security vulnerability, please follow these steps:
+
+1. Go to the **Security** tab of this repository on GitHub.
+2. Click on **"Report a vulnerability"**.
+3. Provide a clear description of the vulnerability and its potential impact. Be as detailed as possible.
+4. If applicable, include steps or a PoC (Proof of Concept) to reproduce the vulnerability.
+5. Submit the report.
+
+Once we receive the private report notification, we will promptly investigate and assess the reported vulnerability.
+
+Please do not disclose any potential vulnerabilities in public repositories, issue trackers, or forums until we have had a chance to review and address the issue.
+
+## Scope
+
+This security policy applies to all the code and files within this repository and its dependencies actively maintained by us. If you encounter a security issue in a dependency that is not directly maintained by us, please follow responsible disclosure practices and report it to the respective project.
+
+While we strive to ensure the security of this project, please note that there may be limitations on resources, response times, and mitigations.
+
+Thank you for your help in making this project more secure.

jiuguan2025cc/Start.bat

@@ -0,0 +1,7 @@
+@echo off
+pushd %~dp0
+set NODE_ENV=production
+call npm install --no-audit --no-fund --loglevel=error --no-progress --omit=dev
+node server.js %*
+pause
+popd

jiuguan2025cc/Update-Instructions.txt

@@ -0,0 +1,75 @@
+How to Update SillyTavern
+
+The most recent version can be found here: https://docs.sillytavern.app/usage/update/
+
+This is not an installation guide. If you need installation instructions, look here:
+https://docs.sillytavern.app/installation/windows/
+
+This guide assumes you have already installed SillyTavern once, and know how to run it on your OS.
+
+Linux/Termux:
+
+You definitely installed via git, so just 'git pull' inside the SillyTavern directory.
+
+Windows/MacOS:
+
+Method 1 - GIT
+
+We always recommend users install using 'git'. Here's why:
+
+When you have installed via `git clone`, all you have to do to update is type `git pull` in a command line in the ST folder.
+You can also try running the 'UpdateAndStart.bat' file, which will almost do the same thing. (Windows only)
+Alternatively, if the command prompt gives you problems (and you have GitHub Desktop installed), you can use the 'Repository' menu and select 'Pull'.
+The updates are applied automatically and safely.
+
+If you are a developer and use a fork of ST or switch branches regularly, you can use the 'UpdateForkAndStart.bat', which works similarly to 'UpdateAndStart.bat',
+but automatically pulls changes into your fork and handles switched branches gracefully by asking if you want to switch back.
+
+Method 2 - ZIP
+
+If you insist on installing via a zip, here is the tedious process for doing the update:
+
+1. Download the new release zip.
+2. Unzip it into a folder OUTSIDE of your current ST installation.
+3. Do the usual setup procedure for your OS to install the NodeJS requirements.
+
+4a. Updating 1.12.0 and above
+
+Copy the user data directory from your data root into the data root of the new install.
+
+By default: /data/default-user
+
+4a. Migrating from <1.12.0 to >=1.20.0
+Copy the following files/folders as necessary(*) from your old ST installation:
+
+  - Assets
+  - Backgrounds
+  - Characters
+  - Chats
+  - Context
+  - Groups
+  - Group chats
+  - Instruct
+  - movingUI
+  - KoboldAI Settings
+  - NovelAI Settings
+  - OpenAI Settings (Chat Completion API)
+  - TextGen Settings (Text Completion API)
+  - QuickReplies
+  - Themes
+  - User Avatars
+  - Worlds
+  - User
+  - settings.json
+  - secrets.json <---- This one is in the base folder, not /public/
+
+  (*) 'As necessary' = "If you made any custom content related to those folders".
+  None of the folders are mandatory, so only copy what you need.
+
+  **NB: DO NOT COPY THE ENTIRE /PUBLIC/ FOLDER.**
+  Doing so could break the new install and prevent new features from being present.
+  Paste those items into the /data/default-user folder of the new install.
+
+5. Start SillyTavern once again with the method appropriate to your OS, and pray you got it right.
+
+6. If everything shows up, you can safely delete the old ST folder.

jiuguan2025cc/UpdateAndStart.bat

@@ -0,0 +1,27 @@
+@echo off
+pushd %~dp0
+git --version > nul 2>&1
+if %errorlevel% neq 0 (
+    echo Git is not installed on this system.
+    echo Install it from https://git-scm.com/downloads
+    goto end
+) else (
+    if not exist .git (
+        echo Not running from a Git repository. Reinstall using an officially supported method to get updates.
+        echo See: https://docs.sillytavern.app/installation/windows/
+        goto end
+    )
+    call git pull --rebase --autostash
+    if %errorlevel% neq 0 (
+        REM incase there is still something wrong
+        echo There were errors while updating.
+        echo See the update FAQ at https://docs.sillytavern.app/usage/update/#common-update-problems
+        goto end
+    )
+)
+set NODE_ENV=production
+call npm install --no-audit --no-fund --loglevel=error --no-progress --omit=dev
+node server.js %*
+:end
+pause
+popd

jiuguan2025cc/UpdateForkAndStart.bat

@@ -0,0 +1,110 @@
+@echo off
+@setlocal enabledelayedexpansion
+pushd %~dp0
+
+echo Checking Git installation
+git --version > nul 2>&1
+if %errorlevel% neq 0 (
+    echo Git is not installed on this system.
+    echo Install it from https://git-scm.com/downloads
+    goto end
+)
+
+if not exist .git (
+    echo Not running from a Git repository. Reinstall using an officially supported method to get updates.
+    echo See: https://docs.sillytavern.app/installation/windows/
+    goto end
+)
+
+REM Checking current branch
+FOR /F "tokens=*" %%i IN ('git rev-parse --abbrev-ref HEAD') DO SET CURRENT_BRANCH=%%i
+echo Current branch: %CURRENT_BRANCH%
+
+REM Checking for automatic branch switching configuration
+set AUTO_SWITCH=
+FOR /F "tokens=*" %%j IN ('git config --local script.autoSwitch') DO SET AUTO_SWITCH=%%j
+
+SET TARGET_BRANCH=%CURRENT_BRANCH%
+
+if NOT "!AUTO_SWITCH!"=="" (
+    if "!AUTO_SWITCH!"=="s" (
+        goto autoswitch-staging
+    )
+    if "!AUTO_SWITCH!"=="r" (
+        goto autoswitch-release
+    )
+
+    if "!AUTO_SWITCH!"=="staging" (
+        :autoswitch-staging
+        echo Auto-switching to staging branch
+        git checkout staging
+        SET TARGET_BRANCH=staging
+        goto update
+    )
+    if "!AUTO_SWITCH!"=="release" (
+        :autoswitch-release
+        echo Auto-switching to release branch
+        git checkout release
+        SET TARGET_BRANCH=release
+        goto update
+    )
+
+    echo Auto-switching defined to stay on current branch
+    goto update
+)
+
+if "!CURRENT_BRANCH!"=="staging" (
+    echo Staying on the current branch
+    goto update
+)
+if "!CURRENT_BRANCH!"=="release" (
+    echo Staying on the current branch
+    goto update
+)
+
+echo You are not on 'staging' or 'release'. You are on '!CURRENT_BRANCH!'.
+set /p "CHOICE=Do you want to switch to 'staging' (s), 'release' (r), or stay (any other key)? "
+if /i "!CHOICE!"=="s" (
+    echo Switching to staging branch
+    git checkout staging
+    SET TARGET_BRANCH=staging
+    goto update
+)
+if /i "!CHOICE!"=="r" (
+    echo Switching to release branch
+    git checkout release
+    SET TARGET_BRANCH=release
+    goto update
+)
+
+echo Staying on the current branch
+
+:update
+REM Checking for 'upstream' remote
+git remote | findstr "upstream" > nul
+if %errorlevel% equ 0 (
+    echo Updating and rebasing against 'upstream'
+    git fetch upstream
+    git rebase upstream/%TARGET_BRANCH% --autostash
+    goto install
+)
+
+echo Updating and rebasing against 'origin'
+git pull --rebase --autostash origin %TARGET_BRANCH%
+
+
+:install
+if %errorlevel% neq 0 (
+    echo There were errors while updating.
+    echo See the update FAQ at https://docs.sillytavern.app/usage/update/#common-update-problems
+    goto end
+)
+
+echo Installing npm packages and starting server
+set NODE_ENV=production
+call npm install --no-audit --no-fund --loglevel=error --no-progress --omit=dev
+node server.js %*
+
+:end
+pause
+popd

jiuguan2025cc/backups/!README.md

@@ -0,0 +1,9 @@
+# Looking for setting snapshots or chat backups?
+
+Individual user backups are now located in the data directory.
+
+Example for the default user under default data root:
+
+/data/default-user/backups
+
+This folder remains for historical purposes only.

jiuguan2025cc/colab/GPU.ipynb

@@ -0,0 +1,193 @@
+{
+  "cells": [
+    {
+      "attachments": {},
+      "cell_type": "markdown",
+      "metadata": {},
+      "source": [
+        "**Links**<br>\n",
+        "Extensions API GitHub: https://github.com/SillyTavern/SillyTavern-extras/<br>\n",
+        "SillyTavern community Discord (support and discussion): https://discord.gg/sillytavern"
+      ]
+    },
+    {
+      "cell_type": "code",
+      "execution_count": null,
+      "metadata": {},
+      "outputs": [],
+      "source": [
+        "#@title <-- Tap this if you run on Mobile { display-mode: \"form\" }\n",
+        "#Taken from KoboldAI colab\n",
+        "%%html\n",
+        "<b>Press play on the audio player to keep the tab alive. (Uses only 13MB of data)</b><br/>\n",
+        "<audio src=\"https://henk.tech/colabkobold/silence.m4a\" controls>"
+      ]
+    },
+    {
+      "cell_type": "code",
+      "execution_count": null,
+      "metadata": {
+        "cellView": "form",
+        "id": "lVftocpwCoYw"
+      },
+      "outputs": [],
+      "source": [
+        "#@markdown (RECOMMENDED) Generates an API key for you to use with the API\n",
+        "secure = False #@param {type:\"boolean\"}\n",
+        "#@markdown Allows to run SillyTavern Extras on CPU (use if you're out of daily GPU allowance)\n",
+        "use_cpu = False #@param {type:\"boolean\"}\n",
+        "#@markdown Allows to run Stable Diffusion pipeline on CPU (slow!)\n",
+        "use_sd_cpu = False #@param {type:\"boolean\"}\n",
+        "#@markdown ***\n",
+        "#@markdown Enables the WebSearch module\n",
+        "extras_enable_websearch = True #@param {type:\"boolean\"}\n",
+        "#@markdown ***\n",
+        "#@markdown Loads the image captioning module\n",
+        "extras_enable_caption = True #@param {type:\"boolean\"}\n",
+        "captioning_model = \"Salesforce/blip-image-captioning-large\" #@param [ \"Salesforce/blip-image-captioning-large\", \"Salesforce/blip-image-captioning-base\" ]\n",
+        "#@markdown * Salesforce/blip-image-captioning-large - good base model\n",
+        "#@markdown * Salesforce/blip-image-captioning-base - slightly faster but less accurate\n",
+        "#@markdown ***\n",
+        "#@markdown Loads the sentiment classification model\n",
+        "extras_enable_classify = True #@param {type:\"boolean\"}\n",
+        "classification_model = \"nateraw/bert-base-uncased-emotion\" #@param [\"nateraw/bert-base-uncased-emotion\", \"joeddav/distilbert-base-uncased-go-emotions-student\"]\n",
+        "#@markdown * nateraw/bert-base-uncased-emotion = 6 supported emotions<br>\n",
+        "#@markdown * joeddav/distilbert-base-uncased-go-emotions-student = 28 supported emotions\n",
+        "#@markdown ***\n",
+        "#@markdown Loads the story summarization module\n",
+        "extras_enable_summarize = True #@param {type:\"boolean\"}\n",
+        "summarization_model = \"slauw87/bart_summarisation\" #@param [ \"slauw87/bart_summarisation\", \"Qiliang/bart-large-cnn-samsum-ChatGPT_v3\", \"Qiliang/bart-large-cnn-samsum-ElectrifAi_v10\", \"distilbart-xsum-12-3\" ]\n",
+        "#@markdown * slauw87/bart_summarisation - general purpose summarization model\n",
+        "#@markdown * Qiliang/bart-large-cnn-samsum-ChatGPT_v3 - summarization model optimized for chats\n",
+        "#@markdown * Qiliang/bart-large-cnn-samsum-ElectrifAi_v10 - nice results so far, but still being evaluated\n",
+        "#@markdown * distilbart-xsum-12-3 - faster, but pretty basic alternative\n",
+        "#@markdown ***\n",
+        "#@markdown Enables Silero text-to-speech module\n",
+        "extras_enable_silero_tts = True #@param {type:\"boolean\"}\n",
+        "#@markdown Enables Microsoft Edge text-to-speech module\n",
+        "extras_enable_edge_tts = True #@param {type:\"boolean\"}\n",
+        "#@markdown Enables RVC module\n",
+        "extras_enable_rvc = False #@param {type:\"boolean\"}\n",
+        "#@markdown ***\n",
+        "#@markdown Enables Whisper speech recognition module\n",
+        "extras_enable_whisper_stt = True #@param {type:\"boolean\"}\n",
+        "whisper_model = \"base.en\" #@param [ \"tiny.en\", \"base.en\", \"small.en\", \"medium.en\", \"tiny\", \"base\", \"small\", \"medium\", \"large\" ]\n",
+        "#@markdown There are five model sizes, four with English-only versions, offering speed and accuracy tradeoffs.\n",
+        "#@markdown The .en models for English-only applications tend to perform better, especially for the tiny.en and base.en models.\n",
+        "#@markdown ***\n",
+        "#@markdown Enables SD picture generation\n",
+        "extras_enable_sd = True #@param {type:\"boolean\"}\n",
+        "sd_model = \"ckpt/anything-v4.5-vae-swapped\" #@param [ \"ckpt/anything-v4.5-vae-swapped\", \"hakurei/waifu-diffusion\", \"philz1337/clarity\", \"prompthero/openjourney\", \"ckpt/sd15\", \"stabilityai/stable-diffusion-2-1-base\" ]\n",
+        "#@markdown * ckpt/anything-v4.5-vae-swapped - anime style model\n",
+        "#@markdown * hakurei/waifu-diffusion - anime style model\n",
+        "#@markdown * philz1337/clarity - realistic style model\n",
+        "#@markdown * prompthero/openjourney - midjourney style model\n",
+        "#@markdown * ckpt/sd15 - base SD 1.5\n",
+        "#@markdown * stabilityai/stable-diffusion-2-1-base - base SD 2.1\n",
+        "#@markdown ***\n",
+        "#@markdown Enables ChromaDB module\n",
+        "extras_enable_chromadb = True #@param {type:\"boolean\"}\n",
+        "\n",
+        "import subprocess\n",
+        "import secrets\n",
+        "\n",
+        "# ---\n",
+        "# SillyTavern extras\n",
+        "extras_url = '(disabled)'\n",
+        "params = []\n",
+        "if use_cpu:\n",
+        "    params.append('--cpu')\n",
+        "if use_sd_cpu:\n",
+        "    params.append('--sd-cpu')\n",
+        "if secure:\n",
+        "    params.append('--secure')\n",
+        "params.append('--share')\n",
+        "modules = []\n",
+        "\n",
+        "if extras_enable_caption:\n",
+        "  modules.append('caption')\n",
+        "if extras_enable_summarize:\n",
+        "  modules.append('summarize')\n",
+        "if extras_enable_classify:\n",
+        "  modules.append('classify')\n",
+        "if extras_enable_sd:\n",
+        "  modules.append('sd')\n",
+        "if extras_enable_silero_tts:\n",
+        "  modules.append('silero-tts')\n",
+        "if extras_enable_edge_tts:\n",
+        "  modules.append('edge-tts')\n",
+        "if extras_enable_chromadb:\n",
+        "  modules.append('chromadb')\n",
+        "if extras_enable_whisper_stt:\n",
+        "  modules.append('whisper-stt')\n",
+        "  params.append(f'--stt-whisper-model-path={whisper_model}')\n",
+        "if extras_enable_rvc:\n",
+        "  modules.append('rvc')\n",
+        "  params.append('--max-content-length=2000')\n",
+        "  params.append('--rvc-save-file')\n",
+        "\n",
+        "\n",
+        "if extras_enable_websearch:\n",
+        "    print(\"Enabling WebSearch module\")\n",
+        "    modules.append('websearch')\n",
+        "    !apt update\n",
+        "    !apt install -y chromium-chromedriver\n",
+        "\n",
+        "params.append(f'--classification-model={classification_model}')\n",
+        "params.append(f'--summarization-model={summarization_model}')\n",
+        "params.append(f'--captioning-model={captioning_model}')\n",
+        "params.append(f'--sd-model={sd_model}')\n",
+        "params.append(f'--enable-modules={\",\".join(modules)}')\n",
+        "\n",
+        "\n",
+        "%cd /\n",
+        "!git clone https://github.com/SillyTavern/SillyTavern-extras\n",
+        "%cd /SillyTavern-extras\n",
+        "!git clone https://github.com/Cohee1207/tts_samples\n",
+        "!npm install -g localtunnel\n",
+        "%pip install -r requirements.txt\n",
+        "!wget https://github.com/cloudflare/cloudflared/releases/download/2023.5.0/cloudflared-linux-amd64 -O /tmp/cloudflared-linux-amd64\n",
+        "!chmod +x /tmp/cloudflared-linux-amd64\n",
+        "\n",
+        "if extras_enable_rvc:\n",
+        "  print(\"Installing RVC requirements\")\n",
+        "  %pip install -r requirements-rvc.txt\n",
+        "\n",
+        "# Generate a random API key\n",
+        "api_key = secrets.token_hex(5)\n",
+        "\n",
+        "# Write the API key to api_key.txt\n",
+        "with open('./api_key.txt', 'w') as f:\n",
+        "    f.write(api_key)\n",
+        "print(f\"API Key generated: {api_key}\")\n",
+        "\n",
+        "cmd = f\"python server.py {' '.join(params)}\"\n",
+        "print(cmd)\n",
+        "extras_process = subprocess.Popen(\n",
+        "    cmd, stdout=subprocess.PIPE, stderr=subprocess.STDOUT, cwd='/SillyTavern-extras', shell=True)\n",
+        "print('processId:', extras_process.pid)\n",
+        "while True:\n",
+        "    line = extras_process.stdout.readline().decode().strip()\n",
+        "    if line != None and line != '':\n",
+        "        print(line)\n"
+      ]
+    }
+  ],
+  "metadata": {
+    "accelerator": "GPU",
+    "colab": {
+      "private_outputs": true,
+      "provenance": []
+    },
+    "gpuClass": "standard",
+    "kernelspec": {
+      "display_name": "Python 3",
+      "name": "python3"
+    },
+    "language_info": {
+      "name": "python"
+    }
+  },
+  "nbformat": 4,
+  "nbformat_minor": 0
+}

jiuguan2025cc/default/!DO-NOT-EDIT-THESE-FILES.txt

@@ -0,0 +1,13 @@
+These are master copies of the default content files and are managed by SillyTavern.
+
+Editing any of these files would not only have no effect, but will also cause merge conflicts during update pulls.
+
+You should edit their respective copies instead, for example:
+
+1. /default/config.yaml => /config.yaml
+2. /default/public/css/user.css => /public/css/user.css
+etc.
+
+Any questions? You're always welcome at our official documentation website:
+
+https://docs.sillytavern.app/

jiuguan2025cc/default/config.yaml

@@ -0,0 +1,235 @@
+# -- DATA CONFIGURATION --
+# Root directory for user data storage
+dataRoot: ./data
+# -- SERVER CONFIGURATION --
+# Listen for incoming connections
+listen: false
+# Listen on a specific address, supports IPv4 and IPv6
+listenAddress:
+  ipv4: 0.0.0.0
+  ipv6: '[::]'
+# Enables IPv6 and/or IPv4 protocols. Need to have at least one enabled!
+# - Use option "auto" to automatically detect support
+# - Use true or false (no qoutes) to enable or disable each protocol
+protocol:
+    ipv4: true
+    ipv6: false
+# Prefers IPv6 for DNS. Enable this on ISPs that don't have issues with IPv6
+dnsPreferIPv6: false
+# The hostname that autorun opens.
+# - Use "auto" to let the server decide
+# - Use options like 'localhost', 'st.example.com'
+autorunHostname: "auto"
+# Server port
+port: 8000
+# Overrides the port for autorun in browser.
+# - Use -1 to use the server port.
+# - Specify a port to override the default.
+autorunPortOverride: -1
+# -- SSL options --
+ssl:
+  enabled: false
+  certPath: "./certs/cert.pem"
+  keyPath: "./certs/privkey.pem"
+# -- SECURITY CONFIGURATION --
+# Toggle whitelist mode
+whitelistMode: true
+# Whitelist will also verify IP in X-Forwarded-For / X-Real-IP headers
+enableForwardedWhitelist: true
+# Whitelist of allowed IP addresses
+whitelist:
+  - ::1
+  - 127.0.0.1
+# Automatically whitelist Docker host and gateway IPs
+whitelistDockerHosts: true
+# Toggle basic authentication for endpoints
+basicAuthMode: false
+# Basic authentication credentials
+basicAuthUser:
+  username: "user"
+  password: "password"
+# Enables CORS proxy middleware
+enableCorsProxy: false
+# -- REQUEST PROXY CONFIGURATION --
+requestProxy:
+  # If a proxy is enabled, all outgoing HTTP/HTTPS requests will be routed through it.
+  enabled: false
+  # Proxy URL. Possible protocols: http, https, socks, socks5, socks4, pac
+  url: "socks5://username:[email protected]:1080"
+  # Proxy bypass list. Requests to these hosts won't be routed through the proxy.
+  bypass:
+    - localhost
+    - 127.0.0.1
+# Enable multi-user mode
+enableUserAccounts: false
+# Enable discreet login mode: hides user list on the login screen
+enableDiscreetLogin: false
+# Enable's authlia based auto login. Only enable this if you
+# have setup and installed Authelia as a middle-ware on your
+# reverse proxy
+# https://www.authelia.com/
+# This will use auto login to an account with the same username
+# as that used for authlia. (Ensure the username in authlia
+# is an exact match with that in sillytavern)
+autheliaAuth: false
+# If `basicAuthMode` and this are enabled then
+# the username and passwords for basic auth are the same as those
+# for the individual accounts
+perUserBasicAuth: false
+
+# User session timeout *in seconds* (defaults to 24 hours).
+## Set to a positive number to expire session after a certain time of inactivity
+## Set to 0 to expire session when the browser is closed
+## Set to a negative number to disable session expiration
+sessionTimeout: -1
+# Disable CSRF protection - NOT RECOMMENDED
+disableCsrfProtection: false
+# Disable startup security checks - NOT RECOMMENDED
+securityOverride: false
+# -- LOGGING CONFIGURATION --
+logging:
+  # Enable access logging to access.log file
+  # Records new connections with timestamp, IP address and user agent
+  enableAccessLog: true
+  # Minimum log level to display in the terminal (DEBUG = 0, INFO = 1, WARN = 2, ERROR = 3)
+  minLogLevel: 0
+# -- RATE LIMITING CONFIGURATION --
+rateLimiting:
+  # Use X-Real-IP header instead of socket IP for rate limiting
+  # Only enable this if you are using a properly configured reverse proxy (like Nginx/traefik/Caddy)
+  preferRealIpHeader: false
+# -- ADVANCED CONFIGURATION --
+# Open the browser automatically
+autorun: true
+# Avoids using 'localhost' for autorun in auto mode.
+# use if you don't have 'localhost' in your hosts file
+avoidLocalhost: false
+
+## BACKUP CONFIGURATION
+backups:
+  # Common settings for all backup types
+  common:
+    # Number of backups to keep for each chat and settings file
+    numberOfBackups: 50
+  chat:
+    # Enable automatic chat backups
+    enabled: true
+    # Maximum number of chat backups to keep per user (starting from the most recent). Set to -1 to keep all backups.
+    maxTotalBackups: -1
+    # Interval in milliseconds to throttle chat backups per user
+    throttleInterval: 10000
+
+# THUMBNAILING CONFIGURATION
+thumbnails:
+  # Enable thumbnail generation
+  enabled: true
+  # Image format of avatar thumbnails:
+  # * "jpg": best compression with adjustable quality, no transparency
+  # * "png": preserves transparency but increases filesize by about 100%
+  # Changing this only affects new thumbnails. To recreate the old ones, clear out /thumbnails folder in your user data.
+  format: "jpg"
+  # JPG thumbnail quality (0-100)
+  quality: 95
+  # Maximum thumbnail dimensions per type [width, height]
+  dimensions: { 'bg': [160, 90], 'avatar': [96, 144] }
+
+# PERFORMANCE-RELATED CONFIGURATION
+performance:
+  # Enables lazy loading of character cards. Improves performances with large card libraries.
+  # May have compatibility issues with some extensions.
+  lazyLoadCharacters: false
+  # The maximum amount of memory that parsed character cards can use. Set to 0 to disable memory caching.
+  memoryCacheCapacity: '100mb'
+
+# Allow secret keys exposure via API
+allowKeysExposure: false
+# Skip new default content checks
+skipContentCheck: false
+# Allowed hosts for card downloads
+whitelistImportDomains:
+  - localhost
+  - cdn.discordapp.com
+  - files.catbox.moe
+  - raw.githubusercontent.com
+# API request overrides (for KoboldAI and Text Completion APIs)
+## Note: host includes the port number if it's not the default (80 or 443)
+## Format is an array of objects:
+## - hosts:
+##   - example.com
+##   headers:
+##     Content-Type: application/json
+##   - 127.0.0.1:5001
+##   headers:
+##     User-Agent: "Googlebot/2.1 (+http://www.google.com/bot.html)"
+requestOverrides: []
+
+# EXTENSIONS CONFIGURATION
+extensions:
+  # Enable UI extensions
+  enabled: true
+  # Automatically update extensions when a release version changes
+  autoUpdate: true
+  models:
+    # Enables automatic model download from HuggingFace
+    autoDownload: true
+    # Additional models for extensions. Expects model IDs from HuggingFace model hub in ONNX format
+    classification: Cohee/distilbert-base-uncased-go-emotions-onnx
+    captioning: Xenova/vit-gpt2-image-captioning
+    embedding: Cohee/jina-embeddings-v2-base-en
+    speechToText: Xenova/whisper-small
+    textToSpeech: Xenova/speecht5_tts
+
+# Additional model tokenizers can be downloaded on demand.
+# Disabling will fallback to another locally available tokenizer.
+enableDownloadableTokenizers: true
+# -- OPENAI CONFIGURATION --
+# A placeholder message to use in strict prompt post-processing mode when the prompt doesn't start with a user message
+promptPlaceholder: "[Start a new chat]"
+openai:
+  # Will send a random user ID to OpenAI completion API
+  randomizeUserId: false
+  # If not empty, will add this as a system message to the start of every caption completion prompt
+  # Example: "Perform the instructions to the best of your ability.\n" (for LLaVA)
+  # Not used in image inlining mode
+  captionSystemPrompt: ""
+# -- DEEPL TRANSLATION CONFIGURATION --
+deepl:
+  # Available options: default, more, less, prefer_more, prefer_less
+  formality: default
+# -- MISTRAL API CONFIGURATION --
+mistral:
+  # Enables prefilling of the reply with the last assistant message in the prompt
+  # CAUTION: The prefix is echoed into the completion. You may want to use regex to trim it out.
+  enablePrefix: false
+# -- OLLAMA API CONFIGURATION --
+ollama:
+  # Controls how long the model will stay loaded into memory following the request
+  # * -1: Keep the model loaded indefinitely
+  # * 0: Unload the model immediately after the request
+  # * N (any positive number): Keep the model loaded for N seconds after the request.
+  keepAlive: -1
+  # Controls the "num_batch" (batch size) parameter of the generation request
+  # * -1: Use the default value of the model
+  # * N (positive number): Use the specified value. Must be a power of 2, e.g. 128, 256, 512, etc.
+  batchSize: -1
+# -- ANTHROPIC CLAUDE API CONFIGURATION --
+claude:
+  # Enables caching of the system prompt (if supported).
+  # https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching
+  # -- IMPORTANT! --
+  # Use only when the prompt before the chat history is static and doesn't change between requests
+  # (e.g {{random}} macro or lorebooks not as in-chat injections).
+  # Otherwise, you'll just waste money on cache misses.
+  enableSystemPromptCache: false
+  # Enables caching of the message history at depth (if supported).
+  # https://docs.anthropic.com/en/docs/build-with-claude/prompt-caching
+  # -- IMPORTANT! --
+  # Use with caution. Behavior may be unpredictable and no guarantees can or will be made.
+  # Set to an integer to specify the desired depth. 0 (which does NOT include the prefill)
+  # should be ideal for most use cases.
+  # Any value other than a non-negative integer will be ignored and caching at depth will not be enabled.
+  cachingAtDepth: -1
+# -- SERVER PLUGIN CONFIGURATION --
+enableServerPlugins: false
+# Attempt to automatically update server plugins on startup
+enableServerPluginsAutoUpdate: true

jiuguan2025cc/default/content/Char_Avatar_Comfy_Workflow.json

@@ -0,0 +1,137 @@
+{
+  "3": {
+    "inputs": {
+      "seed": "%seed%",
+      "steps": "%steps%",
+      "cfg": "%scale%",
+      "sampler_name": "%sampler%",
+      "scheduler": "%scheduler%",
+      "denoise": "%denoise%",
+      "model": [
+        "4",
+        0
+      ],
+      "positive": [
+        "6",
+        0
+      ],
+      "negative": [
+        "7",
+        0
+      ],
+      "latent_image": [
+        "12",
+        0
+      ]
+    },
+    "class_type": "KSampler",
+    "_meta": {
+      "title": "KSampler"
+    }
+  },
+  "4": {
+    "inputs": {
+      "ckpt_name": "%model%"
+    },
+    "class_type": "CheckpointLoaderSimple",
+    "_meta": {
+      "title": "Load Checkpoint"
+    }
+  },
+  "6": {
+    "inputs": {
+      "text": "%prompt%",
+      "clip": [
+        "4",
+        1
+      ]
+    },
+    "class_type": "CLIPTextEncode",
+    "_meta": {
+      "title": "CLIP Text Encode (Prompt)"
+    }
+  },
+  "7": {
+    "inputs": {
+      "text": "%negative_prompt%",
+      "clip": [
+        "4",
+        1
+      ]
+    },
+    "class_type": "CLIPTextEncode",
+    "_meta": {
+      "title": "CLIP Text Encode (Negative Prompt)"
+    }
+  },
+  "8": {
+    "inputs": {
+      "samples": [
+        "3",
+        0
+      ],
+      "vae": [
+        "4",
+        2
+      ]
+    },
+    "class_type": "VAEDecode",
+    "_meta": {
+      "title": "VAE Decode"
+    }
+  },
+  "9": {
+    "inputs": {
+      "filename_prefix": "SillyTavern",
+      "images": [
+        "8",
+        0
+      ]
+    },
+    "class_type": "SaveImage",
+    "_meta": {
+      "title": "Save Image"
+    }
+  },
+  "10": {
+    "inputs": {
+      "image": "%char_avatar%"
+    },
+    "class_type": "ETN_LoadImageBase64",
+    "_meta": {
+      "title": "Load Image (Base64) [https://github.com/Acly/comfyui-tooling-nodes]"
+    }
+  },
+  "12": {
+    "inputs": {
+      "pixels": [
+        "13",
+        0
+      ],
+      "vae": [
+        "4",
+        2
+      ]
+    },
+    "class_type": "VAEEncode",
+    "_meta": {
+      "title": "VAE Encode"
+    }
+  },
+  "13": {
+    "inputs": {
+      "upscale_method": "bicubic",
+      "width": "%width%",
+      "height": "%height%",
+      "crop": "center",
+      "image": [
+        "10",
+        0
+      ]
+    },
+    "class_type": "ImageScale",
+    "_meta": {
+      "title": "Upscale Image"
+    }
+  }
+}

jiuguan2025cc/default/content/Default_Comfy_Workflow.json

@@ -0,0 +1,86 @@
+{
+    "3": {
+        "class_type": "KSampler",
+        "inputs": {
+            "cfg": "%scale%",
+            "denoise": 1,
+            "latent_image": [
+                "5",
+                0
+            ],
+            "model": [
+                "4",
+                0
+            ],
+            "negative": [
+                "7",
+                0
+            ],
+            "positive": [
+                "6",
+                0
+            ],
+            "sampler_name": "%sampler%",
+            "scheduler": "%scheduler%",
+            "seed": "%seed%",
+            "steps": "%steps%"
+        }
+    },
+    "4": {
+        "class_type": "CheckpointLoaderSimple",
+        "inputs": {
+            "ckpt_name": "%model%"
+        }
+    },
+    "5": {
+        "class_type": "EmptyLatentImage",
+        "inputs": {
+            "batch_size": 1,
+            "height": "%height%",
+            "width": "%width%"
+        }
+    },
+    "6": {
+        "class_type": "CLIPTextEncode",
+        "inputs": {
+            "clip": [
+                "4",
+                1
+            ],
+            "text": "%prompt%"
+        }
+    },
+    "7": {
+        "class_type": "CLIPTextEncode",
+        "inputs": {
+            "clip": [
+                "4",
+                1
+            ],
+            "text": "%negative_prompt%"
+        }
+    },
+    "8": {
+        "class_type": "VAEDecode",
+        "inputs": {
+            "samples": [
+                "3",
+                0
+            ],
+            "vae": [
+                "4",
+                2
+            ]
+        }
+    },
+    "9": {
+        "class_type": "SaveImage",
+        "inputs": {
+            "filename_prefix": "SillyTavern",
+            "images": [
+                "8",
+                0
+            ]
+        }
+    }
+}