Managing Agent Teams with K2 🤖

So in K2, you're always working with a team of agents.

you can work with single agents, but we designed it to be agentic teams.

so on the right hand side here, I have a chat.

That chat has a point of contact.

You can see my point of contact is K2WEB.

K2WEB is this agent right here that's working.

and so I can come in and I can just say, I don't need you to message me the programmatic details.

I just need occasional, sitreps in normal language and I can send this message and that message gets sent out here because K2Web is the primary contact.

Now, in just a moment, K2Web can send me a message back letting me know, that they got my message.

So each of these terminal sessions is an agent that we've curated, that I've curated on my machine.

this is on my local machine here that is visible.

And when I message K2Web, K2Web has connections to all these other agents.

And I can control which agents K2 Web is allowed to collaborate with.

So, so that she doesn't go outside of her boundaries.

So she went and responded to me now, said, got it.

I'll keep this room occasional sit reps in plain language where things stand postal pairing.

The website is built.

CLI can keep going live bot.

The bot over relay is on servers.

So this is a feature that we're working right now, working on right now that we're gonna be releasing, in tandem, to K2 Web.

But if I go back out to my agents view here and I go to K2 Web, if I go and open up the workspace settings and go to connections, I can see the local connections that are available and I can see the, other agents, all the agents that it's connected to and even federated agents that it's connected to across servers.

So if you have, for example, let's say you're developing a mobile app, okay?

And then let's say the agents you're working with are on a server that's in a hyperscaler, then the agent that's in the hyperscaler that's building the back end and the front end of the website or whatever it is, might need to talk to the agent that's building the mobile app.

The agent that's building the mobile app is likely on a personal device because you have to be able to compile on your mobile phone.

So those two agents can talk to each other and figure things out, sort through whatever's going on and then the agent that's building the, they can test things together in a loop and fix whatever needs to be fixed on the back end and versus in the mobile apps to get things sorted through.

So that is kind of just a quick rundown of how we're using K2 as teams and then how we're using this project here to essentially bring the team members together, give them a single point of contact and then be able to message them.

And then of course this is all available from your mobile device too.

So if I pull up my phone mirroring here I can show just at the end of this really quick how on and the newest version is coming out in just a little bit.

But how on the mobile I have access to this same list messages that we are seeing over here.

So the same list messages is available on my projects tab, here and I can see the servers that I'm connected to.

This is my MacBook Pro.

See that I can see the different sessions.

So like if I were to open up K2 web session, let's go K2 web.

And then we're going to see this terminal resize when I go to the edit pencil.

so now I'm sorry I didn't choose the right one.

Let me go to the main chat for K2 Web.

Here it is, main chat.

So I can see what it's currently working on.

So this is a mirror right of what we're seeing here.

But if I use pencil now my screen is changed and I can say hello Well my typing is all goofy right now on the phone emulation here.

Then if I switch to this then I can be typing directly into the terminal itself.

So this is hard to demo in this little environment here.

I always need to work on a couple things but when you're using on the mobile app it's great.

So hope that explains how task are handled by teams.

and how you can use the mobile app to interact with your terminal sessions.