Settings and feedback

English | 简体中文 | README

Guide: Install · Sources · Resources · Services · Translation · Settings · Workspace

Open Plugins → Installed → Agent Plugins to configure this extension. Its display name, description, and settings follow the DSH interface language. The configuration page carries this plugin’s switches: Scan project Agent layouts (scanProjectLayouts, default off; see project layouts), MCP enhancement, Download region, Background source updates (autoUpdateSources, default off; refreshes every configured source every 6 hours), the experience feedback tool, and Translation (translationEnabled, Chinese on and English off by default, with your saved choice taking priority; see translation). The card stages what you pick and applies it when you press Save, so what is on screen is what saving writes; a setting marked customized also offers Use default, which hands that one setting back to the plugin. Download region starts on Follow interface language, and choosing it again clears your explicit choice.

Session extension presets

Enable the experimental Agent preset manager in plugin settings. It is off by default and controls only entry visibility, not session authorization or existing selections. The composer then has an Agent extension icon button to the right of Permissions in both blank and ongoing sessions. Hover or focus it to read the selected preset name. Its menu lets you select a saved preset or manage this workspace’s preset library. This choice does not replace the host’s base Agent preset.

• Market lists installed market suites. Project resources appear in their respective surface tabs. Hooks lists every event together and each row names its own stage. Existing presets retain their selections. User and project command hooks have individual switches; installed market suite hooks follow their suite selection and the manager lists them read-only, tagged as following the suite. A hook row opens its own read-only declaration: the full command, the declared matcher, the declared timeout and the host support verdict.
• A workspace default seeds new sessions only. Editing the selected or pending preset in the current session updates that session. Every other session keeps its own detached copy.
• Selecting a saved preset while a session runtime is active takes effect on that session’s next user request. Mid-turn steering and tools do not change. In the manager, click a resource card or its switch to enable or disable it in the preset. If saving fails, keep the draft and retry or discard it.
• Copy and paste a preset between workspace panels to create an independent copy. Transfer includes names and resource identifiers, not credentials or server configuration. The identifiers of local configuration (user hooks and project layout suites) never transfer; their grants follow the selected resources.
• A preset can explicitly enable valid installed extensions that are disabled globally, without changing global settings or source files. Native skills and suite resources remain isolated between sessions; shared services stay mounted while another session needs them. Uninstalled, invalid or unsupported resources remain unavailable. MCP tools supplied by the host compatibility backend or another plugin remain globally managed.
• The switch in preset details changes only the resource selection in the preset. Documents and service configuration remain read-only. Configure credentials, authentication and global tools from the corresponding settings page.
• If a selection update fails, the entry reports that the session is not ready. Explicit recovery restores its last committed choice or captured initial choice. If the first capture failed before recording any choice, recovery retries that capture with its original new-session or legacy classification. Successful recovery resumes queued input without another Send; an empty queue starts no model request. Repeated failures wait for another explicit recovery. Pending and committed records remain durable, while new selection and wake markers stay outside model input. Existing historical placeholder messages remain unchanged.

Experience feedback

The feedbackEnabled setting defaults to true. When the host provides tools and settings, it enables the model-facing report_market_issue tool, which files an issue in this plugin’s GitHub repository — through the gh CLI when it is installed and authenticated, otherwise through GITHUB_TOKEN / GH_TOKEN. With none of those available nothing is filed: the tool opens a prefilled “new issue” page in the browser and returns the complete issue text and link to the model, which hands them to you. Accepted submissions have a 60-second cooldown. Disable the setting in the plugin configuration card to unregister the tool.