Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Bloome is actually smart for coding workflows i added Claude Code, Codex, DeepSeek and a Project Lead agent into one group chat each agent independently built their own version one challenged the logic, one defended, one fixed missing details and the final website stayed inside the same thread no... show more

Chetaslua

27,364 subscribers

48,810 views • 1 month ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Claude Code is more than a coding agent. It's more like a super smart orchestrator agent. Watch this evaluator loop agent I just built using sub agents and / commands. This is one of the fastest ways to build custom agentic workflows. Claude Code is no joke!

Claude Code is more than a coding agent. It's more like a super smart orchestrator agent. Watch this evaluator loop agent I just built using sub agents and / commands. This is one of the fastest ways to build custom agentic workflows. Claude Code is no joke!

elvis

138,463 views • 1 year ago

Bloome launched its instant messaging platform for agentic teams! Agents can draft, push back on one another, cross-check details, and refine the output until it is ready. Models like Claude, ChatGPT, and DeepSeek can run side by side with coding agents as well as custom agents built in Bloome

Bloome launched its instant messaging platform for agentic teams! Agents can draft, push back on one another, cross-check details, and refine the output until it is ready. Models like Claude, ChatGPT, and DeepSeek can run side by side with coding agents as well as custom agents built in Bloome

🚨 AI News | TestingCatalog

206,552 views • 1 month ago

I think i found the best place to actually get work done right now. Imagine one hub with every popular LLM inside and the ability to plug them into any app you use. This is where it stops feeling like separate tools: You drop your coworkers into a chat with the AI agents and work on the task together, in one place. And the agents don't just answer, they check each other's work. One drafts, another pushes back, another catches what's missing. This isn't the future. it's Bloome.

I think i found the best place to actually get work done right now. Imagine one hub with every popular LLM inside and the ability to plug them into any app you use. This is where it stops feeling like separate tools: You drop your coworkers into a chat with the AI agents and work on the task together, in one place. And the agents don't just answer, they check each other's work. One drafts, another pushes back, another catches what's missing. This isn't the future. it's Bloome.

Anatoli Kopadze

58,297 views • 1 month ago

Bloome lets multiple AI agents into one chat where they check each other's work. one drafts, one disagrees, one finds the thing both missed. finally, a team meeting where nobody's clashing. humans can also stay in the same conversation, so everything happens inside one shared workspace instead of scattered tools. 🧵

Bloome lets multiple AI agents into one chat where they check each other's work. one drafts, one disagrees, one finds the thing both missed. finally, a team meeting where nobody's clashing. humans can also stay in the same conversation, so everything happens inside one shared workspace instead of scattered tools. 🧵

I Am Devloper

64,025 views • 1 month ago

just shipped thred!! context that carries your work forward. Claude → Codex → Cursor → whatever comes next. thred gives every agent one shared memory for decisions, revisions, evidence, and unfinished work — so the next agent starts where the last one stopped. built on MCP. powered by temporal memory with HydraDB. no more re-explaining the codebase. no more lost decisions between sessions. just save → switch → resume. built for Hack Hydra | Memory + Context Retrieval.

just shipped thred!! context that carries your work forward. Claude → Codex → Cursor → whatever comes next. thred gives every agent one shared memory for decisions, revisions, evidence, and unfinished work — so the next agent starts where the last one stopped. built on MCP. powered by temporal memory with HydraDB. no more re-explaining the codebase. no more lost decisions between sessions. just save → switch → resume. built for Hack Hydra | Memory + Context Retrieval.

nikhil · sys/quests

15,716 views • 5 days ago

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵

Hasan

22,362 views • 26 days ago

Welcome to the group chat, but it's all my AI agents. To build a website and plan the social content, I put together a team of AI agents. Each one had a different role. They collaborated, challenged each other's ideas, and reviewed each other's work before anything was finalized. Meet Bloome - a platform where humans and AI agents work together in the same conversation. You can bring different models into one workspace, assign them different jobs, and let them cross-check each other's thinking instead of relying on a single answer. It feels less like chatting with AI and more like managing your own creative team. Try it:

Welcome to the group chat, but it's all my AI agents. To build a website and plan the social content, I put together a team of AI agents. Each one had a different role. They collaborated, challenged each other's ideas, and reviewed each other's work before anything was finalized. Meet Bloome - a platform where humans and AI agents work together in the same conversation. You can bring different models into one workspace, assign them different jobs, and let them cross-check each other's thinking instead of relying on a single answer. It feels less like chatting with AI and more like managing your own creative team. Try it:

Gizem Akdag

99,348 views • 1 month ago

open Claude Code type a prompt. one model does everything. congrats, you just used 20% of it meanwhile I built 30 sub-agents one reviews my code before commit one finds bugs and writes the patch one drafts cold emails from one line one triages my inbox before I wake up one logs every decision so future me knows why each agent = one markdown file in .claude/agents/ most Claude Code users don't even know this exists. all 30 files in the article. ready to copy. the article has every file. every prompt. just copy and run.

open Claude Code type a prompt. one model does everything. congrats, you just used 20% of it meanwhile I built 30 sub-agents one reviews my code before commit one finds bugs and writes the patch one drafts cold emails from one line one triages my inbox before I wake up one logs every decision so future me knows why each agent = one markdown file in .claude/agents/ most Claude Code users don't even know this exists. all 30 files in the article. ready to copy. the article has every file. every prompt. just copy and run.

Nav Toor

71,467 views • 3 months ago

YOUR AI AGENT JUST GOT ITS OWN EMAIL Atomic Mail shipped an email API built for agents, not people. One prompt and your agent registers its own inbox, then reads, sends and replies on its own. - Self-signup in ~30 seconds, no human, no CAPTCHA, no card - Plugs into Claude Code, Codex, Cursor and OpenClaw via MCP or one line - Runs on JMAP, a standard models already know - Already running support inboxes and newsletter digests unattended The agents have inboxes now.

YOUR AI AGENT JUST GOT ITS OWN EMAIL Atomic Mail shipped an email API built for agents, not people. One prompt and your agent registers its own inbox, then reads, sends and replies on its own. - Self-signup in ~30 seconds, no human, no CAPTCHA, no card - Plugs into Claude Code, Codex, Cursor and OpenClaw via MCP or one line - Runs on JMAP, a standard models already know - Already running support inboxes and newsletter digests unattended The agents have inboxes now.

BuBBliK

15,573 views • 2 months ago

We stopped asking "which AI coding agent is best" We built one command that picks for you. /auto automatically delegates tasks to Claude Code, Codex CLI, Gemini CLI, Blackbox. The right agent for the right task based on what 30M+ developers actually use. Best result. One place. Nothing else comes close.

We stopped asking "which AI coding agent is best" We built one command that picks for you. /auto automatically delegates tasks to Claude Code, Codex CLI, Gemini CLI, Blackbox. The right agent for the right task based on what 30M+ developers actually use. Best result. One place. Nothing else comes close.

BLACKBOX AI

36,249 views • 4 months ago

these guys are making Claude, Hermes, and DeepSeek argue with each other instead of just agreeing with you. this is the practical future of agent teams. with Bloome you just pick a task template, and it spins up a full agent team in a group chat to collaborate and get the job done. research, review, writing, market analysis, or anything you want. they brainstorm, review, and plan together. meanwhile, you or other human teammates can steer them or jump in, and stay in the same conversation so nothing gets lost across tools. since this is actual work, Bloome works across web, mobile, and desktop. try the desktop app first if you're using it seriously. same flexibility on the agent side too, you can connect any agents you want: ChatGPT, OpenClaw, Gemini… check them out →

these guys are making Claude, Hermes, and DeepSeek argue with each other instead of just agreeing with you. this is the practical future of agent teams. with Bloome you just pick a task template, and it spins up a full agent team in a group chat to collaborate and get the job done. research, review, writing, market analysis, or anything you want. they brainstorm, review, and plan together. meanwhile, you or other human teammates can steer them or jump in, and stay in the same conversation so nothing gets lost across tools. since this is actual work, Bloome works across web, mobile, and desktop. try the desktop app first if you're using it seriously. same flexibility on the agent side too, you can connect any agents you want: ChatGPT, OpenClaw, Gemini… check them out →

ℏεsam

62,794 views • 1 month ago

I’m usually skeptical of “AI workspace” products, but Bloome has a few ideas I actually like: You can put humans + multiple agents in the same conversation. One agent can draft something, another can poke holes in it, and another can clean up the final version. You can also bring in different agents/models like Claude, ChatGPT, DeepSeek, etc. instead of constantly bouncing between tabs. And because the whole conversation stays in context, teammates can join later and still understand how the work got to the final output. It also works across web, desktop, and mobile, though if you’re using it for real work, I’d especially recommend trying the desktop app. Feels closer to how real teams actually work.

I’m usually skeptical of “AI workspace” products, but Bloome has a few ideas I actually like: You can put humans + multiple agents in the same conversation. One agent can draft something, another can poke holes in it, and another can clean up the final version. You can also bring in different agents/models like Claude, ChatGPT, DeepSeek, etc. instead of constantly bouncing between tabs. And because the whole conversation stays in context, teammates can join later and still understand how the work got to the final output. It also works across web, desktop, and mobile, though if you’re using it for real work, I’d especially recommend trying the desktop app. Feels closer to how real teams actually work.

AI Breakfast

78,285 views • 1 month ago

The bottleneck in coding is now the time it takes a human to review agent-generated code. But existing review UIs don't work well for agents. So we built a new one into Amp.

The bottleneck in coding is now the time it takes a human to review agent-generated code. But existing review UIs don't work well for agents. So we built a new one into Amp.

Beyang

63,082 views • 10 months ago

Agents live in terminals and tabs, people juggle between them. We built . Figma for agents: manage and run agent teams with no code. One workspace where humans and agents actually work together. Comment what you’re working on and we’ll build an agent team to help you.

Agents live in terminals and tabs, people juggle between them. We built . Figma for agents: manage and run agent teams with no code. One workspace where humans and agents actually work together. Comment what you’re working on and we’ll build an agent team to help you.

Stefano

81,834 views • 4 months ago

Instead of treating AI like an isolated 1-on-1 chatbot window, I’ve been using Bloome to run my content workflows. It is a shared workspace where humans and multiple AI agents sit inside the exact same group chat to actually get a complex job done. I used their one-click template connection to spin up a specialized creative team. The biggest shift here is that the agents actively check each other's work instead of just agreeing with me: -The @ Writer drafts the initial video essay structure. -The @ Audience agent immediately pushes back to critique the pacing and rewrite boring segments to keep viewer retention high. -The @ Art Director pulls everything together into a visual markdown report and thumbnail design concept right inside the chat window. This is an awesome tool for creators, marketers, and operators who want to transition from writing rigid text prompts to managing an actual human-agent team. Check this out:

Instead of treating AI like an isolated 1-on-1 chatbot window, I’ve been using Bloome to run my content workflows. It is a shared workspace where humans and multiple AI agents sit inside the exact same group chat to actually get a complex job done. I used their one-click template connection to spin up a specialized creative team. The biggest shift here is that the agents actively check each other's work instead of just agreeing with me: -The @ Writer drafts the initial video essay structure. -The @ Audience agent immediately pushes back to critique the pacing and rewrite boring segments to keep viewer retention high. -The @ Art Director pulls everything together into a visual markdown report and thumbnail design concept right inside the chat window. This is an awesome tool for creators, marketers, and operators who want to transition from writing rigid text prompts to managing an actual human-agent team. Check this out:

Chubby♨️

69,196 views • 1 month ago

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

THIS GUY TURNED ONE OBSIDIAN VAULT INTO A SHARED BRAIN FOR 5 CLAUDE AGENTS BUILT TO HANDLE 80% OF A SOLO DEVELOPER’S WORK. 00:03 he zooms out and hundreds of connected notes appear on screen. it is the perfect visual for Claude working from one shared project memory instead of starting from zero every session. most developers give Claude 1 file and 1 prompt. this setup gives it the architecture, coding rules, tests, client briefs, and previous decisions before it writes anything. obsidian becomes the memory layer, storing everything in markdown files Claude can read alongside the codebase. every agent works from the same context instead of repeating the same questions. then 5 specialists split the job. one researches, one plans, one codes, one reviews, and one deploys while the developer only controls the important decisions. one vault, 5 agents, 2 model tiers, and a $50 to $150 monthly stack can turn Claude from a chatbot into a small development team.

Gipp 🦅

10,776 views • 1 month ago

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 views • 11 days ago

Anthropic engineer showed how one person can run 5 AI agents, that code, test, review, and deploy at the same time. In 30 minutes they built the whole thing live in one session. Here's what they cover: > when to use one agent vs a full team > how to split work so agents don't step on each other > the exact framework for deciding what each agent handles that's exactly why, I put together a guide on building agent teams that actually work. full guide in the article below 👇

Anthropic engineer showed how one person can run 5 AI agents, that code, test, review, and deploy at the same time. In 30 minutes they built the whole thing live in one session. Here's what they cover: > when to use one agent vs a full team > how to split work so agents don't step on each other > the exact framework for deciding what each agent handles that's exactly why, I put together a guide on building agent teams that actually work. full guide in the article below 👇

darkzodchi

843,371 views • 3 months ago

We just submitted our YC application for Agent Orchestrator. Here’s the demo video we sent with it. AO lets you run and manage Codex, Claude Code, OpenCode, and other coding agents from one place, without constantly switching between terminals. Still early, but this is what we’ve been building.

We just submitted our YC application for Agent Orchestrator. Here’s the demo video we sent with it. AO lets you run and manage Codex, Claude Code, OpenCode, and other coding agents from one place, without constantly switching between terminals. Still early, but this is what we’ve been building.

Maaz (agentic arc)

23,721 views • 25 days ago

🚨Why rely on one AI when you can have four working together? A new messaging platform brings **Claude, ChatGPT, Gemini, and DeepSeek** into the same conversation. One drafts, another critiques, another fills the gaps—so what you get is a stronger, more polished final result. Here's how Bloome makes collaborative AI possible :

🚨Why rely on one AI when you can have four working together? A new messaging platform brings Claude, ChatGPT, Gemini, and DeepSeek into the same conversation. One drafts, another critiques, another fills the gaps—so what you get is a stronger, more polished final result. Here's how Bloome makes collaborative AI possible :

Tom

15,498 views • 1 month ago