Local System One for Dify — node inputs edition (v0.0.3)

Tool plugin wrapping a self-hosted vLLM endpoint. All three decision arguments are required tool-node inputs, matching an existing Dify OpenAPI custom tool.

Configuration

Provider settings: (without ) and optional . No model ID in provider settings.

Tool node required String inputs:

Input	Example	Purpose
	value of from	exact vLLM model ID
	bind to	text to decide
	see JSON below	full System One questions object as a JSON string, without outer /

Paste the following into (standard JSON; double quotes are required):

Tool outputs

— when is asked. Connect IF/ELSE using exact matches / / .
, — relative model probabilities if present, not calibrated accuracy.
— complete response answers. Supports different question keys and types.
— diagnostic fields when returned by vLLM.

For non-route questions, is empty but the answers are still available.

Packaging

Download a full CLI (not ) from https://github.com/langgenius/dify-plugin-daemon/releases.

From the project parent directory:

Set the in , , before publishing. As this has a new version number (), install/update in Dify and reselect the new tool inputs in the workflow. Do not assume old node bindings migrate automatically.

Notes

The plugin runtime must reach the configured vLLM host. from the plugin usually does not refer to your vLLM container.
The backend must support the selected model on . Registration of the route alone is not enough.
This is a source template. Python syntax and YAML structure have been checked; live Dify SDK packaging and remote inference must be tested in your environment.
is a JSON string and accepts arbitrary named decision questions, provided each question has a .
Outbound connections are confined by the endpoint configured by the workspace operator. Administrators should protect private addresses and review SSRF exposure before public Marketplace publication.

v0.0.3: Dify parameter visibility fix

Changed , , and from to , for visible workflow-node inputs in Dify versions where form parameters do not appear in the tool configuration. The API invocation logic has not changed. Re-add the tool node to reload its parameter schema.

dify-plugin-local-systemone