hey, that's pretty cool. i found this problem myself when working in cursor or antigravity UI IDEs.

can you tell me more about how it discovers project interdependencies (ie a frontend repo needs a backend repo's api endpoints)?

ie you can't just open `claude`/`gemini`/`codex` in the parent folder and it will discover the project relationships themselves?

have you found an interesting way to make the agent "get better over time", ie maybe with any interesting findings the agent learns, it can write to `~/.modulus/MEMORY.md`

Happy to answer questions about how we built the memory/context engine or how we handle multi-repo dependency understanding.