# Jack Dorsey's Buzz: Clearly Explained (and how to use it) Greg Isenberg · 2026-07-28 Greg Isenberg and Vinny explore Buzz, an open-source agent-native chat app from Block (Jack Dorsey's company) that treats AI agents as first-class team members in a Slack-like interface. The central claim is Buzz's openness—built on the Nostr protocol—lets users swap agent harnesses (Claude Code, Codex, Goose) without losing context, and all chats, projects, and decisions carry through each swap. Vinny demos building a CRM app with Wasp framework deployed to Railway and a tweet leaderboard that pipes daily stats into a channel via public API, showing agents can work end to end. He recommends pinning agents to specific models (Fizz to FAINVL, Honey to Sonnet) and creating a chief agent officer for delegation. Greg notes Buzz is early but argues it's worth trying to learn the future of agentic work, where context is the foundation and openness prevents vendor lock-in. The episode ends with Vinny hinting at deeper open protocol integrations to come. ## Questions this episode answers ### What is Buzz and how does it treat AI agents differently from Slack? Vinny explains that Buzz is an open-source chat app from Block where AI agents are first-class team members, not mere integrations. Unlike Slack, an agent’s underlying 'harness' (e.g., Claude Code, Codex) can be swapped at any time, and all your chat context travels with it, so you never lose project history when switching models. [2:57](https://gregisenberg.podhood.com/b7b4f9e7-4a6b-4893-9b8f-e906be1b8690?t=177000) ### What did Vinny actually build live with Buzz's agents during the demo? Vinny showed Buzz’s agent building a complete CRM app with the Wasp full stack framework and deploying it to Railway, all from a chat command. The agent handled coding, git pushing, and live deployment, even providing screenshots. He also built a tweet leaderboard that surfaces daily stats through a public API, demonstrating how Buzz can connect internal tools and workflows. [11:20](https://gregisenberg.podhood.com/b7b4f9e7-4a6b-4893-9b8f-e906be1b8690?t=680000) ### What is shared compute in Buzz and who benefits from it? Buzz’s shared compute feature lets a team run a single local AI model on one machine and share it among all members. Vinny highlights this as ideal for bootstrapped students or small teams avoiding costly cloud AI subscriptions, while ensuring model choice and data control, as users aren’t locked into any one provider. [24:02](https://gregisenberg.podhood.com/b7b4f9e7-4a6b-4893-9b8f-e906be1b8690?t=1442000) ## Key moments - **[0:00] Intro** - **[2:57] Agent teammates** - [2:57] Buzz treats agents as first-class team members, making them integral to the chat rather than side features. - **[3:44] Swappable harness** - [3:44] Buzz allows swapping the AI harness under any agent—Claude Code, Codex, or Goose—without losing chat context. - [6:55] Buzz supports audio huddles where agents join voice calls with full chat context. - **[6:56] Audio huddles** - **[8:34] Parallel Git** - [8:34] Agents in Buzz can create Git feature branches and work in parallel worktrees for coding tasks. - [11:20] Vinny prompts Buzz agents to build a CRM app with the Wasp framework and deploy it to Railway in minutes. - **[11:34] Built on Buzz** - [13:43] Buzz enables on-the-fly creation of high-quality software that can be deployed and managed from chat context. - [15:22] Vinny built a tweet leaderboard app with Buzz, then piped daily stats back into a channel through a public API. - [18:13] Vinny predicts Buzz agents can connect to the X API and start tweeting from chat within 15 minutes. - **[20:32] Agent conversation** - [20:32] Q: How should I talk to Buzz agents? A: Have a normal conversation; they excel at pulling intent from context. - [23:52] Buzz's shared compute feature allows a team to run one local LLM and share it across all members. - **[24:02] Shared compute** - [25:42] Vinny warns that proprietary AI model lock-in risks losing control over your data and future price hikes. - [27:36] Greg identifies Buzz as a context layer that preserves all project knowledge when switching tools. - **[27:38] Context layer** - [29:39] Q: How should I set up agents in Buzz? A: Pin agents to specific models based on task complexity to control token costs. - **[29:40] Agent setup** - [31:21] Buzz agents can leverage globally installed skills from Claude Code, but early beta performance is slower than direct terminal use. - [33:03] Buzz is currently best for solopreneurs and small teams building simple apps, not complex software engineering. - **[34:36] The bet** - [34:36] Greg urges founders to try Buzz to learn how agentic work evolves, even if they ultimately stick with Slack. - **[38:10] Closing** - [38:10] Vinny predicts Buzz's open-source, open-protocol foundation could make it the default tool as the community contributes. ## Speakers - **Greg Isenberg** (host) - **Vinny** (guest) ## Topics Agents ## Mentioned Block (company), Buzz (product), Claude Code (product), Codex (product), Discord (product), FAINVL (product), GitHub (product), Goose (product), Granola (product), Hermes (product), OpenClaw (product), OpenCode (product), Railway (product), Slack (product), Sonnet (product), Twitter (product), Wasp (product) ## Transcript ### Intro **Greg Isenberg** [0:01] Jack Dorsey just launched Buzz, and it's gone completely viral. Yes, it's the same Jack Dorsey who co-founded Twitter, who co-founded Block—this guy is building what people are calling a "Slack killer." Now, why does this matter for you? Well, it's being called a Slack killer because it's almost like this agentic version of Slack. It's a way to have conversations with your teammates, except they're agents. It's a way for you to huddle agents. It's a way for you to have software being built on the fly via agents. So in this episode, we're going to break down it so clearly for you so that you understand what it is, why you should use it, and what are the best tips and tricks to use Buzz. My take on this whole thing is it's a glimpse into the future of work. I can't wait to see what you think about it, and by the end of the episode you'll understand: if it's for you, why you should use it, how you should use it. Enjoy the episode. The startup vibe is broadcast. It's ship and time, baby. **Greg Isenberg** [1:07] What's up, Vinny? I saw your tweet. Jack Dorsey retweeted it. By the end of this episode, what are people going to learn? **Vinny** [1:15] They're going to learn how to use Buzz. Mostly, I think it's like the sweet spot for Buzzright now is, I think, solopreneurs, small teams. They're going to learn how to use it to, like, kind of brainstorm, keep everything in context between their agents, and just, you know, build products, build solutions, ideate, and like, yeah, use it to get stuff out there quicker and be more productive. **Greg Isenberg** [1:44] Cool. Okay, so what I hope to get from this is basically: understand what Buzz is, understand why it matters, understand some best practices on how I can use it to actually use agents to do things for me. And by the end of this episode, I want to understand if I should actually use this thing, or should I just basically continue using Slack. And that's what I hope to get out of this. Do you think you could commit to that? And also, while you're going through it, just share the best practices that haven't been shared anywhere so that, you know, we've got a little edge on people. You think you can do that? **Vinny** [2:23] Yeah, I think so. I just want to start off by saying, like, I think the Slack killer—you know, it's a good line that it's a Slack killer. But I think the real, like, the real selling point for me with Buzz, like, from the beginning, is just the openness of it. So do we want to start there? Just, like, what I mean by open and what kind of, like, what that allows, like the power, how powerful the openness feature of Buzz is. **Greg Isenberg** [2:52] Yeah, I mean, sell me on Buzz. Like, why? **Vinny** [2:55] Okay, okay. **Greg Isenberg** [2:56] Yeah. **Vinny** [2:57] So first off, it's Slack with agents inside, and a lot of people—like, it's kind of like Slack. You got agents inside, so Slack allows you to do that by adding an integration. But in Buzz, they're like first-class citizens,right? ### Agent teammates **Vinny** [3:13] So they're members of your team. You don't think of them as, like, add-ons or just kind of a side feature. They're an integral part of the app. They are part of your team. Think about it that way. So I'm kind of—I like to keep things simple, and I just started using this not too long ago. I mean, it's only been out for a little while. I just discovered it. And these are basically what you see here are the default agents you get when you start. But under the surface, there's a really powerful thing, which is you can edit and add agents. ### Swappable harness **Vinny** [3:44] And when you give agent instructions, that's just basically like a system prompt. The really cool thing underneath is the harness. So we're all probably using Codex, Claude Code, maybe something like Open Code to do our coding work, build products, whatever, be more productive. The great thing here is that your agent harness is swappable under any agent. So I can go under here and say, you know, I want to use Claude Code, I want to use Codex, I want to use Goose. And like, for me already, that point there was like, okay, this is very cool. And the reason why this is so cool is because, I mean, if any of you, all your listeners probably follow this stuff, AI moves at, like, breakneck pace,right? So today it's this model, the next day it's the other model. And sometimes, I don't know about you, but personally, I'm like, I get model fatigue where I'm just like, gosh, you know, I just switched over to this. I just got used to this model. Like, I don't even want to hear the good things about model X because I'm still over here using model Y. But the cool thing about this is that this is a layer on top of that, and you can just switch. And the best part is that your agent, you don't lose anything in that switching process. You can change the harness under your agent, and all the context that's in your chats, so everything you've been chatting about with this agent, like all the stuff you're trying out, the apps you're building, all that context comes with to that new harness, to that new model. So first off, that's something I think is really cool about Buzz. **Greg Isenberg** [5:26] That's a huge deal because I feel like a lot of us are ping-ponging between different models and harnesses and stuff like that, and it's tiresome. You know, when you're starting from scratch, it does feel like—and then I need to understand, okay, what is Saul good at too? You know, like, and what are the contexts for this particular model to get the most out of it? So I think the fact that this is built natively into the product, that you can go and switch, just, like, I like that because it's thinking about how people are working in today's day and age, and they're acknowledging it, and they're like, we understand that, yes, there's going to be new models all the time, and you might want to be switching, but you probably don't want to spend a lot of time adding context, figuring out things, because you're busy trying to run a startup, trying to make money, trying to be productive. **Vinny** [6:24] Yep, yep. Exactly. And you can take all your stuff with you. You know, like, if you've built all these skills and skill files and folders and stuff, you know, as long as they're in, like, the global directory, if they're accessible globally and they're not project-specific, like, Buzz can access them. So you can install agent skills like normal, you can change—then you can change harnesses, change models, and your agents in the chat have access to all of them. So I think that's really cool. I'm really happy about that. **Greg Isenberg** [6:56] Okay, what else do we need to know? ### Audio huddles **Vinny** [6:59] We've got audio huddles with agents. So that allows you to have, like, an audio chat with your agents, and they'll be in the chat and they'll respond to you. And so you can, you know, have a voice call with someone else, bring an agent in and communicate, and they also get the context of your whole chat in the audio huddle. So that's pretty cool. I haven't tried that out yet, though. So I have seen there's some good videos on YouTube that run through it and show you how to do it. **Greg Isenberg** [7:26] What's cool about huddling and, you know, agents or an agent—I tweeted about this. I feel like what I'm missing from building in the AI age is I feel like I'm asking my agents to do things. Maybe I'm using WhisperFlow or even just typing it, and it feels very much like back and forth, back and forth. What's cool about a huddle is it's live. And the way my brain works when I'm being creative and stuff like that is I need, like, live interaction in order to really, like, extract what's going on in my brain. I think there's probably a lot of people like me like that, so it's cool that that's a feature. My dream—and I tweeted this—my dream is eventually to have, like, the ability to FaceTime agents. And that, to me, is like the holy grail of the future of work. But, you know, cool that you can see that Buzz is scratching the surface here. Is it good or is it not good? We'll have to test it. People in the comment section, please let us know. But it's interesting that that feature exists. What's another feature that you're excited about? ### Parallel Git **Vinny** [8:38] I mean, well,right under the surface, you've got these agents, and you probably want them to do work. So they're, like, integrating—they have Git pretty tightly integrated into it, and your agents will actually, you know, they're doing coding, they can create projects, they'll create feature branches, and they work in parallel worktrees. So they're not actually messing with stuff that's locally on your computer. They'll make a worktree, a copy, and they can work there. So they can do things in parallel. So you could, for example, you know, you're talking to your teammate about a UI, the design of your product or your webpage or something, and you can just, you know, tell the agent, like, spin up three different versions of landing pages based on the ideas that you guys had in the chat,right? And they've just added this projects view. So if you go into settings here, there are experiments. You can turn on workflows and projects, for example, and then you'll see that here. And this is basically like, you know, your apps that you're coding on with your agents and working on with your agents. And another interesting thing is that you can integrate with GitHub, but under the surface, they have their own hosted Git hosting. So you can push to remote repositories that are actually on your relay. So that's probably a more technical thing, but Buzz works on relays. So these are, like, servers that you host and/or that get hosted for you by Buzz, by Block, and then they'll actually push that code to the remote repositories on your relay. So the relay is where all your information, all your chats, everything, that's where all that stuff is happening and where it's stored and where it's getting sent and pushed to the other people, you know, chatting with you and the agents chatting with you. So I can see in the future that they're trying to take on more than just Slack here. They're trying to take on GitHub as well. So that's pretty crazy. **Greg Isenberg** [10:49] Cool. And I think, you know, for the non-technical audience, I feel like a lot of my non-technical friends are actually starting to use GitHub now in the AI age. I don't know if you've noticed this. **Vinny** [11:01] No, I don't. I'm just kind of in the. **Greg Isenberg** [11:04] Bubble? **Vinny** [11:05] Mostly in the, yeah, the nerd bubble. **Greg Isenberg** [11:07] Yeah, it's interesting. It's just, I feel like, you know, five years ago, if you were non-technical, ten years ago, if you were non-technical, you barely knew what GitHub was. The word "repo," you were like, you know, are you repossessing my car? You know, but I think now, in an AI age where we're kind of all technical in some way, something like this makes a lot of sense to be built natively. ### Built on Buzz **Vinny** [11:34] Yeah. And the interesting thing is you don't really have to know that much about it. You don't really have to even consider it because your agents will just kind of take care of stuff for you. Like, I was doing stuff here where I was asking you, you know, pull up a simple CRM app. And, you know, I told it, here's the chatright here, spin up a simple CRM app using the Wasp full stack framework and deploy it to Railway for me. So, you know, there's some technical knowledge there. You know, I'm asking for a specific framework, a specific hosting provider, but it'll do that and even, you know, get stuff, pushes it to these remote repositories, deploys it live on the web, and even sends you screenshots. So it's like, oh, here's your CRM, here's your that I just made. And that's all before I even checked out what it was even doing. So it just, it did it for me, gave me the links, gave me a little preview of it, and yeah, I thought that was pretty cool. **Greg Isenberg** [12:36] That's insane. **Vinny** [12:38] Yeah, there's a lot of, I feel like they've baked in a lot of workflows and a lot of just, like, prompts into these agents so that these agents kind of can work end to end and really get tasks done. I think that's the idea. **Greg Isenberg** [12:53] Yeah, that's insane. Like, if you think about it, like, we're kind of, like, glossing over it, but, like, look what you've built. **Vinny** [13:00] Yeah. And it's like, it's live on the internet,right, already. So the nice thing is, you know, I already had a Railway account. I, you know, I know a little bit about working with full stack apps, but I didn't really tell it much. I just said, you can see the chat, put this online. So now I have a fully functioning CRM dashboard that I can share with team members, and then we can, the cool thing is then what you would do is you'd add them to this chat here, and you'd start talking about what features are missing, what things you don't like, like, and then you guys, you know, you have a conversation with your teammates, and you come to a conclusion, and you just tell your agents to go ahead and start working on it, and they'll do it. **Greg Isenberg** [13:44] So why this is a big deal is if you think about it, you know, you're able to create software on the fly, essentially automated, that's high quality, that could be deployed, that you can manage in a view that, you know, is clear. And I think, you know, if you think about your business, let's say you work, you have an agency business, proposals is, you know, the lifeblood of your business in a lot of ways,right? And, you know, imagine that you can create proposals based on people's data. Maybe you're pitching the NFL, and you know, you could put in the context of the pitch meeting notes, let's say, from Granola or something else. It ingests it, and then on the fly, you have these agents based on that create proposals that are unique to those clients. And it's vibe coded or it's using agents to actually, you know, create them. You know, there's so many ways that you can use this interface to think about, okay, I have, you know, context over here, this is how it comes in, and then here's how it's going to get spin up on the internet or through, you know, an asset that is built within code, and then here's how you're going to view it. Is thatright? **Vinny** [15:07] Yep, yeah, exactly. In one of the videos I made that I posted on Twitter, that was what I was going through. So I was taking it more of, like, a marketing angle, and I built a tweet leaderboard for Twitter. So, like, my team, like, how much we're tweeting, how good, what are our top tweets, all that stuff, all that information was being collected in this app, this full stack app. And then I was like, oh, well, instead of just building it with Buzz, why don't I get Buzz to also access the app, get that information, then we can get, like, you know, daily reviews here, daily digests, and we can also, like, kind of brainstorm on what's working in our Twitter strategy for marketing, what's not working, get it to find, like, links between the popular tweets and, you know, brainstorm, come up with new stuff. So that's exactly what I did. I had it, I told it, let's build a publicly facing API, and then let's build a workflow. So I just tell it, daily, you know, check that API and give me the numbers back. And then the awesome thing is, that's what you're seeingright here in this tweet stats from app, it's getting the stuff from that dashboard through an externally facing API and putting it here into this channel, and then I can reply to it and be like, okay, Fizz, which is one of the agents, like, Fizz, let me know what's the common thread between my successful tweets this last seven days, because it also sends those over the API. So if I understood you correctly, I think you're talking about kind of these workflows where you're like, this circular stuff where you're giving information in, getting it out through apps, and it's all going into the context of your agents and stuff like that. **Greg Isenberg** [16:59] Exactly. **Vinny** [17:00] Yeah. **Greg Isenberg** [17:00] Yeah, I mean, I'm interested in this because this is like the quote-unquote boring stuff that every business has that if you can figure out how to have some unfair advantage here, it's what separates a good business from a bad business. **Vinny** [17:18] Yeah. And that's the thing I really like is that this openness of Buzz, like, it allows this kind of, these kind of integrations to happen very easily. So with Slack, like, you would have to, you know, to get all this kind of stuff up and running, you'd have to get API tokens, create an app on their platform. All their stuff is proprietary. You have to, like, learn the structure of things. I mean, with agents, it's easier, but here, because it's built on these open protocols, like, you can get stuff like this running really easily, and then you have this just, like, crazy context engine that just can help you do work. Like, if I wanted to, I could ask Fizzright now, you know, like, connect up the app or, you know, connect yourself to the X API and make it available so that we can start tweeting from Buzz. Like, that wouldn't be that hard. We could probably do that in 15 minutes, you know? **Greg Isenberg** [18:13] Crazy. **Vinny** [18:14] One thing that I really like about this kind of, you know, this closed, we were talking about this closed circle of, like, context that I'm getting back from my app, so that tweet dashboard app is that, like, here it sends me the tweets every day and the stats, like the top tweets and my stats and impressions, and I can just ask the agent, like, let's make sure I'm replying there, and I'll just say, like, what can, like, what is the common thread between my top tweets? And sometimes, like, I used to do this in a session with Claude Code or ChatGPT where I'd be, like, literally, you know, exporting tweet data or copying and pasting tweet data and putting it into ChatGPT on the desk or in the browser, you know, getting information chatted about it and pulling it back. But, like, this is so cool because it's pulling the, it's getting the information from the X API. It's in the context window of the agents here. I can chat about it here, and then, you know, we can chat with colleagues about, like, what, you know, what are some more tweets we want to push out? What's a different marketing angle we could take? And that's what I really like about this here. And you can see there is the agent working. So what's actually going on in the background, that's nice if you're used to looking at this kind of stuff in a terminal. You can actually see the tool calls that it's, the tools that it's calling and think, or here it is, down here, like, what is happening. So it's getting information from the channels, checking for newer stats and things like that, gets the results. And so it's all, like, kind of under the curtain stuff, but we should get a response back soon. **Greg Isenberg** [20:13] And is there, is there any, like, tips around how you, it's best to talk to them? Like, I see here is you just wrote a short and concise question, but how do you, how should, how should people think about the best way to talk to some of these agents? **Vinny** [20:32] I mean, they're pretty good at pulling out the intent behind your questions these days. So just have a conversation with them, like, like you would, like a normal person. So I don't think, I at least don't have any special approach there. ### Agent conversation **Vinny** [20:47] I kind of just say, you know, some, this is probably nicer than what I would normally type. Like, usually I got typos in there and stuff. I'm like, give me the sauce, you know? And they're usually pretty good at that because they have all this context. So I'm usually pretty straightforward and concise with, like, the questions and the stuff, the prompts I give. Reported back. So it's showing, like, what I did. I tried Jack's Buzz. I deployed OpenSAS to OpenShip, my first time successfully self-hosting. So it's like, it's showing that, you know, I'm doing these things as a beginner, and I'm reporting back on what I learned, and those are the things that are doing well. So it worked. Are my top two, top two tweets got over a million impressions, but this sucked theme got a, you know, they were the bottom half, and they got a collective, you know, 88,000. So novelty gets you reach, friction gets you engagement. So there's some actually really good advice there, and, like, that's kind of the power of using it here and having all of it in Buzz is that it makes stuff like this easy and illuminating. So that's really cool. I like that. **Greg Isenberg** [22:04] By the way, I saw one of the, one of the pieces of feedback is nobody is mentioning that Buzz has a backdoor for Bitcoin native payments. What does that mean? **Vinny** [22:17] So Buzz, we were talking about open protocol, so I kind of glossed over this. It's built on Nostr, and Nostr is the name of the open protocol that Buzz is built on. And I personally believe, because, you know, if you know Jack Dorsey, he's a big fan of Bitcoin. Nostr is tightly coupled with Bitcoin Lightning, which is a very fast and, like, almost feel-less way to pay and transfer Bitcoin. And my guess here is that because it's built on Nostr, Nostr is open, you'll be able to integrate Lightning, Bitcoin Lightning payments into Buzz, and you'll either be able to pay, agents will be able to pay for compute, this shared compute idea that we talked about, or that's in there in the settings. You'll be, agents will be able to pay for work and compute, or people will be able to pay other people, tip other people for tasks they get done. So, like, I could honestly imagine a big open community of, let's say, I don't know why I keep gravitating towards graphic designers, but, like, say designers, and, you know, you need a really cool logo, and AI gen, image gen isn't really doing it for you, and you ask some people to, like, you know, spit out some ideas, and some random person in some, you know, graphic design community on Buzz gives you, like, an awesome logo, and you just, you know, boop, tip them. Thank you for that idea, and then you go ahead and keep working. And, yeah, we'll see. It's not integrated at the moment, but I think it will come. **Greg Isenberg** [23:52] Very cool. Awesome. So what else do people need to know about Buzz? **Vinny** [23:59] So let's see. You mentioned that shared compute idea, and I think that goes back into, like, the openness of Buzz, and that's really cool. And that was something that really surprised me too. So why don't we just talk about that for a minute? ### Shared compute **Vinny** [24:16] So we've got this compute setting here, and you can turn it on, and it will automatically suggest some local LLM, some local model, AI models that you can download on your laptop or on your computer, and you can literally share them with the other members of your team. So let's say that you are just starting out, you're a college student, and you want to start building a business. You've got this awesome idea. You don't have a lot of time. You don't have a lot of help, and you don't have, you know, like, the money to buy one of these Max Pro plans, whatever they're called, with, like, unlimited token budget. So you could get together with some friends, you know, buy a decent size laptop or a Mac Studio or something, or maybe even, like, a beefy Mac Mini. You put this on, you share compute, and all of you can use this one model running from one machine, even though you're chatting from different, from different laptops, from different computers, whatever. So that's just, like, a very simple example, but you can see how they're paving the road here for real openness in model choice and being able to, like, really harness the power of these open source and local models that are always getting stronger and, you know, starting to compete with the frontier models from Anthropic and OpenAI. So I think that's really cool. **Greg Isenberg** [25:43] And why do you think that even this is worth playing with, you know? You know, why is this really important? Why is local important in the grand scheme of the future of work? **Vinny** [25:58] I mean, model choice is important depending on what you want to do. And, you know, it's the same idea where Slack is the controller of your data, and that data is very valuable. You're sitting here, you know, spending, I mean, this stuff makes work a lot easier, but you still have these really cool ideas. You're iterating on these ideas. You're putting stuff out there that you work pretty hard on and that you think a lot about. And then to have, like, just one company control all that data, basically, like Slack, for example, have the whole, all your data in that sessions, and if you're tired of Slack and want to move to something else, it's really hard, or it might not even be possible to take all that data with you to some other platform. So you just stay there, and you're stuck with them. It's the same thing for models. You know, you see people talking about why, you know, there are, who knows, today it costs $200 a month for an unlimited plan. Tomorrow it might be $2,000. We don't know. We don't know how, what's going to happen. And the future, you know, having choice in the future is very important for the integrity, for the sustainability of any business because that's your data. That's what you want to be able to do with it. I don't know. Some of these models have restrictions on what you're even able to ask them. So governments have top-down mandates on what they're allowed to do with the models or not. So, you know, we saw models get pulled back after people started using them for a couple of days. So, like, you're building your businesses on top of these tools. You should be, you should have flexibility and freedom and control of these tools, basically. **Greg Isenberg** [27:38] Yeah. And I think the big insight of all of this is a lot of us haven't realized how much of a content ### Context layer **Greg Isenberg** [27:48] hub Slack and products like that have become to us. And we're learning that if you want to get the best out of any of these models, you need to have the most amount of context possible. So what's really cool about Buzz is it's basically like, okay, we recognize that this is your context foundation, and we're going to go help you do a bunch, like, we're going to help you pivot into a bunch of directions. You want to, you know, have these projects that, you know, are integrated to GitHub, we can go do that. If you want to do local stuff and do shared compute, we can help you do that, you know, et cetera, et cetera. You want to huddle an agent, we can help you do that. But it, you know, what's so cool about it is whatever you decide to do, the context is at the core of it. **Vinny** [28:39] Yep. Yep, exactly. And that's what I like about it. That's what I think is really cool is that I think they really hit on something here. So, you know, I think we'll see. It could go, like, I saw people commenting OpenClaw, you know? Nobody's talking about OpenClaw anymore. OpenClaw was a real wow moment in, like, okay, we can get these agents to do a lot of productive work for us. But I have the feeling that it was missing something and this shared context because we're working in teams. We're working with other people. Teams might even just mean your other agents,right? Like, you just, you're going to have conversations whether it's with one agent or another, but now you have the ability to expand that, like, your team set, expand your, you know, your global context window, so to speak, and then make it globally available to everyone in your team, including the agents. So yeah, I think it's super cool. **Greg Isenberg** [29:40] Around setting up and managing your agents, is there any sauce here? Is there anything people need to know besides what you've already shared? ### Agent setup **Vinny** [29:48] I wouldn't say so. I've seen, it depends on how deep in the weeds you like to go. My honest opinion would be you probably don't need to do that much. All I did, the first thing I did was just I wanted one that's FAINVL. I'm using specifically or exclusively, I'm using Claude Code as the harness under here, but they have adapters, so you can adapt, you know, you could even adapt OpenClaw or Hermes or OpenClaw, or I'm sorry, OpenCode or Goose. So, like, any of these harnesses can be added under the surface here, under the hood. But the first thing I did was I just pinned them to models. So Fizz is a FAINVL model, and Honey is Sonnet because there's just certain tasks that I don't need to use the power of FAINVL and burn through tokens so fast. So that would be, like, my main piece of advice. Besides that, just start playing around. I made this chief agent officer. So, like, if I do start to create more agents with more specific kind of instructions and system prompts, then I might delegate the delegation to Mr. Chief Agent Officer here and be like, okay, I have this task. Who's the best for it? Because, you know, you might have a copywriter, you might have a brainstormer, you might have a code reviewer, things like that, and you might forget who they are, or I don't know, you just get an agent to kind of delegate. So that would be pretty much my only advice on that side there. **Greg Isenberg** [31:21] Cool. Anything else you want to show? **Vinny** [31:23] People were asking in Twitter about skills, and I think I mentioned it already, but, like, all the stuff under the surface that you're used to using, if you use Claude Code or something, that's all available as long as it's to Buzz, your Buzz agents, as long as it's globally installed. So skills and things like that, yeah, they can use and they can take advantage of, so you don't lose that stuff. So that's also very nice. And I would say that, like, this is beta software. It's like, it might even be alpha. I'm not sure. It's like early preview software. So some things don't work that great. I was trying to create workflows and, you know, like, set up recurring tasks and things like that, and they weren't really landing great. That was one thing I noticed. Another thing I noticed was things can be kind of slow. If you're used to it being, like, working directly in Claude Code or in a Codex, it seems to be a bit faster there, and I think it's because it's communicating with your server, your relay, and communicating back. And because of that, I think it's at the point now where it's, like, really good for, like I said, solopreneurs, small teams, iterating on small software or small ideas. And if you're really doing, like, you know, complex software engineering, this might not be the tool that you want to use, but if you're just looking for something that can bring you value and, like I said, bring all this, all your knowledge into one central, one central tool, then this is definitely a great, a great thing to use. **Greg Isenberg** [33:04] So if you're a founder, small team, maybe, you know, one to ten, under $10 million in revenue, zero to $10 million in revenue, like, should you use this thing? Maybe you're using Slack today. Should you download Buzz and actually try it out? **Vinny** [33:23] So I'm pretty convinced that, like, I'm trying to convince my team at Wasp that we use this internally and exactly for that reason. So we are a small company, a small startup, and we're a developer tool, so we're a software company. And, like, you have all this stuff that you talk about in Discord. We talk about in Discord, and we have our community there too. So that's one interest, like, one thing I should mention is that you can create channels that are private and public,right? So you could invite people from your community using your product to come chat with you, and then you have private channels just for your team, and then that context is shared, which is also a huge thing because if someone comes into your chat and says, "Hey, we want to get this fixed," then fixing it with an agent is just a, you know, an at away,right? You would just tell Fizz, like, "Let's tackle this bug." Like, whoever just, you know, did a bug report or said, you know, wanted a feature, you could just have them prototype itright there. So yeah, I think for small teams, this is definitely worth checking out. ### The bet **Greg Isenberg** [34:37] So my take on, my take on this is this is so cool. It's clearly, you know, scratching the surface around what the future of work would look like in a world where you have more agent employees than teammates. It does feel early. It does feel like they're just, you know, like I said, scratching the surface. But, you know, my passion is, I don't know if you know this about me, Vinny, but I'm a co-founder in a company called LCA, Late Checkout Agency. That business designs, like, the world's biggest AI-native software, not Buzz, but, like, you know, companies like that. And when I see something like this, I'm just like, it's close. It's not there yet, but it's close. And I do believe that it's probably worth, and I have no affiliation with Buzz or Block or Jack Dorsey, but I do think it's, like, worth trying these tools just so you can, you might learn a thing or two, and then even if you don't end up using Buzz, like, you might just end up, you know, configuring Slack in a way that, you know, is best for you and you learn something here. So I think, or you might realize, like, you love Buzz and forget about Slack and this is the world you want to live in. Regardless, you're going to learn. There is no losing in this situation. So I think the most important thing we can, one of the most important things that we can do in the AI age and the agentic era is just getting our hands dirty, learning how these tools work, playing with them, and seeing how we could live in the future. Because the people that live in the future, Vinny, those, as you know, those are the people that could, you know, look around the corner and who can create products that people really want. And, you know, I think that's really important. **Vinny** [36:36] Yeah. And, yeah, you bring up a really good point, and I think that's why they're kind of looking around the corner with this already. And what I think could allow them to really be a strong player in this arena is the fact that it's open source. So anybody, you know, that has an idea of how to, so it's an open source app built on an open protocol. And so anyone who has an idea of how to improve this can, and, you know, that might take it in the direction because the, you know, the hive mind, so to speak, is, like, going to be using this thing and working on it at the same time. So they'll be like, "Okay, this isn't working for me. I like this about," like you said, "trying out from some other tool. I like this about the tool I usually use. I'm going to add that in here or whatnot." So that might work to their advantage very well, and it might become the tool that people just kind of default to. But things change so fast, so who the hell knows? **Greg Isenberg** [37:42] Amen, brother. Vinny, thank you so much for coming on, giving us a tour, sharing some sauce. I'll include links in the show notes, in the description, where you can follow Vinny for more of this sort of stuff. I would love to have you back on the podcast, Vinny. The comment section on YouTube, please let me know if you enjoyed Vinny. I certainly did. If you enjoyed this topic, what you want me to cover next. Thank you so much, Vinny. Any last words for the people? ### Closing **Vinny** [38:13] Well, if they want me to come back, I can show them some sweet stuff about how you can, like, use the open protocol that Buzz is built on. So you can go pretty deep. And I think there's some pretty powerful stuff there that we both alluded to in our tweets. So yeah, it's worth checking out. **Greg Isenberg** [38:30] Cool. Yeah, let us know. And we live to serve. So if that's what people want, we can go deeper. Thank you, Vinny. Have a creative day, everyone, and I'll see you next time. --- This library is powered by PodHood (https://podhood.com), the podcast website platform.