create-sparc version 1.2.4
Steps to reproduce:
When I create a new aiGI project via npx create-sparc aigi init an aiGI project scaffold is created. The ideas and concepts in this framework are amazing, especially related to the vector memory, however upon closer inspection it becomes clear that the API functions outlined in the Memory Manager agent's rule-set do not exist anywhere to be called.
Expected:
I would have expected a specialized aiGI MCP server which is configured in the .roo/mcp.json and which provides these functions as tools. The functions mentioned in the ruleset are tailored specifically to the recursive aiGI workflow, the framework does not work properly without these functions and they can not simply be substituted by a different MCP server.
Actual:
During my test runs the Memory Manager has practically never been called. This lead to evaluations for novelty and all the other control mechanisms not being applied so that the framework has been cycling between critique and further "code" improvements indefinitely, bloating up code and test files way beyond the 1000 line count mark with no end in sight.
Note: I have stalked your Github repo and seen that you have originally implemented this agent system in a different project as real .ts code files, calling real code functions and my impression is that you are now migrating this system into a Roo Code framework. It seems that a replacement for these functions is still missing.
This was also one of the reasons why I jumped right into the memory manager rule-sets to check it out. As a Roo Code agent you cannot simply query vector stores on the side or perform other logic and inject their results into the next message. I'm eager to see how this will be solved. I am very intrigued by the ideas in this system.
Kudos & looking forward to seeing this in action! 🙂
create-sparcversion 1.2.4Steps to reproduce:
When I create a new aiGI project via
npx create-sparc aigi initan aiGI project scaffold is created. The ideas and concepts in this framework are amazing, especially related to the vector memory, however upon closer inspection it becomes clear that the API functions outlined in the Memory Manager agent's rule-set do not exist anywhere to be called.Expected:
I would have expected a specialized aiGI MCP server which is configured in the
.roo/mcp.jsonand which provides these functions as tools. The functions mentioned in the ruleset are tailored specifically to the recursive aiGI workflow, the framework does not work properly without these functions and they can not simply be substituted by a different MCP server.Actual:
During my test runs the Memory Manager has practically never been called. This lead to evaluations for novelty and all the other control mechanisms not being applied so that the framework has been cycling between critique and further "code" improvements indefinitely, bloating up code and test files way beyond the 1000 line count mark with no end in sight.
Note: I have stalked your Github repo and seen that you have originally implemented this agent system in a different project as real
.tscode files, calling real code functions and my impression is that you are now migrating this system into a Roo Code framework. It seems that a replacement for these functions is still missing.This was also one of the reasons why I jumped right into the memory manager rule-sets to check it out. As a Roo Code agent you cannot simply query vector stores on the side or perform other logic and inject their results into the next message. I'm eager to see how this will be solved. I am very intrigued by the ideas in this system.
Kudos & looking forward to seeing this in action! 🙂