@ricardo_luz great questions! We've been working with other SaaS companies like Attentive, Sourcegraph, AssemblyAI, Willow, and Bento, who have tried using it in a variety of contexts. The main thing in common is that these teams all have substantial existing applications and codebases. What sets it apart from other visual programming environments? Rivet is built to integrate with existing applications. More specifically that means: - Remote Debugger. You can connect the Rivet UI to an app running locally or on a staging instance, and actually have it execute in that environment. Super great for iterating within your application, and you can even "hot reload" your agent graph. - External Calls. You can dynamically define functions that your agent can call in the context of your application. This is especially great if you have access control concerns, because you can dynamically define the calls your agent can make, rather than give them unfettered access to an API. - Collaboration via YAML Project Files. Rivet saves agent graphs to a YAML format. At Ironclad, we version these agent graphs with the rest of our git repo. We now regularly do code reviews on changes to prompts or agent graphs! We literally could not have launched Ironclad Contract AI (https://ironcladapp.com/product/...) without Rivet. Thanks for your support!

Thanks @tarunpaliwal!

@swimburger thank you for your collaboration and contributions!!

@vivek_nair thanks! Actually, when running locally, you can open it in a web app. There's one catch, though: saving project files is pretty janky (it downloads the project file). I think basically everything else works pretty well, though!

Thanks @damndan! ICP is probably early to growth-stage start-ups! That's at least what a lot of our early design partners and collaborators have been. Rivet slots in neatly to most modern TypeScript applications, and is pretty easy to adopt progressively. (Also depends on your definition... I'd consider Ironclad a "growth-stage start-up," but I imagine others would say otherwise!)

Thanks @justin_kwok4!

@walden_yan1 thank you! And great questions! We're far from done with Rivet! As we continue to work on Ironclad Contract AI, we will continue to add to Rivet's capabilities. AND we JUST added the plug-in system, which our friends at AssemblyAI have already been able to use to integrate their audio transcription and understanding AI models into Rivet! Tons of potential there. Re: long prompts - Rivet doesn't do much to protect you from this automatically. However, for Ironclad Contract AI, we make use of things like the "chunk" node to split up large bits of text, and the Vector DB nodes for recalling relevant context. So we think there's enough to get by here, but there is certainly room for more. Re: integrated evaluation flow - Rivet has "testing" utilities, but they're much more like "unit tests" than evals. While I could see this becoming "native" to Rivet, I actually think the plug-in system opens up the possibility of integrating Rivet with emerging solutions around evals!

@heleana thank you!!

@doug_safreno1 thanks! At Ironclad, we have been using Rivet to build an agent in a chat interface. But we've already seen other companies doing very different things. Our friends at Bento (also on PH today!) created an awesome way to build new contextual on-boarding guides based on things like help center articles and just clicking around in an app.

Thanks @deezium!

@klaudia_bumgarner thanks!