14 pointsby adinagoerres10 hours ago5 comments
  • isabelleilyia3 hours ago
    After being a Superglue customer for 6 months now, I think their future is massive.

    Building b2b saas nowadays requires products to be entirely open in terms of configuration and connection to people's greater systems, especially comparing with tools like Claude for specific verticals.

    I had initially plugged in Superglue's CLI for the use case above - creating Salesforce opps. Since then, I've gotten the following behavior relatively out of the box (sometimes it just works live on call with a customer): 1. Searching Hubspot deals by some specific criteria 2. Copying and editing a slide deck

    The development process with Superglue first went from hours building brittle code -> minutes building a tool. Now it's gone from that to simply an extra SKILL file as soon as we notice a trend in what customers are asking it to do.

    Awesome team and awesome product. So lucky to be working with them :)

  • adinagoerres10 hours ago
    Adina here, one of superglue's creators. I'm curious to hear folks opinions on this. Also to clarify how agents are able to call APIs via superglue: the first step is to set up auth and systems on superglue so it can process and extract documentation and any other context for calling the APIs, which is then passed on to the agents
  • heushreck9 hours ago
    Feels like you’ve basically turned the “tooling bottleneck” into a prompt + policy problem, which is way more scalable but shifts the real challenge to constraint design and observability.
    • adinagoerres9 hours ago
      Yes, we've seen this work best with clear instructions around Salesforce, Attio etc. superglue does come with a number of observability and monitoring features, but of course this can be extended for a specific setup.
  • fiehtle2 hours ago
    integrations are the bottleneck, cli is the new ui
  • hoerzu6 hours ago
    What's the mcp?