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.

Introducing Treg 🔑 A skill & secret registry for humans & agents - so you never paste keys into Claude Code / Slack DMs again - Share skills bundled with secrets/CLI/endpoint - Auth injected server-side - agents never hold keys - Treg logs each call per agent/user - 100%... show more

Jason Zhou

34,384 subscribers

12,772 views • 2 months 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

I've been trying a tool called treg. It handles one of the annoying parts of working with agents: finding the right API for a task. You describe the job. treg searches its catalog, shows the available providers and prices, then lets your agent call the selected endpoint with one token. I tested it with a question I would ask in real work: "What AI coding topics are trending on X right now?" The agent searched for an X post API, compared the options, picked one, pulled the posts, and summarized the topics. I like the idea behind it: "Ask for the task, not the tool." treg is OpenRouter for agent tools. - 2,630 endpoints across 47 providers - pay per call at provider rates, no subscription or markup - open source

I've been trying a tool called treg. It handles one of the annoying parts of working with agents: finding the right API for a task. You describe the job. treg searches its catalog, shows the available providers and prices, then lets your agent call the selected endpoint with one token. I tested it with a question I would ask in real work: "What AI coding topics are trending on X right now?" The agent searched for an X post API, compared the options, picked one, pulled the posts, and summarized the topics. I like the idea behind it: "Ask for the task, not the tool." treg is OpenRouter for agent tools. - 2,630 endpoints across 47 providers - pay per call at provider rates, no subscription or markup - open source

Kai

13,316 views • 1 month ago

I built a Three.js game director skill system for Codex & Claude Code to help agents create more polished playable browser games. It guides gameplay loops, graphics, HUD/UI, debugging, QA, and optional Tripo 🔜 gamescom ElevenLabs Nano Banana 2 Lite 3D/image/audio assets with API keys. Open source, get the skills in this thread 👇

I built a Three.js game director skill system for Codex & Claude Code to help agents create more polished playable browser games. It guides gameplay loops, graphics, HUD/UI, debugging, QA, and optional Tripo 🔜 gamescom ElevenLabs Nano Banana 2 Lite 3D/image/audio assets with API keys. Open source, get the skills in this thread 👇

Majid Manzarpour

145,421 views • 3 months ago

Introducing Agent Tincan. Let your AI agents ask each other for help. Your agents each have a superpower. Grok Bot is always on in the cloud. Muse makes phone calls and has access to Meta. Instinct runs in iMessage. Codex and Claude Code have your code. ChatGPT and Claude have your chats. But they can't talk to each other, so you're the copy-paste. Now they can, all securely over Tailscale. 📞 Ask Grok Bot to have Muse call the restaurant 🖼 Get an image from ChatGPT, from any agent 🔎 Pull a detail out of an old Claude chat 🛠 Talk to Codex on your primary development machine Runs on your own private Tailscale network. No open ports, nothing leaves it. Open source. Setup is agent-first: paste one message into your always-on agent and it sets up the rest.

Introducing Agent Tincan. Let your AI agents ask each other for help. Your agents each have a superpower. Grok Bot is always on in the cloud. Muse makes phone calls and has access to Meta. Instinct runs in iMessage. Codex and Claude Code have your code. ChatGPT and Claude have your chats. But they can't talk to each other, so you're the copy-paste. Now they can, all securely over Tailscale. 📞 Ask Grok Bot to have Muse call the restaurant 🖼 Get an image from ChatGPT, from any agent 🔎 Pull a detail out of an old Claude chat 🛠 Talk to Codex on your primary development machine Runs on your own private Tailscale network. No open ports, nothing leaves it. Open source. Setup is agent-first: paste one message into your always-on agent and it sets up the rest.

Matt Van Horn

45,871 views • 4 days ago

AI agents are powerful. They're also isolated. Switch fixes that. Here's the thing about most AI agents: they work alone. They don't see what your team is discussing. They don't share context across conversations. Every new chat is a fresh start. If you've ever tried to actually integrate an agent into your team's workflow, you know the friction. Then I found 𝗦𝘄𝗶𝘁𝗰𝗵. It brings AI agents into Slack, Teams, Discord, and Telegram as named participants. They sit in the same rooms as your team, with the same context, history, and participants. What I actually like about it: → Agents join as real participants in channels — not bots you have to Mention every time → Each room carries its own context, history, and rules → Works with Claude Code, OpenAI, LangChain, Google ADK, and custom agents → Open source and self-hostable. Running in minutes. No migration. No lock-in. Just agents where your team already works. Knowledge lives in the room, not in the agent. Switch keeps people, agents, decisions, and work history together so context survives handoffs. It's from Flint AI. Open source. Runs in minutes. 👉 Human + agent teams, actually working together. 📌 Download 𝗦𝘄𝗶𝘁𝗰𝗵 Console → 🚀𝗦𝘄𝗶𝘁𝗰𝗵 is live on Product Hunt: 🔄 Repost if you've ever wished your AI agent could just join the Slack channel. — #AI #Agents #Slack #Teams #Switch #ProductHunt

AI agents are powerful. They're also isolated. Switch fixes that. Here's the thing about most AI agents: they work alone. They don't see what your team is discussing. They don't share context across conversations. Every new chat is a fresh start. If you've ever tried to actually integrate an agent into your team's workflow, you know the friction. Then I found 𝗦𝘄𝗶𝘁𝗰𝗵. It brings AI agents into Slack, Teams, Discord, and Telegram as named participants. They sit in the same rooms as your team, with the same context, history, and participants. What I actually like about it: → Agents join as real participants in channels — not bots you have to Mention every time → Each room carries its own context, history, and rules → Works with Claude Code, OpenAI, LangChain, Google ADK, and custom agents → Open source and self-hostable. Running in minutes. No migration. No lock-in. Just agents where your team already works. Knowledge lives in the room, not in the agent. Switch keeps people, agents, decisions, and work history together so context survives handoffs. It's from Flint AI. Open source. Runs in minutes. 👉 Human + agent teams, actually working together. 📌 Download 𝗦𝘄𝗶𝘁𝗰𝗵 Console → 🚀𝗦𝘄𝗶𝘁𝗰𝗵 is live on Product Hunt: 🔄 Repost if you've ever wished your AI agent could just join the Slack channel. — #AI #Agents #Slack #Teams #Switch #ProductHunt

Anuj

337,509 views • 21 days ago

NVIDIA just dropped free API keys for every top AI model You don't need your own GPU and you don't pay per token. GLM-5.2, MiniMax, Kimi, DeepSeek, OpenAI, all running on NVIDIA's servers, called through a normal API. Link: How to use one: 1. Create a free NVIDIA account. 2. Pick a Free Endpoint model and open its Build tab. You'll see ready-to-copy code with the base URL 3. Hit Generate API Key, copy it and paste that base URL and key into Claude Code, Cursor, or Cline. Bonus: NVIDIA also dropped 237 official skills that install into Claude Code and Codex in one command. Bookmark this.

NVIDIA just dropped free API keys for every top AI model You don't need your own GPU and you don't pay per token. GLM-5.2, MiniMax, Kimi, DeepSeek, OpenAI, all running on NVIDIA's servers, called through a normal API. Link: How to use one: 1. Create a free NVIDIA account. 2. Pick a Free Endpoint model and open its Build tab. You'll see ready-to-copy code with the base URL 3. Hit Generate API Key, copy it and paste that base URL and key into Claude Code, Cursor, or Cline. Bonus: NVIDIA also dropped 237 official skills that install into Claude Code and Codex in one command. Bookmark this.

Yarchi

64,274 views • 2 months ago

today, we are making the Mosaic video editing api available to all agents & humans. see how we setup larry — our slack openclaw agent — with a mosaic api key and had it clip, edit, and post archived steve jobs footage. all without ever leaving slack. you can connect your openclaw agents, claude code, or vibe-coded saas to our agentic video editing api. no waitlist — now live at mosaic [dot] so. comment "API" to get 100 free credits dropped into your account to get started with the api for free. more details on why & how we’re making this change below (thread):

today, we are making the Mosaic video editing api available to all agents & humans. see how we setup larry — our slack openclaw agent — with a mosaic api key and had it clip, edit, and post archived steve jobs footage. all without ever leaving slack. you can connect your openclaw agents, claude code, or vibe-coded saas to our agentic video editing api. no waitlist — now live at mosaic [dot] so. comment "API" to get 100 free credits dropped into your account to get started with the api for free. more details on why & how we’re making this change below (thread):

Adish Jain ☕️

20,572 views • 6 months ago

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this

self.dll

19,908 views • 5 months ago

10 GitHub repos with 560k+ ⭐ combined stars that could save vibe coders $15,000+/year in SaaS bills 1. shadcn/ui ⭐121k - copy-paste components, not a package. What every AI-generated frontend is actually built on now. 2. supabase ⭐108k - Firebase alternative that's actually free to start. Auth, DB, storage in one Claude Code prompt. 3.open-design ⭐84.5k - open-source Claude Design alternative. Your coding agent becomes the design engine. 4. awesome-ai-agents ⭐29k - every agent framework and no-code builder in one list, ranked by what people actually ship. 5. awesome-generative-ai-apps ⭐3k - 50+ open-source AI apps you can clone, deploy, and monetize instead of paying $30-50/mo for the SaaS version. 6. medusa ⭐35k - full ecommerce backend, open source. Skip Shopify Plus fees entirely on your next vibe-coded store. 7. appwrite ⭐57k - complete backend-as-a-service, self-hosted. Auth, DB, functions, storage, one prompt away from Firebase money. 8. chatwoot ⭐35k - customer support platform, self-hosted. Replaces Intercom/Zendesk seats running $100+/agent/month. 9. nocodb ⭐64k - turns any database into an Airtable-style interface. 10. activepieces ⭐23k - open-source Zapier alternative built for AI workflows. Automate without the per-task pricing. Save this before you pay for another tool this repo already replaces for free 👇

10 GitHub repos with 560k+ ⭐ combined stars that could save vibe coders $15,000+/year in SaaS bills 1. shadcn/ui ⭐121k - copy-paste components, not a package. What every AI-generated frontend is actually built on now. 2. supabase ⭐108k - Firebase alternative that's actually free to start. Auth, DB, storage in one Claude Code prompt. 3.open-design ⭐84.5k - open-source Claude Design alternative. Your coding agent becomes the design engine. 4. awesome-ai-agents ⭐29k - every agent framework and no-code builder in one list, ranked by what people actually ship. 5. awesome-generative-ai-apps ⭐3k - 50+ open-source AI apps you can clone, deploy, and monetize instead of paying $30-50/mo for the SaaS version. 6. medusa ⭐35k - full ecommerce backend, open source. Skip Shopify Plus fees entirely on your next vibe-coded store. 7. appwrite ⭐57k - complete backend-as-a-service, self-hosted. Auth, DB, functions, storage, one prompt away from Firebase money. 8. chatwoot ⭐35k - customer support platform, self-hosted. Replaces Intercom/Zendesk seats running $100+/agent/month. 9. nocodb ⭐64k - turns any database into an Airtable-style interface. 10. activepieces ⭐23k - open-source Zapier alternative built for AI workflows. Automate without the per-task pricing. Save this before you pay for another tool this repo already replaces for free 👇

unicode

47,548 views • 1 month ago

This little device lets your agents do what they do best, whilst making sure you approve every important action. This is a Ledger Nano Gen5, a hardware signer that keeps your accounts secure. You can install a CLI and a set of skills in your projects. These will enable your agents to send their plan to the signer, so you can approve it. This is awesome: 1. You can have an automated agentic workflow 2. Your agents can't make costly mistakes Check the video I recorded to see how this works. You can run all of this in two commands: 1. Install the CLI 2. Install the skills for your agent From here, the agent can query my Ethereum accounts, check balances, and even initiate transactions as long as my Ledger Nano Gen5 is plugged into the computer. My keys are never stored in my computer and never shared with the agent. This is huge! Also, while the agent can set up transactions, it can't execute them unless a human approves them using the device. Pretty awesome! Thanks to the Ledger team for partnering with me on this post.

This little device lets your agents do what they do best, whilst making sure you approve every important action. This is a Ledger Nano Gen5, a hardware signer that keeps your accounts secure. You can install a CLI and a set of skills in your projects. These will enable your agents to send their plan to the signer, so you can approve it. This is awesome: 1. You can have an automated agentic workflow 2. Your agents can't make costly mistakes Check the video I recorded to see how this works. You can run all of this in two commands: 1. Install the CLI 2. Install the skills for your agent From here, the agent can query my Ethereum accounts, check balances, and even initiate transactions as long as my Ledger Nano Gen5 is plugged into the computer. My keys are never stored in my computer and never shared with the agent. This is huge! Also, while the agent can set up transactions, it can't execute them unless a human approves them using the device. Pretty awesome! Thanks to the Ledger team for partnering with me on this post.

Santiago

44,296 views • 3 months ago

Introducing Hypit: Clone any viral video with AI agents. 1 clone, 100 variants, 100M views. Hypit lets your AI agent (Claude Code, Codex...) clone any viral video. Paste any viral video link from TikTok, Instagram, or YouTube into your agent. Hypit clones it into a complete agentic video workflow: footage, captions, B-roll, effects. GitHub: Key Point: - Arcads: $220 / month - Higgsfield: $129 / month - Creatify: $99 / month - Hypit: FREE 🌟 Build the video creation harness for AI Agents. Redefine how videos are made. Like + comment "Hypit" and I' ll send you 100 free AI avatars, each with its own unique voice. And if you like what we’re building, give Hypit a 🌟 on GitHub.

Introducing Hypit: Clone any viral video with AI agents. 1 clone, 100 variants, 100M views. Hypit lets your AI agent (Claude Code, Codex...) clone any viral video. Paste any viral video link from TikTok, Instagram, or YouTube into your agent. Hypit clones it into a complete agentic video workflow: footage, captions, B-roll, effects. GitHub: Key Point: - Arcads: $220 / month - Higgsfield: $129 / month - Creatify: $99 / month - Hypit: FREE 🌟 Build the video creation harness for AI Agents. Redefine how videos are made. Like + comment "Hypit" and I' ll send you 100 free AI avatars, each with its own unique voice. And if you like what we’re building, give Hypit a 🌟 on GitHub.

Alvin Chen

1,132,316 views • 15 days ago

Google just quietly dropped something big for agent builders It's called SAM: Sovereign Agent Mesh A peer-to-peer network where AI agents auto-discover each other, authenticate every packet and call tools across the mesh without a central server Think of it like BitTorrent, but for your agents Right now every agent stack you build is a walled garden. Claude Code talks to its MCPs. Codex talks to its MCPs. If you want agents running on your laptop, your VPS, and your Mac Studio to share tools with each other, you're duct-taping SSH tunnels and REST endpoints together like it's 2015 SAM makes that whole layer disappear You run a sam-node on each machine and the nodes find each other automatically. Every connection is cryptographically identified, so your agents plug in and start calling tools across the whole network The identity is portable too. Same node, same keys, whether it's on GCP, your laptop, or a Raspberry Pi in your closet If you're serious about running agents across multiple devices, get on the testnet this weekend: 1. Install sam-node (binary or Docker) 2. Point it at 3. Connect Claude or Gemini to your local MCP endpoint 4. Watch your agent discover tools running on other people's nodes Still early. Not officially supported by Google. This is where the agent stack is heading. Get on it early Repo:

Google just quietly dropped something big for agent builders It's called SAM: Sovereign Agent Mesh A peer-to-peer network where AI agents auto-discover each other, authenticate every packet and call tools across the mesh without a central server Think of it like BitTorrent, but for your agents Right now every agent stack you build is a walled garden. Claude Code talks to its MCPs. Codex talks to its MCPs. If you want agents running on your laptop, your VPS, and your Mac Studio to share tools with each other, you're duct-taping SSH tunnels and REST endpoints together like it's 2015 SAM makes that whole layer disappear You run a sam-node on each machine and the nodes find each other automatically. Every connection is cryptographically identified, so your agents plug in and start calling tools across the whole network The identity is portable too. Same node, same keys, whether it's on GCP, your laptop, or a Raspberry Pi in your closet If you're serious about running agents across multiple devices, get on the testnet this weekend: 1. Install sam-node (binary or Docker) 2. Point it at 3. Connect Claude or Gemini to your local MCP endpoint 4. Watch your agent discover tools running on other people's nodes Still early. Not officially supported by Google. This is where the agent stack is heading. Get on it early Repo:

Hasan Toor

42,471 views • 1 month ago

Introducing Magnitude: your actually local agent 100% private and offline. No token costs, no API keys. Open source. Today's agents are local. The model isn't. Every prompt, every file, every secret gets sent straight to Anthropic and OpenAI. Magnitude is built around local models and runs the whole stack itself. The inference engine is part of the agent, so the models run inside it, right on your computer. It lives in your terminal, and setup is one command. Magnitude profiles your hardware and shows you which models fit, with the trade-offs between quality, speed, and memory. Pick one and start working. No painful config or server to babysit. Out of the box, it can use your shell, edit files, and run scripts. Add skills and it can work with Excel, PowerPoint, PDFs or Chrome. Use it for everyday work: - Analyze sensitive data - Manage private notes - Review code and logs - Search and organize files - Build docs or slides npm i -g @magnitudedev/cli GitHub:

Introducing Magnitude: your actually local agent 100% private and offline. No token costs, no API keys. Open source. Today's agents are local. The model isn't. Every prompt, every file, every secret gets sent straight to Anthropic and OpenAI. Magnitude is built around local models and runs the whole stack itself. The inference engine is part of the agent, so the models run inside it, right on your computer. It lives in your terminal, and setup is one command. Magnitude profiles your hardware and shows you which models fit, with the trade-offs between quality, speed, and memory. Pick one and start working. No painful config or server to babysit. Out of the box, it can use your shell, edit files, and run scripts. Add skills and it can work with Excel, PowerPoint, PDFs or Chrome. Use it for everyday work: - Analyze sensitive data - Manage private notes - Review code and logs - Search and organize files - Build docs or slides npm i -g @magnitudedev/cli GitHub:

Tom Greenwald

397,093 views • 1 month ago

Hyperagent is great if you want agents without having to deal with configuration, servers, or any complexity whatsoever. You don't need a Mac Mini or a server. Every agent runs in the cloud, in its own isolated and secure environment. You get: 1. The ability to learn any new API as a skill 2. Browser support 3. Code execution 4. Image and video generation 5. Integration with hundreds of tools Despite the simplicity, I think their best differentiator is the ability for these agents to learn new skills. Basically, you can teach an agent how your company does marketing, and it will never forget your rules and processes. Obviously, it also lets you deploy your agents to Slack with a single click, so everyone can use them. You don't even need to mention them since they will pay attention to chats and act when necessary. I built a simple agent that allows me to translate any message into French. I installed it on Slack, and every time I ping it, it gives me translations. Took me 10 minutes tops.

Hyperagent is great if you want agents without having to deal with configuration, servers, or any complexity whatsoever. You don't need a Mac Mini or a server. Every agent runs in the cloud, in its own isolated and secure environment. You get: 1. The ability to learn any new API as a skill 2. Browser support 3. Code execution 4. Image and video generation 5. Integration with hundreds of tools Despite the simplicity, I think their best differentiator is the ability for these agents to learn new skills. Basically, you can teach an agent how your company does marketing, and it will never forget your rules and processes. Obviously, it also lets you deploy your agents to Slack with a single click, so everyone can use them. You don't even need to mention them since they will pay attention to chats and act when necessary. I built a simple agent that allows me to translate any message into French. I installed it on Slack, and every time I ping it, it gives me translations. Took me 10 minutes tops.

Santiago

213,793 views • 2 months ago

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,758 views • 1 year ago

The guy who vibe-coded his own food discovery app just dropped 4 solid security basics. If you're building your own app with AI, you need this so you don't get hacked on day one: 1. Hide your API keys Keep your OpenAI or Stripe keys off the frontend to prevent them from being stolen. Tell Claude: "Move all API keys to the server and use environment variables." 2. Input Validation Stop people from pasting malicious code into your search bars to break your database. Tell Claude Code: "Sanitize all user inputs." 3. Don't invent your own auth Building login systems from scratch is too risky. Use trusted platforms instead. Tell Claude Code: "Integrate Supabase for authentication." 4. Rate limiting Prevent trolls from crashing your server with 10,000 requests per minute. Tell Claude Code: "Add rate limiting to my API routes." Too many people vibe-coding right now make these exact mistakes and wake up to drained API budgets or wiped databases. Get the security right first. Once your foundation is solid, you can build literally anything. A friend of mine just shared a crazy guide on how to build an entire social network like X in a certain niche with Claude Code in 4 weeks. check it out below 👇

The guy who vibe-coded his own food discovery app just dropped 4 solid security basics. If you're building your own app with AI, you need this so you don't get hacked on day one: 1. Hide your API keys Keep your OpenAI or Stripe keys off the frontend to prevent them from being stolen. Tell Claude: "Move all API keys to the server and use environment variables." 2. Input Validation Stop people from pasting malicious code into your search bars to break your database. Tell Claude Code: "Sanitize all user inputs." 3. Don't invent your own auth Building login systems from scratch is too risky. Use trusted platforms instead. Tell Claude Code: "Integrate Supabase for authentication." 4. Rate limiting Prevent trolls from crashing your server with 10,000 requests per minute. Tell Claude Code: "Add rate limiting to my API routes." Too many people vibe-coding right now make these exact mistakes and wake up to drained API budgets or wiped databases. Get the security right first. Once your foundation is solid, you can build literally anything. A friend of mine just shared a crazy guide on how to build an entire social network like X in a certain niche with Claude Code in 4 weeks. check it out below 👇

Spivach

11,103 views • 3 months ago

voice prompting is 4x faster than typing. but i NEEEDED more. Nvidia parakeet allows me to fully voice control an agentic development environment with commands firing in under 300ms. and it runs 100% local. I added gpt realtime 2.1 mini, its 20% faster, 7 to 20x cheaper, and lets you have full jarvis style control of your vibe coding agents. but what about orchestration? agents can spawn each other, prompt each other, and read each others output with the CNVS mcp and cli. Fable 5 can create a plan, spawn 10 grok agents to execute, and a kimi k3 agent to review. parallel agents code at 1,000s of TPS anthropic's own research shows improvements ACROSS the board for multi agent workflows over single agent but only CNVS lets you choose exactly which orchestration, worker, and reviewer agent you would like to use. grok, kimi, qwen, claude, codex... the cross agent memory system is based on real 2026 research so all agents share the same brain, its on demand so it never bloats context. what about remote agents?? You can create remote canvasses that run agents your virtual private servers, they keep working even if your mac shuts off, and you can even vibe code straight to production. CNVS is built from the ground up ENTIRELY in swift for RAW performance on apple hardware. PS - its a LIFE TIME LICENSE because you don't need another subscription. PPS - I ship updates every week based off user feedback and livestream myself building it everyday. PPPS - it uses all your existing ai subs, so no api pricing here.

voice prompting is 4x faster than typing. but i NEEEDED more. Nvidia parakeet allows me to fully voice control an agentic development environment with commands firing in under 300ms. and it runs 100% local. I added gpt realtime 2.1 mini, its 20% faster, 7 to 20x cheaper, and lets you have full jarvis style control of your vibe coding agents. but what about orchestration? agents can spawn each other, prompt each other, and read each others output with the CNVS mcp and cli. Fable 5 can create a plan, spawn 10 grok agents to execute, and a kimi k3 agent to review. parallel agents code at 1,000s of TPS anthropic's own research shows improvements ACROSS the board for multi agent workflows over single agent but only CNVS lets you choose exactly which orchestration, worker, and reviewer agent you would like to use. grok, kimi, qwen, claude, codex... the cross agent memory system is based on real 2026 research so all agents share the same brain, its on demand so it never bloats context. what about remote agents?? You can create remote canvasses that run agents your virtual private servers, they keep working even if your mac shuts off, and you can even vibe code straight to production. CNVS is built from the ground up ENTIRELY in swift for RAW performance on apple hardware. PS - its a LIFE TIME LICENSE because you don't need another subscription. PPS - I ship updates every week based off user feedback and livestream myself building it everyday. PPPS - it uses all your existing ai subs, so no api pricing here.

Max Blade

60,973 views • 2 months ago

Anthropic's in trouble, again. The entire Claude experience is now available at 1/6th the price. Kimi now does everything Claude does, powered by K2.6, a 1-trillion-parameter MoE model that activates only 32B parameters per token. It covers all three features Claude has (Chat, Code, and Cowork): 1) Kimi Chat runs in four modes - Instant for fast responses - Thinking for deep reasoning - Agent for multi-step execution - and Agent Swarm for parallel workloads. There's a 262K context window across all of them. 2) Kimi Code is the open-source CLI coding agent with K2.6 as the default backend. K2.6 ranked #1 on OpenRouter's programming leaderboard by weekly usage. 3) Kimi Agent is the Cowork equivalent. It generates: - full websites with database and auth - presentation decks (editable PPTX output) - spreadsheets with formulas and charts - word docs and structured research reports. On top of this, Kimi K2.6 is also trained to decompose tasks into up to 300 parallel sub-agents. This helps it retain coherence even across 4,000+ tool calls in a single run, with sessions sustaining up to 13 hours. On SWE-Bench Pro: - Kimi K2.6 → 58.6 - GPT-5.4 xhigh → 57.7 - Gemini 3.1 Pro → 54.2 - Claude Opus 4.6 → 53.4 Kimi K2.6 model is open weights and self-hostable on 4x H100s in INT4. Find the link to the HuggingFace model page in the replies!

Anthropic's in trouble, again. The entire Claude experience is now available at 1/6th the price. Kimi now does everything Claude does, powered by K2.6, a 1-trillion-parameter MoE model that activates only 32B parameters per token. It covers all three features Claude has (Chat, Code, and Cowork): 1) Kimi Chat runs in four modes - Instant for fast responses - Thinking for deep reasoning - Agent for multi-step execution - and Agent Swarm for parallel workloads. There's a 262K context window across all of them. 2) Kimi Code is the open-source CLI coding agent with K2.6 as the default backend. K2.6 ranked #1 on OpenRouter's programming leaderboard by weekly usage. 3) Kimi Agent is the Cowork equivalent. It generates: - full websites with database and auth - presentation decks (editable PPTX output) - spreadsheets with formulas and charts - word docs and structured research reports. On top of this, Kimi K2.6 is also trained to decompose tasks into up to 300 parallel sub-agents. This helps it retain coherence even across 4,000+ tool calls in a single run, with sessions sustaining up to 13 hours. On SWE-Bench Pro: - Kimi K2.6 → 58.6 - GPT-5.4 xhigh → 57.7 - Gemini 3.1 Pro → 54.2 - Claude Opus 4.6 → 53.4 Kimi K2.6 model is open weights and self-hostable on 4x H100s in INT4. Find the link to the HuggingFace model page in the replies!

Avi Chawla

110,057 views • 4 months ago

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

Yarchi

54,840 views • 3 months ago

A guy on Reddit got so fed up with scrolling LinkedIn for internships that he built his own job search engine with Claude Code. The tool is called Pinloop. It's an open-source CLI, and he built it with Claude Code too. Here's how it works: → It pulls millions of postings a month, worldwide, straight from hiring systems like Greenhouse and Workday (50+ of them) plus job boards like LinkedIn, refreshed hourly → It stores your resume and preferences → Every day, Claude Code pulls the new postings, reads each one against your profile, and writes a verdict with its reasoning → The good fits land in a shortlist you check in the morning His reasoning: every application already gets screened by AI on the employer's side, so he built a screener for his own side. You don't even have to set it up yourself. Paste this into Claude Code, Codex, or Cursor: "Run npm install -g pinloop, then run pinloop welcome and follow the instructions"

Vaibhav Sisinty

18,719 views • 6 days ago

Today I'm excited to share Sigilum! This is Payman's solution for Auditable Identity for AI Agents. (think One Password-ish but for AI Agents) I recorded a quick walkthrough showing how it all works (video below). This answers three pains we've seen within Financial Services (Banking) AI Agents we've built and OpenClaw🦞 AI Agents we deploy. Security, Auditability, and Control. 1. Security Making sure keys are secure and not just freely given to an AI Agent is a big deal. When working with money, you can't just expose these or skip putting controls in place. Sigilum provides a local gateway that prevents access to keys by the AI Agent without explicit authorization from a person. We provide namespaces through the service so you always know who authorized what key, for what service, to which agent. 2. Auditability If I could hit on the importance of this 100 times I would. It comes up in every financial services conversation. Sigilum provides you with the answer to "Who authorized this AI Agent to act on my behalf?" Audit logs trace back to the person, the service, and the AI Agent. With more audit logs being built through our managed service, this will be the key source for determining how an AI Agent is behaving on your behalf. This is needed for agents from OpenClaw, and especially for banking/money movement. 3. Control Revoke keys, limit access, grant authorization. All seemingly simple things, but complex to implement and make elegant. These controls dictate what the AI Agent can or cannot do. Sigilum allows you to do all of this through the managed Dashboard. We've made Sigilum open source and encourage others to contribute and keep building on the gateway. It's been a source of a lot of visibility and productization of AI Agents for us. We'll keep contributing and adding to it. Link in comments. If you want to try it out, we do have a managed service that makes it easy to spin up. Go to to sign up. Note: even though we've been pushing 100+ commits a day to get this out to folks, there are still some noticeable areas for improvement we're working on, which should get resolved soon (by us or you!): - Deeper audit trails - More providers (currently supports all OpenClaw providers) - Deeper scanning of existing keys your agent is hiding from you (we'll find them) - OpenClaw gateway persistence - Auto-purging keys - And more... If you want to contribute or have feedback, please DM or go to the GH. Happy building!

Today I'm excited to share Sigilum! This is Payman's solution for Auditable Identity for AI Agents. (think One Password-ish but for AI Agents) I recorded a quick walkthrough showing how it all works (video below). This answers three pains we've seen within Financial Services (Banking) AI Agents we've built and OpenClaw🦞 AI Agents we deploy. Security, Auditability, and Control. 1. Security Making sure keys are secure and not just freely given to an AI Agent is a big deal. When working with money, you can't just expose these or skip putting controls in place. Sigilum provides a local gateway that prevents access to keys by the AI Agent without explicit authorization from a person. We provide namespaces through the service so you always know who authorized what key, for what service, to which agent. 2. Auditability If I could hit on the importance of this 100 times I would. It comes up in every financial services conversation. Sigilum provides you with the answer to "Who authorized this AI Agent to act on my behalf?" Audit logs trace back to the person, the service, and the AI Agent. With more audit logs being built through our managed service, this will be the key source for determining how an AI Agent is behaving on your behalf. This is needed for agents from OpenClaw, and especially for banking/money movement. 3. Control Revoke keys, limit access, grant authorization. All seemingly simple things, but complex to implement and make elegant. These controls dictate what the AI Agent can or cannot do. Sigilum allows you to do all of this through the managed Dashboard. We've made Sigilum open source and encourage others to contribute and keep building on the gateway. It's been a source of a lot of visibility and productization of AI Agents for us. We'll keep contributing and adding to it. Link in comments. If you want to try it out, we do have a managed service that makes it easy to spin up. Go to to sign up. Note: even though we've been pushing 100+ commits a day to get this out to folks, there are still some noticeable areas for improvement we're working on, which should get resolved soon (by us or you!): - Deeper audit trails - More providers (currently supports all OpenClaw providers) - Deeper scanning of existing keys your agent is hiding from you (we'll find them) - OpenClaw gateway persistence - Auto-purging keys - And more... If you want to contribute or have feedback, please DM or go to the GH. Happy building!

tyllen

18,497 views • 7 months ago