Persistent named bots beat disposable chat sessions

Transcript

Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.

1. 6:24

   use the code peter to sign up and get three months free that's granola.ai slash peter now back to our episode you also have a channel like meow app or something where you have a bunch of bots talking to each other yeah so once once you have bigger tasks that um you want to different bots with different roles have their own perspective and contribute to it yeah this is an example like if let's say we are building an app that can translate cast mail to english and i want to start review this idea from different perspectives so i will have my um pm design edge like three individual bots added them into a single group chat and i will throw this prompt and then they'll start to discuss and ideate about this thing and it's interesting to see like how they think about the idea how they debate with each other um if you want a specific bot to reply to you just simply

2. 7:25

   at mention it, and only that bot would reply to you. If you just send a message in a group chat, just like how you message your friends in group chat, they will review it, and then they will reply, they will decide if they should reply from their own end goal. I don't think this is easy to do in some of the other AI apps, right? Because keeping the context clean and having all these bots that have their own context chat with each other is pretty unique.

3. 7:50

   There's two angles you can think about the problem. Some people manage their tasks and jobs by individual sessions. asking projects and we are creating bots as more persistent named agents that have their own identity, memory system, have their own tools. It's really like abstract what's reusable into the role and then you can have them work together by creating separate chats and group chats for them. Like even I have multiple projects with the same designer bot, I can create another chat with it like for a different project right and then i can do this repeatedly for different projects i'm managing because one thing we notice is a lot of time uh in the ai agent products those chat are very ephemeral they're almost disposable like you don't care like maybe you only care like top three to five that you're actively working on and then for the chats like you happen two weeks ago like

4. 8:52

   you never go back. So I think this is a great way to like balance the two, that for whatever reusable, the capability, the memory, then you kind of abstract them into different rows. And then for individual projects that has the end, has the deadline, and then you can create this dedicated sessions and work with our bots in it. And, but, but just like a human, the designer bot, like if I talk to designer bot for mail app and bark app, it knows about both right in its context yes or is it separate yes so when a bot is working in a group chat you will able to see