I have to guess /hope that they did this already; who would make a time investment like this without first proving that the product has value? Anyway I certainly wouldn’t even pilot it without some proof.
You can study it all by graphing text extracts with NetworkX before you pay for an off-the-shelf LLM to provide a false sense of confidence.
The exercise will help you build the prompt regardless of what tech you use.
Additionally, incorporating agents and managing their workflows require a distinct set of metadata and separate workflows, which we are still in the process of exploring.
If you have an API to manage issues, that could work as well. Would need that anyway for custom build integration etc.
Otherwise, we have a public API to do CRUD operations for all important entities (issues, labels etc). We are working to get an openAPI spec once that is out we should have all the APIs added to our https://docs.tegon.ai
Edit: Never mind, found the list you posted elsewhere.
We are almost done working in 2 other areas 1. AI assistant while create a new issue ensuring the issue has enough information 2. Chat assistant to interact with the tool
Someone else's mystery machine is fine for a start, but if you want to train and test (and validate) your assumptions or do your own experiments, these AI features don't offer much.