Loading video...

Video Failed to Load

Go Home

pov: you're running 15 loops across in glm 5.2 in opencode, codex, claude, amp or pi and have no idea which one needs you, bring em all to opensessions cmux, superset - cool ideas, but i got tired of blank screens, glitchy terminals, and macos-only apps i just wanted...

Palanikannan_M's profile picture

Palani — oss/acc

1,183 subscribers

13,942 views • 1 month ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I love working in terminal, but I can't design or brainstorm in there. So I built Hatch! One IDE for the full loop: explore ideas → test out designs with SuperDesign.Dev → find right skills for the job → ship with agents. > build: supports Claude code, OpenCode and Cursor agents in parallel with worktrees. > idea maze: use the canvas to sketch out ideas, paste tweets or images. > idea maze: let your agent make connections, critique your ideas or come up with related ones. > design: bring SuperDesign.Dev prompts or exports directly into your workspaces. vibedesign before vibecoding. > skills: ask your agent what skills to get with your workspace context. All open source!
0:24

I love working in terminal, but I can't design or brainstorm in there. So I built Hatch! One IDE for the full loop: explore ideas → test out designs with SuperDesign.Dev → find right skills for the job → ship with agents. > build: supports Claude code, OpenCode and Cursor agents in parallel with worktrees. > idea maze: use the canvas to sketch out ideas, paste tweets or images. > idea maze: let your agent make connections, critique your ideas or come up with related ones. > design: bring SuperDesign.Dev prompts or exports directly into your workspaces. vibedesign before vibecoding. > skills: ask your agent what skills to get with your workspace context. All open source!

Firat Sertgoz

38,578 views • 6 months ago

I'm open-sourcing tws, the tool I've been using for the last few months to organize my engineering work. I've always been a terminal-first engineer; tmux + nvim has been my default. Then AI coding agents arrived and shifted what I needed from that setup. Running several Claude Code and Codex sessions in parallel, the flat tmux session list stopped being enough. So I built tws to fit how I actually work now. It's built on top of tmux, no reinvented wheel. You keep all of tmux's power and flexibility underneath. On top of that, it gives you: - Threads: an abstract organizational layer above tmux sessions, so related work groups together instead of sitting in a flat list - Notes: quick markdown notes attached to each thread or session, kept right next to your work - Fast switching: fuzzy finding, recent-session jumps, and keyboard-driven navigation between everything - Agents view: every Claude Code / Codex session running across your projects in one place, with the ability to pin the ones you keep coming back to Fully configurable — themes, palette, keybindings — via a TOML file. If tmux + terminal isn't your setup, this probably isn't for you. But if you like working from terminal, you might like it. It's been the core piece of how I work for a while now. Github:
0:20

I'm open-sourcing tws, the tool I've been using for the last few months to organize my engineering work. I've always been a terminal-first engineer; tmux + nvim has been my default. Then AI coding agents arrived and shifted what I needed from that setup. Running several Claude Code and Codex sessions in parallel, the flat tmux session list stopped being enough. So I built tws to fit how I actually work now. It's built on top of tmux, no reinvented wheel. You keep all of tmux's power and flexibility underneath. On top of that, it gives you: - Threads: an abstract organizational layer above tmux sessions, so related work groups together instead of sitting in a flat list - Notes: quick markdown notes attached to each thread or session, kept right next to your work - Fast switching: fuzzy finding, recent-session jumps, and keyboard-driven navigation between everything - Agents view: every Claude Code / Codex session running across your projects in one place, with the ability to pin the ones you keep coming back to Fully configurable — themes, palette, keybindings — via a TOML file. If tmux + terminal isn't your setup, this probably isn't for you. But if you like working from terminal, you might like it. It's been the core piece of how I work for a while now. Github:

Yusuf

219,855 views • 1 month ago

We built Openwork! I found Claude Cowork to be too expensive So i asked Claude Code to build me a better version with Composio tool router It can: - access local files and your terminal via claude code - connect and use 500+ apps like gmail, outlook, slack on demand - chain actions across local files and cloud apps in one flow In the demo we use it to scan through my laptop and find all my unfinished projects and put them in a notion database with completion status. excited to see more usecases link:
1:09

We built Openwork! I found Claude Cowork to be too expensive So i asked Claude Code to build me a better version with Composio tool router It can: - access local files and your terminal via claude code - connect and use 500+ apps like gmail, outlook, slack on demand - chain actions across local files and cloud apps in one flow In the demo we use it to scan through my laptop and find all my unfinished projects and put them in a notion database with completion status. excited to see more usecases link:

Karan Vaidya

241,615 views • 6 months ago

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!
1:38

Introducing 🌸 Kanna – a web ui for Claude Code + Codex running right in your browser (and my first open source project!) It's sort of like if Claude Code & Codex had a baby with a much better ui/ux 💅 Here's what makes Kanna special: 🔀 One-click switch between Claude Code / Codex 🌐 Runs in your browser on localhost - no app switching 🧩 Embedded split terminals, persisted between chats with a beautiful horizontal scrolling UX 📁 Full project file browser built in, embedded editor coming soon too. Coming soon: 🔒 End-to-end encryption + remote access via reverse proxy 🌿 Git integration, diffs, PRs 🧱 Plugins I wanted to replace switching between cursor, the github app, browser & (most recently) the codex app. The browser is hardest to recreate yet also the most flexible so it makes sense to build in the browser itself. Install in 5 seconds: bun install -g kanna-code then just type: kanna Kanna is purely a ui/ux layer. It uses your existing CLIs, is 100% compliant & no data ever leaves your machine. If running claude or codex in your terminal works, kanna works too. Kanna natively supports every tool call, model, reasoning effort, fast mode, plan mode, compaction, user questions, web searching, skills, agents, mcps, everything. There are a few libraries that do this but none that I found as comprehensive. All feedback welcome!

Superdaddy

43,285 views • 4 months ago

Claude Code is unusable. So I built my own. Introducing BridgeCode. Launching next Wednesday. Everything you love about Claude Code. No rate limits. No 529 errors. No 500 errors. No nerfing. Connect to any provider. Claude Opus 4.6. GPT 5.4. Gemini 3.1 Pro. GLM 5.1. All of them. Switch models in seconds. And one more thing. Swarm mode. One prompt. Ten agents. Working together to ship your code. Claude Code rate limited me into building a competitor. Thank you, Anthropic. Launching next Wednesday.
0:21

Claude Code is unusable. So I built my own. Introducing BridgeCode. Launching next Wednesday. Everything you love about Claude Code. No rate limits. No 529 errors. No 500 errors. No nerfing. Connect to any provider. Claude Opus 4.6. GPT 5.4. Gemini 3.1 Pro. GLM 5.1. All of them. Switch models in seconds. And one more thing. Swarm mode. One prompt. Ten agents. Working together to ship your code. Claude Code rate limited me into building a competitor. Thank you, Anthropic. Launching next Wednesday.

BridgeMind

47,103 views • 3 months ago

Tired of managing 5 different AI API keys? 😩 I just switched to CometAPI and now I use GPT-4o, Claude, Gemini, Grok + image models with ONE single key. All I did was change the base_url and api_key in my code. Done in 15 seconds. No new libraries. No extra logins. No mess. Now I can test any model instantly and everything stays in one dashboard. Super clean for side projects or real apps. If you build with AI at all, this makes life way easier. Check it:
0:48

Tired of managing 5 different AI API keys? 😩 I just switched to CometAPI and now I use GPT-4o, Claude, Gemini, Grok + image models with ONE single key. All I did was change the base_url and api_key in my code. Done in 15 seconds. No new libraries. No extra logins. No mess. Now I can test any model instantly and everything stays in one dashboard. Super clean for side projects or real apps. If you build with AI at all, this makes life way easier. Check it:

Wesley

71,489 views • 1 month ago

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨
0:59

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨

Daniel San

124,913 views • 11 months ago

WeWeb MCP is here. Your favorite AI agents can now build directly inside WeWeb. Bring Claude Code, Cursor, ChatGPT, Codex, Antigravity, or any agent you choose. Your agent can help build secure web apps using WeWeb’s pages, components, workflows, API requests, databases, integrations, auth, storage, and more. You decide what it can work on: the full app, or only specific parts of your project. Everything stays visible and editable in WeWeb, so you can review what was built, make changes visually, and keep maintaining the app with your team. No black box. Open beta starts today.
8:36

WeWeb MCP is here. Your favorite AI agents can now build directly inside WeWeb. Bring Claude Code, Cursor, ChatGPT, Codex, Antigravity, or any agent you choose. Your agent can help build secure web apps using WeWeb’s pages, components, workflows, API requests, databases, integrations, auth, storage, and more. You decide what it can work on: the full app, or only specific parts of your project. Everything stays visible and editable in WeWeb, so you can review what was built, make changes visually, and keep maintaining the app with your team. No black box. Open beta starts today.

weweb.io

1,386,257 views • 1 month ago

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)
5:02

Loop engineering is great until something breaks. Here is how I improve the reliability of my agentic loops. I use human-in-the-loop (HITL). It's easy and extremely effective. Anyone can build this. My setup: I recorded a quick demo of how it all works. I shared recently that I now use more voice agents to build and communicate with agents. I also use them to verify. I hate the idea of being tied down to my computer or in a Slack channel to communicate with my agents. Here is what I have done to streamline communication with my agents. All my Claude and Codex agent sessions now use the Dial MCP server. It has a bunch of tools and provisions my agents with their own number that can place calls as native tools, with voice, SMS, and iMessage behind one interface. As my loops/automations work on PRs and new features, my agents escalate decisions to me via a short phone call. This is extremely useful when I am on the road or away from my desk. If you want to try this with Claude Code or Codex, paste this into your agent and get started right away: "Get yourself a Dial phone number and call me. Say hello and that setup is working, then hang up. Follow Natan Voitenkov and team are building something special here. Go check them out. Give your agent a phone number now: ($5 free credit)

elvis

15,295 views • 19 days ago

i was tired of running my one woman BD team for the past 2.5 years so I built my own in use /bd-intern in claude to initiate > intern sets up a quick interview to understand you better > all other agents get full context and are ready to roll > setup takes less than 5 min, runs via a Claude Plugin stop doing and start prompting
0:54

i was tired of running my one woman BD team for the past 2.5 years so I built my own in use /bd-intern in claude to initiate > intern sets up a quick interview to understand you better > all other agents get full context and are ready to roll > setup takes less than 5 min, runs via a Claude Plugin stop doing and start prompting

Mashiat

16,472 views • 4 months ago

OKKKK Ive fully automated Codex + Claude Code it take any app idea and runs a fleet of parallel agents in iterative loops nonstop for 24hr+ it can research, design, plan and execute for DAYS zero back and forth it also costs $0 because it’s powered by AI subs we all already pay for so I could have 100s of complex, polished iOS apps built in 30 days if i really wanted to - for the SAME price as anyone else on the same subscription this is CLONK
0:32

OKKKK Ive fully automated Codex + Claude Code it take any app idea and runs a fleet of parallel agents in iterative loops nonstop for 24hr+ it can research, design, plan and execute for DAYS zero back and forth it also costs $0 because it’s powered by AI subs we all already pay for so I could have 100s of complex, polished iOS apps built in 30 days if i really wanted to - for the SAME price as anyone else on the same subscription this is CLONK

Paulius 🏴‍☠️

44,744 views • 1 month ago

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.
1:54

How I have Claude automate anything I do on my computer just by showing it: I use the free Clips app and hit record to start recording. Then I just do the action - like navigating to Rippling and approving any unapproved time off - and I’ll often just talk out loud as I do it explaining any add’l details like I would when showing a human. The Clips app captures everything on your screen and everything you say, and transforms it into a format Claude can “see and hear”. You'll then get a link that you can easily share with Claude (or humans too). I’ll paste it to Claude and say something like, "automate this for me every day at 8:00 AM." The link has special metadata that agents like Claude can discover. It exposes APIs to see the full transcript with timestamps and grab screenshots of what was on your screen at any of those timestamps. Once it's created the routine, you can go to the Routines tab in Claude Code desktop app. This also works with the CLI, Claude Cowork, Codex etc. You’ll see your new routine there, and you can just hit Run Now to have it start running it. Video attached shows this step by step. The Clips apps is free and open source - I’ll link to it and the source code in the thread.

Steve (Builder.io)

25,187 views • 26 days ago

Bolt 2.0 is here - and it changes everything about building apps with Bolt. No external Supabase connections. No RLS headaches. No auth setup. No separate analytics or hosting. Plus, you can use Claude code directly inside Bolt. Now everything happens inside bolt.new. Here’s how I built a full app in 10 minutes - DB, auth, analytics, and hosting - all with just a few prompts. Everything you need to know about 2.0 🧵
0:20

Bolt 2.0 is here - and it changes everything about building apps with Bolt. No external Supabase connections. No RLS headaches. No auth setup. No separate analytics or hosting. Plus, you can use Claude code directly inside Bolt. Now everything happens inside bolt.new. Here’s how I built a full app in 10 minutes - DB, auth, analytics, and hosting - all with just a few prompts. Everything you need to know about 2.0 🧵

Dhruval

69,311 views • 9 months ago

THIS GUY ADDED A LIVE BROWSER TO CLAUDE CODE SO YOU CAN CLICK ANY ELEMENT AND EDIT IT INSTANTLY biggest issue with vibe coding UI is that you have to describe what you want to change. if you prompt it the wrong selector or wrong component, Claude can't find it. now you just click it. your app runs in an embedded browser with Claude Code. you can click any button, any text, any div. Claude instantly knows exactly what you're pointing at. click. instruct. done. no more "change the button in the top right corner of the second card component." all you have to do now is just click the button. AND its open source
0:40

THIS GUY ADDED A LIVE BROWSER TO CLAUDE CODE SO YOU CAN CLICK ANY ELEMENT AND EDIT IT INSTANTLY biggest issue with vibe coding UI is that you have to describe what you want to change. if you prompt it the wrong selector or wrong component, Claude can't find it. now you just click it. your app runs in an embedded browser with Claude Code. you can click any button, any text, any div. Claude instantly knows exactly what you're pointing at. click. instruct. done. no more "change the button in the top right corner of the second card component." all you have to do now is just click the button. AND its open source

Om Patel

152,845 views • 3 months ago

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!
28:01

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!

JJ Englert

29,809 views • 3 months ago

"I am a Claude Code maximalist. I try to live in it all day if I can." Carl Vellotti 🥞 has gone deeper on Claude Code than any PM I know. In my new episode, he showed me how to connect Claude Code to: → Google Workspace: Prep for meetings → Linear: Create tickets from PRDs → Slack: Share status updates → Reddit: Monitor subreddit discussions He does all of the above using skills and MCPs in his personal Claude Code OS. Some quotes from Carl: "Connecting Claude Code to the apps that you use at work makes it way more powerful." "Why would you need to go to all these websites if you can just get the info right here?" "I use this consult-the-council skill to get Claude, ChatGPT, and Grok to all review my work in one shot." 📌 Watch now: Thanks to our sponsors: Granola - The best AI meeting notes app I've ever used: Replit ⠕ - Create beautiful prototypes and full stack apps:
0:41

"I am a Claude Code maximalist. I try to live in it all day if I can." Carl Vellotti 🥞 has gone deeper on Claude Code than any PM I know. In my new episode, he showed me how to connect Claude Code to: → Google Workspace: Prep for meetings → Linear: Create tickets from PRDs → Slack: Share status updates → Reddit: Monitor subreddit discussions He does all of the above using skills and MCPs in his personal Claude Code OS. Some quotes from Carl: "Connecting Claude Code to the apps that you use at work makes it way more powerful." "Why would you need to go to all these websites if you can just get the info right here?" "I use this consult-the-council skill to get Claude, ChatGPT, and Grok to all review my work in one shot." 📌 Watch now: Thanks to our sponsors: Granola - The best AI meeting notes app I've ever used: Replit ⠕ - Create beautiful prototypes and full stack apps:

Peter Yang

141,421 views • 4 months ago

I've used Claude Code to build 20+ projects in the last 6 months. Thousands of new users across them. And I've never written a single line of code. I just dropped a 24-min video with my top 10 tips for non-developers — the exact playbook I use every day to run multiple AI agents that handle work that used to take me a full week. This is the best beginner guide to learning and building with Claude Code out right now. Every tutorial I found assumes you're a developer. This one doesn't. I cover everything from first install to running multi-agent workflows — with live demos and real examples for every single tip. How I set up new projects, how I got Claude to match my writing style, how I automate repeatable workflows with one command, and how I run multiple agents working on different tasks at the same time. I also built a full resource repo to go alongside the video — curated video tutorials, the best skill libraries, plugin directories, MCP server guides, written docs, community links, and a starter template you can copy-paste into your first project today. Comment "GUIDE" and I'll send you the full guide with everything you need to learn Claude Code! (make sure we're connected so I can DM you)
24:48

I've used Claude Code to build 20+ projects in the last 6 months. Thousands of new users across them. And I've never written a single line of code. I just dropped a 24-min video with my top 10 tips for non-developers — the exact playbook I use every day to run multiple AI agents that handle work that used to take me a full week. This is the best beginner guide to learning and building with Claude Code out right now. Every tutorial I found assumes you're a developer. This one doesn't. I cover everything from first install to running multi-agent workflows — with live demos and real examples for every single tip. How I set up new projects, how I got Claude to match my writing style, how I automate repeatable workflows with one command, and how I run multiple agents working on different tasks at the same time. I also built a full resource repo to go alongside the video — curated video tutorials, the best skill libraries, plugin directories, MCP server guides, written docs, community links, and a starter template you can copy-paste into your first project today. Comment "GUIDE" and I'll send you the full guide with everything you need to learn Claude Code! (make sure we're connected so I can DM you)

JJ Englert

419,218 views • 5 months ago

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)
0:39

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)

Akshay 🚀

167,968 views • 21 days ago

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:
1:21

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

42,501 views • 1 month ago

Cursor vs Claude Code (day 3 of 30) today I re-tested Conductor and I don't want to overhype this but... what the actual fook 😮 this thing is amazing! closest things to the "perfect workflow" I have seen in a long time, and it's something I could see myself use full-time it's so minimal and the polar opposite of Cursor but it has all the essentials → Claude Code + Codex subscriptions (= unlimited usage) → great integration with Claude Code's plan mode → multiple tabs with multiple agents at the same time → can use multiple models, not just one → great file tree and diff viewer → best git worktree support I've ever seen there's honestly so much more, like a dedicated "review" button (which you can pair to your favorite review model, e.g. gpt-5.2-extra-high), buttons to create and merge pull requests, to launch your dev server, ... this solves literally EVERY fault I can think of when using Claude Code and/or Codex, combining both into one easy UX that not only does everything the tools can do, but actually adds useful stuff on top just 6 months ago I couldn't have dreamt about any this and the wildest part is that IT IS FREE (I'd literally pay for this UX lol) first time I'm genuinely enjoying myself since starting this challenge not saying it's a full Cursor replacement yet, it obviously isn't for a lot of people (no browser, no debug mode, no code indexing, etc) ... but this is the closest thing I've seen yet 👀 follow for day 4!
5:56

Cursor vs Claude Code (day 3 of 30) today I re-tested Conductor and I don't want to overhype this but... what the actual fook 😮 this thing is amazing! closest things to the "perfect workflow" I have seen in a long time, and it's something I could see myself use full-time it's so minimal and the polar opposite of Cursor but it has all the essentials → Claude Code + Codex subscriptions (= unlimited usage) → great integration with Claude Code's plan mode → multiple tabs with multiple agents at the same time → can use multiple models, not just one → great file tree and diff viewer → best git worktree support I've ever seen there's honestly so much more, like a dedicated "review" button (which you can pair to your favorite review model, e.g. gpt-5.2-extra-high), buttons to create and merge pull requests, to launch your dev server, ... this solves literally EVERY fault I can think of when using Claude Code and/or Codex, combining both into one easy UX that not only does everything the tools can do, but actually adds useful stuff on top just 6 months ago I couldn't have dreamt about any this and the wildest part is that IT IS FREE (I'd literally pay for this UX lol) first time I'm genuinely enjoying myself since starting this challenge not saying it's a full Cursor replacement yet, it obviously isn't for a lot of people (no browser, no debug mode, no code indexing, etc) ... but this is the closest thing I've seen yet 👀 follow for day 4!

Robin Ebers • Build Apps With AI

40,726 views • 7 months ago