✨ [New]: Invictus Agent implementation #402
Description
Category
No response
Description
After doing a quick ChatBot POC in CoPilot Studio, we should now create a "full" and production-ready version of an Invictus Agent.
Scope
- The initial scope will be to expose the Invictus documentation to the user, and allow them to search through natural language. This includes, but is not limited to, Github documentation, Release Notes, Roadmap, ...
-
IDEA: Allow the Agent to tell the user about recent errors and give them more (and clearer) information on what happened (=> possibility to link to the work that was done to use AI to further enhance the error messages)
-
IDEA: Further down the road, we should consider allowing the Agent to perform actions for the user, such as Resume, Resubmit, Ignore...
Archtecture considerations
- PAAS vs SAAS: Since the scope is going to grow beyond simple documentation exposure, it's probably a good idea to create this as a PAAS application, so that - like the rest of Invictus - it lives on the tenant of the client itself.
- IDEA: Can we use Context7 to link the Agent with the Github documentation?
- IDEA: Can we use APIM to expose an MCP server to the agent (still only in Preview though)
Additional context
No response