feat: add ViBo Memory plugin (persistent L1/L2/L3 memory for agents)

[vnbochkarev-netizen]

Plugin Submission

Plugin information

• Author: vnbochkarev-netizen
• Plugin name: vibo
• Version: 0.0.1
• Source repository: https://github.com/vnbochkarev-netizen/ViBo-memory
• Contact: [email protected]

Submission type

• New plugin
• Version update

What changed

Added the ViBo Memory plugin — persistent encrypted memory (L1/L2/L3) for Dify agents.

• memory_search — recall relevant facts (97.5% fewer tokens vs full history)
• memory_add — save facts (L1 public / L2 private / L3 secrets)
• thread_memory — conversation context across sessions
• usage — token savings report

Risk level

• Low risk
• Medium risk
• High risk

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

The plugin makes outbound HTTPS requests only to the ViBo memory API at
https://wwwvibo.com (endpoints /status, /memory/add, /memory/search,
/memory/thread, /usage) using the user-supplied ViBo license key. No
command/code execution, SQL, SSH/SFTP, browser automation, or local filesystem
access. Data stored in ViBo is encrypted (AES-256-GCM) and isolated per key;
L3 secrets never enter the LLM context.

Local validation

• Reproduced every pre-check-plugin validator from langgenius/dify-marketplace-toolkit locally (check-package-contents, check-package-secrets, check-package-binaries, check-manifest-metadata, check-readme-metadata, check-package-dependencies, check-python-safety-warnings, check-prohibited-financial-activity): all pass with zero blocking errors.
• pip install -r requirements.txt (dify_plugin>=0.9.0, requests) resolves and installs cleanly.
• python3 -m main starts the plugin server successfully.

Reviewer notes

• Distributed as a single .difypkg (zip of 20 source files).
• Trial keys at https://wwwvibo.com (2 days, no card); paid plans from $2.5/month.

[vnbochkarev-netizen]

Risk level: Low risk ✅

Justification:

• Simple Python plugin (4 HTTP tools calling a public REST API)
• No system access, no file operations, no network listeners
• Only dependency: dify_plugin + requests (standard)
• Credentials: user-provided ViBo API key (validated via HTTPS)
• No data leaves Dify other than the API key + tool parameters

The plugin only makes outbound HTTPS calls to https://wwwvibo.com
and returns text to the agent.

[crazywoola]

@crazywoola please see the errors in the CI checks above.

[vnbochkarev-netizen]

Hi @crazywoola! Could you approve the workflow run? It's stuck in action_required (waiting for approval) on every commit — this blocks the CI checks.

We've fixed the issues found earlier and verified everything locally on Python 3.12 (same as CI):

• dify_plugin installs cleanly (0.10.2) — requirements are compatible
• All validators pass: manifest, README, secrets, package contents, dependencies
• Plugin install test passes (serverless + Flask on :8080)
• Packaging test passes (dify-plugin-daemon 0.6.10, --test)

The plugin is ready for review. Thanks!

[crazywoola]

🤖 CI Summary

Check	Status
Pre Check Plugin	🟡 re-running — run log
PR Risk Label	✅ pass

What's wrong

Your earlier CI run was cancelled seconds after it started (it was a duplicate queued run that got superseded), so it never produced a result.

What I did

I've re-triggered the Pre Check Plugin run against the current head of your branch. Please check back in a few minutes — if it fails, the log will show the exact validation errors to fix.

Thank you! 🙏