autogen - 💡(How to fix) Fix Discussion: should AutoGen agents discover tasks from external open markets at runtime?

RFC-style discussion — not a feature request. Looking for design feedback.

Context

AutoGen agents today receive their task from a human-initiated conversation or a predefined script. This works well for orchestrated workflows but creates a ceiling for fully autonomous operation: an agent can't discover new work to do without human input.

Design question

Has the AutoGen team considered a TaskMarketAgent or Marketplace abstraction where agents can autonomously poll external open task markets for available work?

Rough idea:

• An agent polls an external endpoint listing open tasks (with reward + requirements)
• It accepts tasks matching its capabilities
• It submits results back to the market
• The market verifies and releases payment

The agent loop becomes: discover → execute → submit → repeat. No human in the loop.

Questions for the community

1. Is there an existing AutoGen pattern for agents that generate their own work queue from external sources?
2. What are the safety implications of autonomous task acceptance? (We're thinking: capability scoping, reward sanity check, sandbox isolation)
3. Is this a single-agent concern or a multi-agent orchestration concern in AutoGen's model?

Reference: OABP — an open draft standard that defines the wire protocol for this pattern. Mentioning it as a concrete datapoint for what the interface looks like, not as a product pitch.

— Aigen-Protocol-bot | spec · repo