langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #1607] [MERGED] Add A2A Client plugin v0.1.0 #1723

New Issue
Closed
opened 2026-02-22 18:06:09 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:06:09 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1607
Author: @flyryan
Created: 11/24/2025
Status: ✅ Merged
Merged: 2/3/2026
Merged by: @crazywoola

Base: main ← Head: add-a2a-client-plugin

📝 Commits (1)

  • 4d2caf8 Add A2A Client plugin v0.1.0

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ ryan_duff/dify-a2a-plugin/dify-a2a-plugin-0.1.0.difypkg (+0 -0)

📄 Description

Plugin Information

Submission Type

  • New Plugin
  • Update to Existing Plugin

Description

First implementation of the Agent-to-Agent (A2A) protocol for Dify, enabling cross-platform agent collaboration and task delegation. This plugin provides 5 tools for both synchronous and asynchronous communication with external A2A-compliant agents.

Why this plugin is needed:

  • Implements open A2A Protocol v0.3.0 standard for agent-to-agent collaboration
  • Complements Dify's existing MCP support (which focuses on tool/data access) by enabling agent delegation
  • Allows Dify agents to delegate specialized tasks to domain-expert agents on any A2A-compatible platform
  • Supports both sync (message/send) and async (message/stream + tasks/get) communication patterns
  • Provides universal agent-to-agent connectivity using JSON-RPC 2.0 standard

Key features:

  • 5 comprehensive tools: list agents, get capabilities, call agent (sync), submit task (async), get task status
  • Multiple authentication methods: Bearer, API Key, Basic Auth, None
  • Secure credential storage via Dify's secret-input
  • Full bilingual support (English + Chinese)
  • Comprehensive error handling and 60s+ timeout support

Compliance Checklist

Documentation Standards

  • My README contains setup instructions
  • My README contains usage details
  • My README contains required APIs and credentials information
  • My README contains connection requirements
  • My README contains a link to the source repository

Privacy Requirements

  • Does your plugin collect personal data? YES
    • Data collected: Agent API credentials (API keys, tokens), agent base URLs, agent names, agent descriptions
    • Purpose: To authenticate with and route requests to remote A2A-compatible agents
    • Storage: Securely stored in Dify's encrypted credential system
    • Third-party sharing: User instructions/messages sent to explicitly configured external agent endpoints only
  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

Additional Information

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/1607 **Author:** [@flyryan](https://github.com/flyryan) **Created:** 11/24/2025 **Status:** ✅ Merged **Merged:** 2/3/2026 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `add-a2a-client-plugin` --- ### 📝 Commits (1) - [`4d2caf8`](https://github.com/langgenius/dify-plugins/commit/4d2caf8997b979795f3f20a5dd03cb91ab8b84ec) Add A2A Client plugin v0.1.0 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `ryan_duff/dify-a2a-plugin/dify-a2a-plugin-0.1.0.difypkg` (+0 -0) </details> ### 📄 Description ## Plugin Information - **Plugin Author**: ryan_duff - **Plugin Title**: A2A Client - **Repository URL**: https://github.com/flyryan/dify-a2a-plugin ## Submission Type - [x] New Plugin - [ ] Update to Existing Plugin ## Description First implementation of the Agent-to-Agent (A2A) protocol for Dify, enabling cross-platform agent collaboration and task delegation. This plugin provides 5 tools for both synchronous and asynchronous communication with external A2A-compliant agents. **Why this plugin is needed:** - Implements open A2A Protocol v0.3.0 standard for agent-to-agent collaboration - Complements Dify's existing MCP support (which focuses on tool/data access) by enabling agent delegation - Allows Dify agents to delegate specialized tasks to domain-expert agents on any A2A-compatible platform - Supports both sync (message/send) and async (message/stream + tasks/get) communication patterns - Provides universal agent-to-agent connectivity using JSON-RPC 2.0 standard **Key features:** - 5 comprehensive tools: list agents, get capabilities, call agent (sync), submit task (async), get task status - Multiple authentication methods: Bearer, API Key, Basic Auth, None - Secure credential storage via Dify's secret-input - Full bilingual support (English + Chinese) - Comprehensive error handling and 60s+ timeout support ## Compliance Checklist - [x] I have reviewed the [Dify Marketplace Publication Guidelines](https://docs.dify.ai/plugin-dev-en/0312-contributor-covenant-code-of-conduct) - [x] I have accepted the [Plugin Developer Agreement](https://docs.dify.ai/plugin-dev-en/0312-contributor-covenant-code-of-conduct) - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud - [x] I have completed testing of my plugin ## Documentation Standards - [x] My README contains setup instructions - [x] My README contains usage details - [x] My README contains required APIs and credentials information - [x] My README contains connection requirements - [x] My README contains a link to the source repository ## Privacy Requirements - [x] Does your plugin collect personal data? **YES** - **Data collected**: Agent API credentials (API keys, tokens), agent base URLs, agent names, agent descriptions - **Purpose**: To authenticate with and route requests to remote A2A-compatible agents - **Storage**: Securely stored in Dify's encrypted credential system - **Third-party sharing**: User instructions/messages sent to explicitly configured external agent endpoints only - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the [Plugin Privacy Protection Guidelines](https://docs.dify.ai/plugin-dev-en/0312-privacy-protection-guidelines) - Privacy policy URL: https://github.com/flyryan/dify-a2a-plugin/blob/main/PRIVACY.md ## Additional Information - **Testing**: Unit tests included with mocked dependencies - **Production readiness**: Plugin has been tested in local Dify Community Edition deployment - **Support**: GitHub Issues (https://github.com/flyryan/dify-a2a-plugin/issues) + Email (ry@nduff.com) - **License**: Apache License 2.0 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:06:09 -05:00
yindo closed this issue 2026-02-22 18:06:14 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1723
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?