Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions .github/workflows/dify-plugin.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
name: Dify plugin

on:
pull_request:
paths:
- integrations/dify/**
- .github/workflows/dify-plugin.yml
push:
branches: [main]
paths:
- integrations/dify/**
- .github/workflows/dify-plugin.yml

permissions:
contents: read

jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0 # v7.1.0
with:
python-version: "3.12"
- run: python -m pip install -r requirements.txt pytest
working-directory: integrations/dify
- run: python -m pytest tests -q
working-directory: integrations/dify
- name: Package with the official CLI
run: |
curl --fail --location https://github.com/langgenius/dify-plugin-daemon/releases/download/0.6.15/dify-plugin-linux-amd64 --output "$RUNNER_TEMP/dify"
echo "d0a1e3b25bd6c5f6cd749cad2cf04817ea808344e6cc07a2c49bb0108019ab93 $RUNNER_TEMP/dify" | sha256sum --check
chmod +x "$RUNNER_TEMP/dify"
"$RUNNER_TEMP/dify" plugin package integrations/dify -o loom-0.1.0.difypkg
- uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
with:
name: loom-dify-plugin
path: loom-0.1.0.difypkg
42 changes: 42 additions & 0 deletions docs/architecture/dify-adapter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# Dify tools adapter

The Dify plugin calls Loom through the Python SDK and stores no content locally.
Its three native tools map to `memory.set`, `memory.search` and `knowledge.search`.
The optional standalone package requires the 0.11 plugin SDK minor series and the
Loom 1.x SDK; the server and core SDK do not depend on Dify.

## Invariants

Provider credentials bind the endpoint, organization, namespace, token and agent.
A required User ID form parameter binds the end user outside the model's arguments.
Recall can read that user's memories across Loom agents; documents are shared by the
namespace. Both search operations pin `namespace_scope=this`. Separate namespaces
and token grants constrain mutually untrusted applications. Loom applies its usual
actor, provenance, conflict handling, rolling schema and erasure rules to these calls.

The administrator controls the HTTP destination. The plugin checks its URL shape
and rejects embedded credentials, queries and fragments; deployment network policy
constrains which hosts the plugin runner can reach. Requests have finite timeouts
and one attempt. Tool errors expose no credentials or remote response detail.
The plugin creates no additional database, cache, model provider or telemetry path.

Dify patches Python threading with gevent greenlets. Each request constructs, calls
and closes its SDK client inside the current hub's native thread pool, so overlapping
clients do not run asyncio loops on the same native thread. Credentials stay local to
that request. The SDK call waits at most 30 seconds; pool admission, client setup and
close have separate waits rather than a whole-invocation deadline.

Dify installs the package from a local `.difypkg`. The official CLI packages source,
metadata, runtime requirements, icons, license, README and privacy statement. Its
ignore file excludes tests, environments, credentials and build state. CI invokes
the native tools against a fake SDK HTTP transport, checks overlapping native calls
over loopback HTTP, validates native tool schemas and builds the package.
Live tests run only with an explicit private Loom URL and
token; platform execution is documented separately from those SDK tests.

## Source entry points

- `integrations/dify/client.py`: scoped SDK calls and request failures.
- `integrations/dify/provider/loom.py`: credential validation.
- `integrations/dify/tools/`: native tool implementations and schemas.
- `.github/workflows/dify-plugin.yml`: tests and packaging.
19 changes: 19 additions & 0 deletions docs/features/integrations/frameworks.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ or needs another database, vector store or cache.
| LangGraph | `LoomStore` | Python, `loom.integrations.langgraph` | `BaseStore` |
| Strands Agents | `LoomMemoryStore` | Python, `loom.integrations.strands` | the `MemoryStore` protocol |
| Strands Agents | `LoomMemoryStore` | TypeScript, `@clickhouse/loom/integrations/strands` | the same protocol, structurally |
| Dify | Remember, Recall, Search knowledge | `integrations/dify` standalone plugin | Native Dify tools |

Any other framework that can call an HTTP endpoint or an MCP server uses Loom directly:
see [agent integration](../../guides/agent-integration.md) and
Expand Down Expand Up @@ -630,6 +631,24 @@ with `?toolset=core` and a bearer token, and expose `loom_memory_set` and `loom_
to its AI Agent.
[The MCP client setup](./mcp-clients.md#other-editors-and-agents) describes that route.

## Dify

The [Loom tools plugin](../../../integrations/dify/README.md) runs Remember, Recall and
Search knowledge as native Dify tools. Install its `.difypkg` from a local package
file and configure a reachable Loom URL, a scoped writer token and the deployment's
organization, namespace and agent. Bind the User ID form field to your app's user;
it is separate from model-generated arguments.

Remember stores a fact, Recall searches that user's memories across agents, and
Search knowledge searches shared app documents. Both searches stay in the configured
namespace. The plugin calls the Python SDK, adds no store and keeps data in your Loom
deployment. [Privacy](../../../integrations/dify/PRIVACY.md) describes credentials,
network access, provider processing and retention. The package is tested through the
native plugin SDK against Loom; a Dify application and Dify Cloud have not been tested.

The [MCP/OpenAPI setup](mcp-clients.md#hosted-builders-and-chat-apps) also works without
the package.

## LangGraph

`LoomStore` (`sdk/python/loom/integrations/langgraph.py`) is a LangGraph `BaseStore`, so
Expand Down
3 changes: 3 additions & 0 deletions docs/use-cases/agent-memory.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,3 +81,6 @@ in Loom across agent runs and handoffs.

For a visual workflow, [n8n nodes](../features/integrations/frameworks.md#n8n) connect an
AI Agent to Loom conversation history, durable memories and knowledge search.

Use the [Dify tools plugin](../features/integrations/frameworks.md#dify) to save facts,
recall a user's memories and search app documents from a workflow.
12 changes: 12 additions & 0 deletions integrations/dify/.difyignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
tests/
__pycache__/
*.pyc
.pytest_cache/
.ruff_cache/
.venv/
.env*
.git/
.github/
.gitignore
*.difypkg
pyproject.toml
5 changes: 5 additions & 0 deletions integrations/dify/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
__pycache__/
.pytest_cache/
.venv/
.env*
*.difypkg
201 changes: 201 additions & 0 deletions integrations/dify/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,201 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for describing the origin of the Work and
reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or directory name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright 2026 ClickHouse, Inc.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
22 changes: 22 additions & 0 deletions integrations/dify/PRIVACY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# Privacy

The plugin sends the configured organization, namespace, agent, end-user identifier,
memory keys, fact text and search queries to the Loom endpoint configured by the
Dify administrator. The token is sent in the HTTP Authorization header.

Dify stores provider credentials and may retain workflow inputs, outputs and execution
logs under its own deployment settings. The plugin adds no telemetry, log files or
local data store. It does not send data to the plugin maintainers.

Loom stores memories and documents in the user's Loom deployment. Its configured
providers may process the text for embeddings or memory extraction; the deployment
operator controls those providers and retention. Remember writes persist after the
workflow ends. Use Loom's deletion and erasure operations to remove stored data, and
configure Dify separately to remove workflow traces.

This plugin makes authenticated requests to an administrator-configured URL. Treat
that destination and the Dify plugin runner as trusted; use network policy and scoped
tokens to constrain access.

For privacy questions, use the source repository's security policy:
[ClickHouse/loom security](https://github.com/ClickHouse/loom/security/policy).
Loading
Loading