Skip to content

Add agent and services architecture plan with dynamic tools registry#82

Draft
Copilot wants to merge 4 commits intomainfrom
copilot/create-agent-services-registry
Draft

Add agent and services architecture plan with dynamic tools registry#82
Copilot wants to merge 4 commits intomainfrom
copilot/create-agent-services-registry

Conversation

Copy link
Contributor

Copilot AI commented Feb 3, 2026

Problem

Outline a feasible architecture for agents that work across go-micro services, with service discovery, standardized protocols, and a monetization model.

Design

Two-Component Architecture

Agent Layer: Claude-based agent with dynamically generated tools registry. Tools are automatically built from service metadata rather than hardcoded—when a new service registers, it becomes immediately available as an agent capability.

Service Marketplace: Registry where developers publish go-micro services. Each service declares methods, schemas, and pricing. 70% revenue to developer, 30% to platform.

Protocol

  • Primary: gRPC for production (typed, efficient)
  • Fallback: HTTP JSON-RPC for easier onboarding
  • Discovery: Hybrid pull/push—initial poll, then subscribe to registry changes
  • Health: Periodic checks with circuit breakers for failing services

Example Flow

User: "What's the weather in London?"
  ↓
Agent queries tools registry → finds weather.GetForecast
  ↓
Calls service via gRPC → deducts 2 credits
  ↓
Returns formatted response → credits author 1.4p, platform 0.6p

Deliverables

Three planning documents under docs/:

  • AGENT_SERVICES_ARCHITECTURE.md (929 lines): Full technical spec with service registry schema, tools conversion logic, marketplace model, security considerations, 5-phase roadmap
  • AGENT_SERVICES_QUICKSTART.md (175 lines): Executive summary with example use cases
  • AGENT_SERVICES_CHECKLIST.md (434 lines): Phase-by-phase implementation tasks with 8-11 week timeline to MVP

Integrated into docs navigation under "Planning" category.

Open Questions

  • Service versioning strategy for breaking changes
  • Tool selection heuristics when multiple services offer similar capabilities
  • Service dependency chains and nested revenue splits
  • Approval flow (automatic vs manual review)

No implementation—pure design specification ready for stakeholder review.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI changed the title [WIP] Create agent framework for microservices integration Add agent and services architecture plan with dynamic tools registry Feb 3, 2026
Copilot AI requested a review from asim February 3, 2026 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants