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).
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.
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
- 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.
Looks like this is already used in real world by your customers. Any learnings you can share for deployment?
- 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.