@illli-studio/dsh-mory

Requirements / 使用条件

• DSH >=0.2.1-rc.5 <0.3.0 with its Web UI, Connection and Tools services.
• Node.js 22.18+ for the Mory runtime and development checks.
• A running Mory service on the computer hosting DSH. The online browser-only repository at me.mory.cloud is not automatically connected or imported.

npm install -g @illli-studio/mory
mory init
mory start --background

If Mory is already running, keep using it. The plugin reads MORY_HOME/config.json or ~/.mory/config.json on the DSH host, respecting its port and token. Memory content stays in the existing Mory SQLite repository; disabling this plugin does not delete it.

Connection configuration / 连接配置

Environment variables are read on the DSH host, not the browser:

• MORY_HOME: directory containing config.json (default ~/.mory).
• MORY_API_URL: override the API origin, for example http://127.0.0.1:8787.
• MORY_API_TOKEN: override the bearer token.

Advanced Loader row config accepts apiUrl, configPath (absolute path), and tokenEnv (environment variable name). Credentials entered in the settings password field are sent to the authenticated DSH backend and stored there; reading settings does not return them. Default row config is {}. To override it in your own bundle patch:

- id: mory
  config:
    apiUrl: 'https://memory.example.com'
    tokenEnv: MORY_REMOTE_TOKEN

Use HTTPS for a remote service. URLs must be origins without path/query/embedded credentials. The plugin does not forward a local token to a remote origin unless an explicit token is entered for that origin or supplied through the environment, and refuses HTTP redirects. Remote hosting must independently provide a compatible authenticated Mory API.

/api/mory is an authenticated, exact POST Fetch route registered through DSH Connection. Stored Mory tokens are never included in settings responses. Requests are limited to 1 MiB, upstream responses to 8 MiB, and upstream calls to 40 seconds. Token configuration errors and revision conflicts are displayed in the panel.