24 comments

  • anonyonoor 13 minutes ago
    What would be great too is a library for mini apps built with agents. I find these little apps to be useful all the time, but despite usually being written in very versatile HTML that is cross-platform, these things are confined to the specific platform I used and usually the chats too. I wish there was a provider agnostic way to build and view mini apps anywhere (desktop and mobile).
  • jrflo 11 minutes ago
    What is HN's policy on creating green accounts to inflate engagement on launch?
  • fg137 19 minutes ago
    Got really confused by the name. Apparently Google has a "Coral platform" which used to ship TPUs as USB devices (although that's discontinued, and Google barely markets the Coral brand these days). If you search "Coral AI" there are tons of products/companies called by that name, and this one is not nearly at the top. Maybe something to think about.
    • jcs 11 minutes ago
      That's fair - we like the metaphor a lot (hence the video on our website) but adding a suffix word may not be a bad idea
  • antonmry 34 minutes ago
    It's great how easy is to integrate Coral with my own workflow without having to make big changes to it. It makes a breed to add external services and manage agents permissions
  • nikolicmilena 49 minutes ago
    Cool - as we give agents more autonomy and write permissions, granular controls like this will be vital. Gonna get the team to test this.
    • jcs 4 minutes ago
      Would love to hear how you get on: james@withcoral.com.
  • ocamoglu 1 hour ago
    Better and granular controls as well as task specific memory for cost and time savings sounds amazing. Looking forawrd to trying this further.

    Looks like this is already used in real world by your customers. Any learnings you can share for deployment?

    • jcs 1 hour ago
      Thanks! A few things:

      - Starting locally with the desktop app helps is a great way to figure out Coral out before investing in the shared server deployment. The shared server needs you to bring your own IdP, among other things.

      - Don't design custom tools up front. Let agents discover what they need, but keep the human in the loop to review additions/updates.

      - Decide how you want your users to authenticate with the upstream provider (shared token vs. as themselves). Most prefer the latter when possible, and accept users will need to complete a one off OAuth flow for each provider. We're working on ID-JAG support to streamline this step.

      • ocamoglu 56 minutes ago
        Ok, thanks makes sense. User authorization was another question i had, you answered already.
  • wavemode 2 minutes ago
    vibecoded slop is bad enough, but creating a bunch of bot accounts to comment in this thread is outright malicious. flagged.
  • latissi 25 minutes ago
    Nice Works!
  • greenBottle 1 hour ago
    Looks good. We're evaluating it.
  • disrpt 1 hour ago
    Much love.
    • jcs 5 minutes ago
      Thank you
  • jurgenaut23 1 hour ago
    Will give it a go!
    • jcs 5 minutes ago
      Great - shoot me a mail with any questions or feedback: james@withcoral.com
  • algsoch 42 minutes ago
    [flagged]
  • hitakshiA 1 hour ago
    [flagged]
  • akshmnd 1 hour ago
    [flagged]