OpenFang

Ecosystem

Channels, MCP, A2A, OFP, Desktop

Overview
What It Is
Core Concepts
Architecture
Security (16 Layers)
Hands
Ecosystem
Getting Started
Benchmarks
Whitepaper
Sources

Ecosystem & Integrations

40 Channel Adapters

The architecture document lists 40 adapters and emphasizes that:

  • Each adapter implements the ChannelAdapter trait.
  • It utilizes ChannelOverrides for per-channel configuration of model/system prompt/DM policy/group policy/rate limit/output format.
  • A formatter is responsible for converting Markdown to the format specific to the platform (e.g., Telegram HTML / Slack mrkdwn, etc.).

(The complete list can be found in the Channel System section of the docs/architecture.)

Tools + MCP

Both the official website and architecture documentation highlight:

  • A batch of built-in native tools.
  • Support for Model Context Protocol (MCP):
    • MCP Client: Connects to external MCP servers.
    • MCP Server: Exposes OpenFang's tools externally.
    • Tool naming incorporates namespaces (mcp_{server}_{tool}) to prevent collisions.

A2A (Agent-to-Agent)

The architecture document mentions that OpenFang implements Google's A2A protocol:

  • Publishes AgentCard (/.well-known/agent.json).
  • Supports the task lifecycle (send/get/cancel).

OFP (OpenFang Protocol, P2P Network)

OFP is OpenFang's peer-to-peer communication protocol:

  • JSON-framed message over TCP.
  • HMAC-SHA256 mutual auth (nonce + constant-time verify).
  • Peer registry to maintain the list of remote agents.
  • Integrates with the capability system: Requires OfpDiscover/OfpConnect/OfpAdvertise permissions, etc.

Desktop App (Tauri 2.0)

Architecture description: The desktop app boots the kernel within the same process, starts a local axum server, and then uses a WebView to open the dashboard. It provides capabilities like a system tray, notifications, single-instance enforcement, and more.