Hi 
,
We noticed some of you understandably expect Argus to be an official Tuist product. It’s not, and we didn’t communicate that clearly. We’ve updated the README to reflect this. Use it at your own risk and expect rough edges.
So what is Argus? It started as an experiment exploring whether agents become more useful when you feed them structured build system data. Turns out they do. Since then, we’ve been playing with exporting different kinds of data and asking agents questions that platform teams typically have, like “should this target be static or dynamic?” The results have been promising.
What’s next? Over the coming weeks, we’ll figure out how to bring these ideas into Tuist proper. The shape is still TBD, but we’re leaning toward an integration where data isn’t just local to where it’s generated. Instead, it would be collected and stored in our infrastructure, then exposed through an interface that agents can query to understand builds across your project’s history and your team’s machines. This would likely become a Tuist feature, possibly an extension of our current insights, but more tightly integrated into your workflows and more powerful.
In the meantime: if you’re experimenting with Argus, I’d love to hear about your experience. I’m especially interested in questions you wish it could answer. That feedback helps us understand what data we need to collect and what capabilities to build.
