@crckss/dsh-remote-trust

Configuration

- insert:
    - id: remote-trust
      name: "@crckss/dsh-remote-trust"
      config:
        # Authorities allowed to call privileged methods.
        # Port-less host matches any port; host:port matches exactly.
        hosts:
          - dsh.example.com
          - 100.34.48.118
        # Optional: open privileged methods beyond the defaults
        # (these are host-native actions, opt-in).
        extraEndpoints:
          - host.pickDirectory
        # Optional: request body ceiling for the forwarded bridge.
        maxRequestBodyBytes: 4194304

Trusted authorities are merged from two places:

• config.hosts — explicit entries in the patch layer;
• ctx.webStartup.trustedHosts — whatever the invocation declared with --trusted-host, plus LAN IP literals derived from the bind (when bound to all interfaces).

So the plugin follows the deployment's existing trust declaration: if you already run dsh web --trusted-host dsh.example.com, the plugin picks that up even with an empty hosts list.

Opened by default

agentPreset.read          agentPreset.copy
agentPreset.openDocument  agentPreset.remove
settings.describe         settings.openDocument
settings.update           settings.replace
settings.mutate
credentials.describe      credentials.set
credentials.unset
llm.discoverModels

host.pickDirectory and host.openPath stay loopback-only unless listed in extraEndpoints.