RFC: Audit CLI agent attachment in interactive and query modes

[evansenter]

Summary

Audit how agents are registered and attached to the CLI in both interactive and query modes, ensuring the architecture is clean and extensible.

Motivation

The CLI currently has multiple ways to invoke agents:

• Query mode: gemicro --agent <name> "query"
• Interactive mode: agent selection during session

Questions to answer:

1. How are agents discovered and registered?
2. Is the agent registry the right abstraction?
3. Can third-party agents be added without modifying the CLI?
4. Is there unnecessary coupling between the CLI and specific agents?

Scope

1. Document current flow

   • How --agent flag resolves to an Agent impl
   • How interactive mode presents agent options
   • Where agent registration happens

2. Evaluate extensibility

   • Can agents be added via plugins/extensions?
   • Does the CLI need to know about all agents at compile time?
   • How would external agents be integrated?

3. Identify improvements

   • Registry patterns that could help
   • Plugin architectures to consider
   • Configuration-driven agent loading

4. Consider user experience

   • Agent discovery and help text
   • Validation and error messages
   • Tab completion potential

Related

• Issue Migrate DeveloperAgent to use LlmClient instead of raw client() #238 (DeveloperAgent migration)
• Eval agent loading concerns (separate RFC)