The Startup Ideas Podcast - Jack Dorsey's Buzz: The New Hermes Agent?

Episode Date: July 28, 2026

I sit down with Vinny for a live tour of Buzz, an open source, agent-native chat app from Block built on an open protocol. Vinny makes the case that openness is the real story here: agents arrive as first-class teammates, the harness underneath each agent swaps freely between Claude Code, Codex, Goose, and open code, and your entire chat context travels with you through every swap. He demos real output, including a CRM app built with the Wasp full stack framework and deployed to Railway, plus a tweet leaderboard that pipes daily stats back into a channel through a public API. I press him for the honest state of the software and for the setup advice he actually uses day to day. By the end I share where I land on Buzz versus Slack, and why I think anyone building right now gains from putting their hands on tools like this. Timestamps 00:00 – Intro 02:57 – Agents as First-Class Team Members 03:49 – Swappable Harnesses Under Any Agent 06:55 – Audio Huddles With Agents 08:34 – Git, Feature Branches, and Parallel Worktrees 11:20 – Building a CRM App with Buzz and Agents 13:43 – Why This Matters 18:13 – Best way to engage with your Agents 23:53 – Shared Compute and Local Models 25:42 – Model Choice, Data Ownership, and Lock-In 27:36 – Context as the Foundation 29:39 – Setting Up Agents 31:21 – Skills and Speed 33:03 – Who Should Try Buzz Today 34:36 – My Take: Live in the Future 38:10– Closing Thoughts Key Points Buzz treats agents as members of your team, so one shared chat becomes the context layer for humans and agents together. The harness under any agent swaps freely, and every chat, project, and decision comes along for the ride. Globally installed agent skills stay available inside Buzz, so an existing Claude Code setup carries straight over. Agents branch, work in parallel worktrees, push to Git hosting on your own relay, and ship live apps end to end. Shared compute lets a small team run one local model on one machine and use it from many computers. Buzz sits in early preview today, which makes it a strong fit for solopreneurs and small teams iterating fast. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND VINNY ON SOCIAL: X/Twitter: https://x.com/hot_town Youtube: https://www.youtube.com/channel/UCHP5Hdx0X-sM0uv2bl_OOqg

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 their 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. What's up, Vinny? I saw your tweet. Jack Dorsey retweeted it. By the end of this episode, what are people going to learn? They're going to learn how to use Buzz. Mostly, I think it's like the sweet spot for Buzz right 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 product. build solutions, ideate, and like, yeah, use it to get stuff out there quicker and be more productive. 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. You think you could commit to that? And also, while you're going through it, just shared the best practices that haven't been shared anywhere so that we've got a little edge on people.

You think you can do that? 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 for uh with buzz like from the beginning is just the the openness of it so um do we want to start there just like what i mean by open and and what kind of like what that allows

like the power how powerful the openness feature of buzz is yeah i mean sell me on buzz like why okay okay yeah um so first off um 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? 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're 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. 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, cloud 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 Claudecode.

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 the stuff, AI moves at like a 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, that 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. 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 context 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. Yeah, yeah, exactly. And you can take all your stuff with you, you know, like if you're, if you've built a 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 to 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. Okay. What else do we, what else do we need to know? We've got audio huddles with agent. 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 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. So what's cool about huddling? agents or an agent, I tweeted, 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 live.

And the way my brain works when I'm being creative is stuff like that is I need like live. 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 if it's not good? We'll have to test it. People in the common section, please let us know. But it's interesting that that feature exists. What's another feature that you're excited about? 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. they work in parallel work trees. So they're not actually messing with stuff that's locally on your computer. They'll make a work tree, 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 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. Cool. And I think, you know,

for the non-technical audience, 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. No, I'm just kind of in the, I'm mostly in the nerd bubble. Yeah, it's interesting. It's just I feel like, you know, five years ago, if you were non-technical, 10 years ago, if you're non-technical, you barely knew what GitHub was. The word repo, you're like, are, 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. 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 chat right 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, gets stuff, pushes it to these remote repositories, deploys it live on the web, and even sends you screenshots. So it's like, okay. here's your, 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. That's insane. That's insane. Yeah, there's a lot of, I feel like they've baked in a lot of workflows and, um, a lot of just

like, uh, prompts into these agents so that these agents kind of can work enter. end and really get tasks done. I think that's the idea. Yeah, that's insane. Like, if you think about it, like, we're kind of like glossing over it, but like, look what you felt. 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 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. 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. 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 is clear. And I think, you know, if you think about your business, let's say 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're, 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 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 an asset that is built within code. And then here's how you're going to view it.

Is that right? 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 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 the 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, um, give me the numbers back.

And then the awesome thing is that's what you're seeing right here. And this tweet stats for app 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 FIS, 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. Exactly. Yeah.

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. Mm-hmm. Yeah.

And that's the thing I really like is that this openness of buzz, like, it allows 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, that'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 Fizz right 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? Crazy. One thing that I really like, about this kind of, you know, this close, 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, the 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, um, Claude code or chat GBT where I'd be like literally, you know, exporting tweet data or copying pasting tweet data and putting it into chat GPT on the, on the, um, desk, or on the, uh, in the browser, you know, getting information chat about it and pulling it back. But like, this is so cool because it's,

pulling the 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 um you know we're we can chat with colleagues about like what do you know what are some more tweets we want to push out what's a different marketing angle we could take and um 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 um If you're used to looking at this kind of stuff in a terminal, you actually see the tool calls that it's the tools that it's calling. And here it is down here, like what it's happening.

So it's getting information from the channels, checking for newer stats and things like that, gets the result. And so that's all like kind of under the curtain stuff. But we should get a response back soon. And is there, is there any, like tips around how you is 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 to talk to some of these agents um i mean they're pretty good at pulling out the 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, special approach there. I kind of just say, you know, 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 try. jacks buzz. I deployed open SaaS to open ship 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 makes stuff like this easy and illuminating.

So that's really cool. I like that. By the way, I saw one of the pieces of feedback is nobody is. mentioning that Buzz has a backdoor for Bitcoin native payments. What does that mean? So Buzz, we're talking about Open Protocol. So I kind of glossed over this. It's built on Noster. And Noster is the name of the Open Protocol that Buzz is built on. And I personally believe, because if you know Jack Dorsey, he's a big fan of Bitcoin. Noster has tightly coupled with Bitcoin Lightning, which is a very fast and almost.

most feeless way to pay and transfer Bitcoin. And my guess here is that because it's built on Noster, Noster's 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, 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 I can honestly imagine a big open community of, let's say,

I don't know why I keep gravitating towards graphic designers, but like I 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, 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. Very cool. Awesome. So what else do people need to know about Buzz? 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? So we've got this compute setting here and you can turn it on and it will automatically suggest some local LLM, some local AI models that you can download on your laptop or on computer and you can literally share them with the other members of your team. So let's say that you 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 an 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 Open AI.

So I think that's really cool. And why do you think that even this is worth playing with? You know, why is this really important? Why is the local important in the grand scheme of the future of work? 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 i mean this stuff makes work a lot easier but you're you still have these really cool ideas you're iterating

on these ideas um 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 um 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 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. Yeah, and I think the big insight of all of this is a lot of us haven't realized how much of a content 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 content. 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 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. is at the core of it. 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, open claw, you know, nobody's talking about open claw anymore. Open claw was a real wow moment and 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 you're going to have conversations whether it's with one agent or another. But now you have the ability to expand that the like your team set, expand your global context window, so to speak. And then make it globally available to everyone in your team, including the agent. So, yeah, I think it's super cool. 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? 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 fable. I'm using specifically or exclusively I'm using clawed code as the harness under here. But they have adapters so you can adapt, you know, you can even adapt open claw or Hermes or open code 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 FIS is a fable model and honey is sonnet. because there's just certain tasks that I don't need to use the power of fable 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. Cool. Anything else you want to show? 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 clod 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 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, solarpreneurs, 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 your knowledge into one central tool, then this is definitely a great thing to use. So if you're a founder, small team, maybe one to 10, 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 to? out. 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. 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 an app away, right? You would just tell Fizz, like, let's tackle this bug. Like whoever just did a bug report or said, you know, wanted a feature, you could just have them prototype it right there. So, yeah, I think for small teams, this is definitely worth checking out. So 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, like I said, scratching the surface. But, you know, my passion is, I don't know if you know this about me, Vinnie, but I'm a co-founder in a company called LCA, lay checkout agency. And that business designs like the world's biggest AI native software, not buzz, but like 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 Blocker 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 what 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, in 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. 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 place. layer 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, 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? Amen, brother. Denny, 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 fall. 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? Well, if they want me to come back, I can show them some sweet stuff about

how you can use the open protocol that its buzz is built. 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. Cool. Yeah, let us know. And we live to serve. So if that's what people want, we can go deeper.

Thank you, Vinnie. Have a creative day, everyone. And I'll see you next time.