Clip'd Score any video free
Hype Check · Greg Isenberg

Worth your time?

Jack Dorsey's Buzz: The New Hermes Agent? by Greg Isenberg

Jack Dorsey's Buzz: The New Hermes Agent? Watch on YouTube
Hype score · lower is better
18/100
Useful / Authentic

This video primarily teaches: it gives a hands-on tour, demos, and practical tips for using Buzz rather than pitching a paid product.

Substance80
Proof65
Pitch pressure10
Claim inflation15
The 15-second version

Post it, send it, settle the argument.

Download clip
Receipts

Why this score

  • 3:42Explains the swappable harness and preserved chat context when switching models (concrete product design detail), which raises substance because it’s a specific, usable capability rather than hype.
  • 11:48Host says he asked Buzz to spin up a CRM with Wasp and deploy it to Railway and received links/screenshots, a live demo-level claim that increases proof (shows the feature working end-to-end).
  • 21:31Speaker reports concrete metrics, 'my top two tweets got over a million impressions', this gives quantifiable evidence that the workflow produced measurable results, boosting proof.
  • 31:48Guest calls Buzz 'beta/alpha' and notes slow or flaky workflows, which lowers inflated promise risk and reduces claimInflation because the video caveats limitations rather than guaranteeing perfection.
Title deliveredTitle asks if Buzz is a new agent-style platform (Hermes-like); the video explains Buzz’s agent-first design, openness, harness switching, and tradeoffs, so it delivers on that promise.
Skip the video

The short version

Kept by Clip'd

This episode walks through Jack Dorsey’s new app Buzz and why it’s being called a potential Slack killer: agents are first-class team members, you can swap underlying LLM harnesses without losing chat context, and agents can build, deploy, and iterate on software with Git and hosted relays. The hosts demo live workflows (agents spinning up a CRM and deploying to Railway), explain openness (Noster protocol, shared compute, Bitcoin Lightning integration potential), and give practical audience advice on who should try Buzz now and how to configure agents and models.

Keep the lesson

What it teaches

  • Design for portable context. Keep chat, app state, and assets decoupled from any single model or hosting provider so you can swap models, change vendors, or upgrade tooling without losing history or skills. Apply this when you expect rapid model churn or when your team needs vendor flexibility. Don't apply it when a si
  • Separate the orchestration layer from compute. Treat the agent UI and skills as an orchestration layer and make the LLM/harness replaceable underneath (cloud code, Claude Code, Fable, Goose). Use this when building team-facing tools that must evolve with model innovation. Avoid it if low latency and single-model optimi
  • Use shared compute to democratize model access. Host a local model on one machine and share the instance to lower costs and increase model choice for small teams or student projects. Apply when budget or token limits matter. The common mistake is assuming hosted frontier models are always superior; sometimes a shared l
Jump straight there

Key moments

  • 2:56Buzz treats agents as members of your team, shifting mental model from add-on integrations to first-class collaborators.
  • 4:58Demonstration that you can switch the agent harness/model (cloud code, codeex, goose) without losing chat context or skills.
  • 7:01Announcement of audio huddles with agents, enabling live voice collaboration with agents that carry chat context into the call.
  • 8:44Explanation that agents create projects, feature branches and parallel work trees via Git, preventing local repo conflicts.
  • 11:53Live demo where an agent is asked to 'spin up a simple CRM app using the Wasp fullstack framework and deploy it to Railway,' then returns a deployed link and screenshots.
  • 16:10Example of circular workflows: Buzz pulls data from an externally facing API (tweet stats), ingests it, and agents analyze it directly inside the chat.
Lines worth keeping

Quotes

  • My take on this whole thing is it's a glimpse into the future of work.0:44
  • They're an integral part of the app. They're part of your team.3:12
  • you don't lose anything in that switching process.5:02
  • whatever you decide to do, the context is at the core of it.28:32
Clip'd

Skip the video. Keep the lesson.

Score your next video free