luigidemasi opened a new issue, #65:
URL: https://github.com/apache/camel-kit/issues/65

   > Imported from 
[luigidemasi/camel-kit#109](https://github.com/luigidemasi/camel-kit/issues/109),
 opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-25.
   > Closed by 
[luigidemasi/camel-kit#114](https://github.com/luigidemasi/camel-kit/pull/114), 
merged on 2026-06-26.
   
   ---
   
   ## Description
   
   `AgentRegistry` currently hardcodes supported agent metadata in Java. This 
is workable for the current set of agents, but Camel-Kit's architecture depends 
on multi-agent parity, and agent-specific behavior already spans Java code, 
templates, MCP config paths, command formats, dispatch templates, and trait 
files.
   
   Relevant files:
   - 
`camel-kit-core/src/main/java/io/github/luigidemasi/camelkit/config/AgentRegistry.java`
   - 
`camel-kit-core/src/main/java/io/github/luigidemasi/camelkit/config/AgentConfig.java`
   - 
`camel-kit-core/src/main/java/io/github/luigidemasi/camelkit/generator/AgentGeneratorFactory.java`
   - `camel-kit-core/src/main/resources/templates/`
   - `camel-kit-core/src/main/resources/templates/mcp-configs/`
   
   ## Expected Behavior
   
   Agent capabilities should be described in resource files and loaded by the 
registry.
   
   A descriptor should include:
   
   - agent id
   - display name
   - command directory
   - command file format
   - argument placeholder
   - MCP config path
   - MCP server container key
   - description
   - generator strategy or capabilities
   - dispatch template path
   - settings/templates to install
   - whether the agent supports subagents or traits
   
   ## Additional Context
   
   A possible format is YAML or JSON under:
   
   `camel-kit-core/src/main/resources/agents/registry/`
   
   This would let agent support evolve through data and templates instead of 
requiring Java edits for every metadata change.
   
   The first implementation can load descriptors into the existing 
`AgentConfig` model to minimize blast radius.
   
   ## Acceptance Criteria
   
   - Built-in agents are loaded from resource descriptors instead of a 
hardcoded `Map`.
   - Existing public `AgentRegistry` methods keep working.
   - Agent generator tests pass for all supported agents.
   - Missing or malformed agent descriptors fail with clear validation errors.
   - Documentation is updated to describe where agent capabilities are 
configured.
   
   ## Validation
   
   Run:
   
   `./mvnw -pl camel-kit-core -Dtest='AgentGeneratorFactoryTest,*GeneratorTest' 
test -Dformat.skip=true`
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to