Repository navigation
Conversation
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Plugin Submission
Plugin information
Submission type
What changed
Loom adds tools to remember facts, recall an application's user memories and search documents in a configured Loom deployment. Workflows can retain user context and retrieve documents shared by their namespace through the Loom SDK.
This contribution is prepared for ClickHouse's Loom project. AI assistants contributed implementation and submission preparation. No Dify affiliation or endorsement is claimed.
Risk level
Required checks
.envfiles,.gitdirectories, virtual environments, caches, logs, or IDE files.PRIVACY.mdor a hosted privacy policy, andmanifest.yamlreferences it.Security and privacy notes
The plugin sends configured identity fields, user identifiers, memory keys, fact text and search queries to an administrator-selected Loom endpoint using a bearer token. Remember writes persist in that deployment. Stored inputs and search results may contain personal or sensitive content.
Administrators must trust the endpoint and plugin runner, prefer HTTPS, restrict destinations through deployment network policy and scope tokens to the application's namespace. They must obtain the operator and processor privacy policies applicable to their chosen deployment; no universal hosted processor is prescribed. User ID is an application-controlled form field outside model-generated arguments. Knowledge search reads documents shared by the namespace. Give untrusted applications separate namespaces and token grants.
The plugin adds no local store or telemetry and does not directly call a model. Dify controls credential storage and workflow logs. The Loom deployment controls retention, deletion and any configured embedding or extraction providers. The endpoint has no fixed vendor-domain allowlist.
PRIVACY.mddescribes these boundaries.Requests use 15-second HTTP timeouts, one attempt and a 30-second SDK call wait. Pool admission and client setup/close have separate waits, so these are not a whole-tool deadline. Credential validation reads at most one memory row and discards it. Request failures fail the tool instead of returning empty search results.
Local validation
The current source completed the hosted Community Edition 1.20.0 application check in run44909860029. It performed normal setup and workspace debugging, registered the native tools and completed remember, same-user recall, other-user empty recall and shared-document workflows. It verified all seven persisted identity/value fields in one row, preserved the storage bind across tool execution, purged the test organization and verified owned process/container/volume/network cleanup. Runtime files were retained; no intentional interruption was exercised in that run.
That run built its Loom server and SDK wheel from the tested source. Its isolated plugin environment matched 71 SDK package files to that candidate wheel. The installed metadata version was 1.3.0; this is not a test of the published registry wheel.
The current package is 13,330 bytes with SHA256
318b1e847263d5cebd4a8b9351d5a6919bf989d410bcac7f4ccfef0759e1475f. All 19 members match the linked source, including its packaged README. The current official Marketplace Toolkit at commit83ee707c1dde758678f94a311f15b42d74f8c402reports zero blocking failures, zero execution failures and one dependency-warning category for this archive. Two bounded dependency ranges lack exact versions, so OSV lookups are skipped; no vulnerability clearance is claimed. All 64 source checks and seven workflows pass; the application-check repair is merged.The package validation command is:
The local validator excludes Marketplace duplicate/version checks and install/upload checks. Those require the normal upstream workflow.
Reviewer notes
The canonical repository has no existing
clickhouse/loomplugin path or matching all-state Loom submission. The Marketplace search was unavailable, so current Marketplace name/version availability remains unproved; the development-guidelines box remains unchecked for that limitation. The ordinary upstream duplicate/version and install checks remain required. No acceptance or verification is assumed.Cloud, browser and protected-session behavior are untested. Host dataset/vector retrieval is outside the tools-only check. The manifest's minimum Dify1.0.0 and amd64/arm64 fields declare compatibility targets, not a tested matrix.
verifiedremains false. No Marketplace acceptance or published-registry-wheel runtime qualification is claimed.