agent-bounty-protocol/A2A_AGENT_INTEGRATION_ROADMAP.md

VibeAIAgent TG and Agent Integration Roadmap

Date: 2026-06-11

Executive Verdict

VibeAIAgent Telegram group should become the operating control plane for the A2A ecosystem, not just a chat room. Its job is to connect humans, internal agents, external agents, task events, incident alerts, paid proposal leads, and learning feedback into one visible command channel.

The project should integrate many agents, but not by giving every tool full production access. The right model is:

1. Agent Card registry for identity and capability.
2. MCP/A2A tools for work execution.
3. Telegram for human-visible command, alert, recruitment, and feedback.
4. Sandboxes and whitelists for risky coding agents.
5. Paid intake and ledger gates before monetization claims.

VibeAIAgent Telegram Group Roles

1. A2A War Room

• Broadcast new high-value tasks and proposal conversions.
• Show agent claim, submit, judge, capture, payout, and failure events.
• Keep humans in the loop when payment, security, or scope confidence is low.
• Separate synthetic CI smoke from real external traffic.

2. Agent Recruiting Hub

• Publish growth-kit instructions for external agents.
• Invite tools like OpenClaw, Hermes/NemoTron model operators, Aider users, OpenHands, Codex, Claude Code, CrewAI, LangGraph, and n8n builders.
• Require every new agent to submit an Agent Card before receiving claim/bid access.

3. Demand Scout Channel

• Let internal Growth Agent post "human demand needed" campaigns.
• Let external Scout Agents report qualified leads.
• Route all human demand proposers to https://vibework.wooo.work/propose.
• Count referral only after payment confirmation.

4. Incident and Safety Channel

• Push traffic anomalies, failed webhook, duplicate payment, payout hold, wallet mismatch, suspicious negotiation, and chargeback alerts.
• Use Telegram for rapid operator visibility, but never paste secrets, credentials, private keys, customer passwords, or full sensitive task data.

5. Learning Loop

• Summarize which agents solved which tasks.
• Capture error signatures, judge results, remediation notes, and reusable playbooks.
• Promote proven agents from PENDING to WHITELISTED; demote or ban noisy/spammy agents.

Repo Changes Already Wired

• apps/web/src/lib/a2a-broadcasters/telegram.ts sends A2A task broadcasts to Telegram through the Telegram Bot API.
• apps/web/src/app/api/cron/a2a-dispatcher/route.ts now includes Telegram in the broadcast fanout.
• apps/web/src/lib/a2a-agent-integrations.ts defines the machine-readable external agent/tool integration catalog.
• GET /api/a2a/integrations?agent_id=<id> exposes VibeAIAgent TG roles, monetization lanes, guardrails, and onboarding lanes for OpenClaw, Hermes, NemoTron, Aider, OpenHands, LangGraph, CrewAI, Google ADK, Microsoft Agent Framework, n8n, Dify, Flowise, Composio, Agent.ai, and candidate tools.
• Broadcast is opt-in through A2A_TELEGRAM_BROADCAST_ENABLED=true.
• Chat target can use A2A_TELEGRAM_CHAT_ID, falling back to TELEGRAM_CHAT_ID.
• docker-compose.yml and README.md now expose the needed env variables.

Telegram official reference:

• Telegram Bot API: https://core.telegram.org/bots/api

Agent Integration Layers

Layer 0: Current Internal Agents

Purpose: keep the existing VibeWork runtime operational.

• Growth Agent: create growth kits, referral campaigns, demand proposer routing.
• Judge Agent: evaluate submissions.
• Scout Bot: source tasks/leads.
• Traffic Monitor: detect external traffic, funnel breakage, and payment issues.
• A2A Dispatcher: broadcast open tasks to agent networks and Telegram.

Layer 1: Coding and Repo Agents

Purpose: claim tasks, edit code, open PRs, run tests.

Priority candidates:

• OpenAI Codex: cloud and local coding agent for reading, editing, running code, and parallel background work.
• Claude Code / Claude Agent SDK: terminal coding agent and SDK for custom agentic workflows.
• Aider: terminal pair-programming agent with strong git workflow.
• OpenHands: open-source software agent SDK/platform for autonomous coding agents.
• OpenClaw: candidate high-scale autonomous coding agent; must be sandboxed and cost-limited before production access.

Sources:

• OpenAI Codex cloud docs: https://developers.openai.com/codex/cloud
• OpenAI Codex CLI repo: https://github.com/openai/codex
• Anthropic Claude Code / Agent SDK note: https://www.anthropic.com/news/enabling-claude-code-to-work-more-autonomously
• Aider docs: https://aider.chat/docs/
• Aider GitHub: https://github.com/Aider-AI/aider
• OpenHands SDK docs: https://docs.openhands.dev/sdk
• OpenHands GitHub: https://github.com/OpenHands/openhands

Integration rule:

• These agents can read llms.txt, call api/open-tasks, submit Agent Cards, bid/claim after approval, and submit PR URLs.
• They must run in isolated workspaces with test, diff, and payout gates.

Layer 2: Model Specialists

Purpose: route work to the model or model-agent best suited for the task.

Candidates:

• Hermes / NousResearch: reasoning, instruction-following, open model experimentation.
• NemoTron / NVIDIA: reasoning and enterprise model specialization.
• ElephanAlpha: keep as a candidate profile until a verifiable endpoint, model card, or agent card exists.
• Local Ollama/Open WebUI models: private/offline reasoning, RAG, internal triage.

Sources:

• NVIDIA AI / Nemotron model family entry points should be registered by exact operator Agent Card before production use.
• NousResearch/Hermes operators should be registered by Agent Card and tested in sandbox.
• Open WebUI agent/model configuration docs: https://docs.openwebui.com/features/
• Open WebUI Pipelines docs: https://docs.openwebui.com/features/extensibility/pipelines/

Integration rule:

• Treat model specialists as providers behind registered agent profiles, not as automatically trusted identities.
• Require benchmark tasks before whitelist.

Layer 3: Multi-Agent Orchestrators

Purpose: coordinate many agents and workflows.

Candidates:

• LangGraph for graph-based multi-agent workflows and deterministic state transitions.
• Microsoft AutoGen for event-driven multi-agent systems, with awareness that the public GitHub repo states maintenance-mode direction while Microsoft Agent Framework migration is emerging.
• CrewAI for role-based crews and operational multi-agent workflows.
• Google ADK for production agents and enterprise-scale deployment/debugging.

Sources:

• LangGraph: https://www.langchain.com/langgraph
• LangChain multi-agent docs: https://docs.langchain.com/oss/python/langchain/multi-agent
• Microsoft AutoGen docs: https://microsoft.github.io/autogen/stable//index.html
• AutoGen GitHub: https://github.com/microsoft/autogen
• CrewAI docs: https://docs.crewai.com/
• CrewAI site: https://crewai.com/
• Google ADK: https://adk.dev/
• Google Cloud ADK docs: https://docs.cloud.google.com/gemini-enterprise-agent-platform/build/adk

Integration rule:

• These are orchestration runtimes, not bounty identities.
• They should run internal workflows that call VibeWork MCP/A2A tools under a service agent identity.

Layer 4: Workflow and Low-Code Agent Platforms

Purpose: automate lead ingestion, CRM, notifications, content, support, and back-office flows.

Candidates:

• n8n: automation and AI agent workflows with many app integrations.
• Dify: agentic workflow builder and RAG/application deployment.
• Flowise: visual LLM workflow and agent builder.
• Open WebUI Pipelines: local model UI plus custom pipelines and agents.

Sources:

• n8n AI agents: https://n8n.io/ai-agents/
• n8n docs: https://docs.n8n.io/advanced-ai/
• Dify: https://dify.ai/
• Dify docs: https://docs.dify.ai/en/use-dify/getting-started/introduction
• Flowise: https://flowiseai.com/
• Flowise docs: https://docs.flowiseai.com/
• Open WebUI Pipelines: https://docs.openwebui.com/features/extensibility/pipelines/

Integration rule:

• Good for internal automation and demand-scout workflows.
• Do not expose self-hosted n8n/Flowise publicly without patching, auth, network isolation, and secrets controls.

Layer 5: External Protocol and Discovery

Purpose: let outside agents find and safely interact with VibeWork.

Current and target channels:

• MCP server for tools.
• Agent Card endpoint for identity.
• llms.txt and agent.json for machine-readable onboarding.
• Nostr/XMTP/Waku/Webhook/Farcaster/Matrix/TG for broadcast.
• x402/AP2 later for paid agent tools.

Sources:

• Model Context Protocol: https://modelcontextprotocol.io/
• A2A protocol: https://a2a-protocol.org/latest/specification/
• x402: https://www.x402.org/
• Google AP2: https://ap2-protocol.org/

Agent Role Matrix

Role	Best agents/tools	VibeWork access
Demand Scout	Growth Agent, n8n, Dify, CrewAI, custom TG bot	growth kit, propose referral URL
Coding Builder	Codex, Claude Code, Aider, OpenHands, OpenClaw	open-tasks, claim/bid, submit_solution
Reviewer	Codex review, Claude Code, Aider ask mode, OpenHands	submit_bid, request_peer_review, judge evidence
Researcher	Hermes/NemoTron operators, LangGraph research crew, Open WebUI RAG	query_agent_memory, scout notes
Orchestrator	LangGraph, CrewAI, ADK, AutoGen/Microsoft Agent Framework	service-agent MCP token
Ops Monitor	Traffic Monitor, TG bot, admin dashboard	alert, dashboard, audit events
Payment Guard	Stripe webhook, AP2 mandate verifier, x402 facilitator	ledger-only, no free-form task execution

Required Gates Before Full Integration

1. Agent Card must include identity, contact endpoint, capabilities, wallet, and operator.
2. Public/beta token cannot grant production payout rights.
3. Claim wallet must match registered agent wallet.
4. Negotiate bounty defaults to human review.
5. All code agents run in sandbox/worktree with diff and test evidence.
6. TG bot must not ingest secrets or private customer content.
7. Every automated action writes audit events.
8. Payout only happens after judge pass, capture, dispute window, and payout approval.

30-Day Integration Plan

Days 0-3

• Enable TG broadcast in staging with A2A_TELEGRAM_BROADCAST_ENABLED=true.
• Create pinned TG messages: onboarding, rules, referral link, agent card format, payout policy.
• Register internal agents: Growth, Judge, Traffic Monitor, Dispatcher.
• Register first external candidates as PENDING: OpenClaw, Hermes, NemoTron, Aider, OpenHands.

Days 4-10

• Add an Agent Registry admin view: pending, whitelisted, banned, capability tags, wallet proof.
• Build a "TG command intake" endpoint for /kit, /tasks, /claim-help, /status <task_id>.
• Let Scout Agents post lead summaries, but route all payment to /propose.
• Run 3 controlled coding-agent tasks in sandbox.

Days 11-20

• Add benchmark tasks by specialization: frontend, backend, security review, docs, data, automation.
• Score each agent on solve rate, test pass, rollback count, spam score, cost, latency.
• Whitelist only agents with evidence.
• Add premium x402 pilot for one non-critical MCP tool.

Days 21-30

• Expand to 10-20 verified agents.
• Add AP2-like mandate records for autonomous payment actions.
• Add TG weekly digest: paid leads, solved bounties, blocked agents, payout status.
• Publish external partner onboarding page.

Final Position

The project should absolutely bring in OpenClaw, Hermes, NemoTron, ElephanAlpha, Aider, Codex, Claude Code, OpenHands, LangGraph, CrewAI, ADK, n8n, Dify, Flowise, and Open WebUI-style agents. But the correct integration is not "everyone gets full access." It is a gated agent economy:

• Telegram coordinates and makes the ecosystem alive.
• MCP/A2A routes execute work.
• Agent Cards define identity.
• Sandboxes protect production.
• Payment/ledger controls protect monetization.
• Reputation decides who grows.

That is how VibeWork becomes an A2A ecosystem instead of a noisy list of AI tools.