Clip
Summary
The team is building toward a single app that serves two personas — Access staff building and distributing agents, and customers building on their own data. Right now there are three tools and three names, and that's three too many. No full demo today, but the team showed the direction: org ID targeting for agents is in, third-party data connectors are now registerable via the UI (not just dev workflow), and GraphQL connectors now use an MCP wrapper. A full end-to-end demo is coming next week.
Screenshots
Transcript
Ohh. Thanks, Elliot. I'll call you sharing the slides as well.
That's great. So I'm just going to provide an update of what we've been working on this week. We won't demo it.
I'll give a bit of an intro after as to why that is as well as a look ahead to next week. So yeah, this week we've been working on organisation ID targeting of agents. And so this is to support our EAP programmes that we have at the moment.
Currently, some of the feedback that we've had is that agents aren't made for certain organisations are kind of being targeted. So this will allow our softcos to better target the agents that they create to specific organisations. Again, this is probably more of a stop gap.
I think we need to look at more dynamic ways of targeting in the future, but meets the immediate need of the EAPs. We've also been working on exposing off third party data connectors to the connectors application to support our internal beta. I think we're kind of almost there on that one.
In the last couple of reviews, we've shown how you can register an internal access application data connector with the connectors application. And that's generally been via a kind of development process. So we've now made that available via the UI as well for a better experience.
Skills, I mean, that's something that we've kind of been working on that unfortunately didn't demo well there as well. But again, we want to be able to, when configuring the Access application data connectors, that you can also kind of create a skill description for that API as well. So skills really are like a step-by-step guide of how to interact with the API for specific tasks that deliver very, I guess, deterministic or as close to deterministic as can be, a set of steps for an AI experience.
And then we've also, when adding a GraphQL connector, implemented an MCP wrapper so that we kind of have an MCP pattern when connectors are interacting with agents that are built as well. And the reason why we haven't done a demo today, I'll just give a bit of an intro into next week and into where we're working towards as well, which is if we were to kind of demo at the moment, be probably making some changes across many different applications. So today we have agent builder, co-work creator, and connectors.
And that's three tools, three names, and we need to facilitate one simple conversation with our customers. And that's three too many points of confusion. So our big focus for next week is a demo as well. is to kind of really wrap up the end-to-end flow and set the core foundations for wider adoption and GA of Agent Builder internally, but also with our customers, and essentially move that kind of three tools, three names to, you know, Two personas that we need to serve, us internally as access, either P& E or professional services that are building agents and distributing those to our customers, as well as our customers building agents on top of our data and their data as well.
But consolidating those two personas, within one app and creating 0 confusion at the end of it. So yeah, that's our big kind of goal for next week as we reach that. And again, we'll wrap up all the changes that we've made this week with a full end-to-end demo of how that all fits together as well.
So yeah, any questions, let me know. But if not, I will hand over to Workflow, is that John today?