Loading video...

Video Failed to Load

Go Home

Data encryption is now live on Veilnet. Available in @veilnet/[email protected]. Any blob — file, dataset, config, recovery codes, contract draft, research note, agent memory — can now be encrypted on your device, shipped to Veilnet as ciphertext, and fetched back later without the decryption key ever leaving your machine....

Veilnet_'s profile picture

Veilnet

1,176 subscribers

11,761 views • 2 months 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

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇
2:24

We’re excited to launch OpenMemory MCP, a private memory for MCP-compatible clients powered by mem0 Today, most AI assistants and dev tools operate without memory. You plan your roadmap in Claude, implement tasks in Cursor, but none of them know what the other did. Each tool operates in isolation, and your context disappears as soon as the session ends. OpenMemory MCP solves this. Built on the open Model Context Protocol (MCP), OpenMemory MCP runs 100% locally and provides a persistent, portable memory layer for all your AI tools. It enables agents and assistants to read from and write to a shared memory, securely and privately. Key capabilities: ✅Works across MCP clients like Cursor, Claude Desktop, Windsurf, Cline and more ✅Provides standardized memory operations (add_memories, search_memory, list_memories, delete_all_memories) ✅Stores data on your machine, fully private ✅Offers a centralized dashboard for visibility and control ✅Simple Docker-based setup with no vendor lock-in If you're building on MCP, OpenMemory MCP is the easiest way to add persistent, private memory to your clients with zero cloud dependencies and full local control. We’ve put together a short demo to show how it works Check it out in the links below 👇

Taranjeet

471,972 views • 1 year ago

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:
3:08

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:

Spenser Skates

32,332 views • 9 months ago

🔮 MCP INTEGRATION NOW LIVE ON OPENSERV This is bigger than most realize. We're not just adding a feature - we're enabling a fundamentally new paradigm for agent infrastructure. Before MCP: agents trapped in walled gardens, limited by what you explicitly feed them. After MCP: agents that can access 10K+ tools, interact with your existing systems, and truly operate in your digital world. Think about this: -Every integration used to require custom code -Every data source needed specific formatting -Every agent had to be built for specific tools MCP eliminates all of that. One standard to connect any agent to any tool. This isn't just convenience - it's the unlock that makes agents actually useful in the real world. OpenServ + MCP = AI teams that can genuinely get things done, not just talk about doing them. This is the breakthrough that turns agents from toys into tools.
0:22

🔮 MCP INTEGRATION NOW LIVE ON OPENSERV This is bigger than most realize. We're not just adding a feature - we're enabling a fundamentally new paradigm for agent infrastructure. Before MCP: agents trapped in walled gardens, limited by what you explicitly feed them. After MCP: agents that can access 10K+ tools, interact with your existing systems, and truly operate in your digital world. Think about this: -Every integration used to require custom code -Every data source needed specific formatting -Every agent had to be built for specific tools MCP eliminates all of that. One standard to connect any agent to any tool. This isn't just convenience - it's the unlock that makes agents actually useful in the real world. OpenServ + MCP = AI teams that can genuinely get things done, not just talk about doing them. This is the breakthrough that turns agents from toys into tools.

OpenServ

34,665 views • 1 year ago

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!
2:43

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

Andrew Ng

142,010 views • 1 year ago

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.
0:46

Everyone's building AI agents that run on someone else's server, store memory in someone else's database, and can be shut down by someone else's terms of service. I built one that can't be. FlowClaw is an AI agent that runs on a decentralized distributed computer. Your agent, your conversations, your memory, your tools — all stored onchain on Flow, a distributed network of validator nodes across the world. Not a centralized cloud. Not someone's S3 bucket. A blockchain that functions as censorship-resistant compute and storage for your AI. This isn't a wrapper. Your agent is a Resource — a first-class programmable object in Cadence (Flow's smart contract language) that physically lives in your account's on-chain storage. It can't be duplicated, seized, or deleted by anyone except you. Your encrypted messages, your cognitive memory, your scheduled tasks — they persist on a global distributed ledger that no single entity controls. It's an alpha build. It will break. But it works today on mainnet and I want people to push it this weekend. What it does: You go to authenticate with a passkey (Face ID, Touch ID), and you have a blockchain account in seconds. No wallet. No seed phrase. No tokens needed — gas is sponsored. You're immediately chatting with an AI agent that has real tool execution: live web data, token prices, on-chain balances, Cadence script execution, FLOW transfers. Every message is encrypted client-side before it touches the chain. The agent has a cognitive memory system — it doesn't just remember your last message, it builds molecular memory clusters where related knowledge bonds together for contextual retrieval across sessions. You can spawn sub-agents from a visual canvas to run parallel research. The memory tab shows you exactly what your agent knows. Everything is transparent and everything is yours. 11 smart contracts. No external dependencies. No keeper networks. No account abstraction hacks. Here's the part that matters for the censorship-resistance crowd: FlowClaw supports BYOK — bring your own key. You can plug in any LLM provider. But pair it with Venice and you get the full stack: a censorship-resistant AI model running inference with no content filtering, connected to an agent whose state lives on a decentralized network that no company can shut down, with end-to-end encrypted conversations that nobody can read — not the relay operator, not the LLM provider, not the blockchain validators. Venice doesn't log prompts. Flow can't read your encrypted storage. The relay never sees your plaintext. That's not a privacy policy. That's architecture. You can also use OpenAI, Anthropic, or any OpenAI-compatible provider. The agent platform doesn't care — it's model-agnostic. But the Venice pairing is the one that closes every gap in the stack. For the people tinkering with OpenClaw and the broader open-source agent ecosystem — FlowClaw is exploring what happens when you take the agent off the cloud entirely. Not just open-sourcing the code (though it is), but putting the actual runtime state on a distributed computer. Your agent's memory isn't in a SQLite file on your laptop or a Pinecone index on someone's cluster. It's on-chain, encrypted, and replicated across every validator node on Flow. You own it the way you own a private key — mathematically, not contractually. The blockchain here isn't a gimmick bolted onto an agent for token speculation. It's functioning as the infrastructure layer that replaces AWS. Flow accounts are programmable containers with their own storage, keys, and security capabilities. Passkey authentication works natively because Flow supports P-256 keys at the protocol level — the same curve your phone uses for biometrics. Gas sponsorship works natively because Flow transactions have separate proposer, authorizer, and payer roles built into the protocol. No proxy contracts. No relayers. No ERC-4337. Now here's the part that interests me economically. Every FlowClaw interaction is an on-chain transaction. Every message stored, every memory committed, every session created, every sub-agent spawned. An active user might generate dozens of transactions in a single conversation. Scale that and FlowClaw becomes a real contributor to Flow's transaction volume. Flow.com becomes deflationary at 250 TPS. Applications like FlowClaw that generate high-frequency, storage-heavy transactions are exactly what moves the needle. Every encrypted message uses account storage, which requires FLOW balance to back it. Every transaction burns fees. The more agents running, the more demand for $FLOW — not because of a tokenomics gimmick, but because the protocol literally requires it for compute and storage. FlowClaw doesn't have its own token. The token is $FLOW. The entire platform runs natively on the network — using Flow storage, paying Flow transaction fees, backed by Flow account balances. If FlowClaw succeeds, FLOW captures that value directly. I'm sharing this early because the AI agent space is moving fast and I think the decentralized infrastructure angle is underexplored. Most "crypto AI" projects are tokens with a chatbot attached. FlowClaw is the opposite — it's an agent platform that happens to use a blockchain because the blockchain solves real engineering problems that centralized infrastructure can't. Try it: Github: Create an agent, ask it something, spawn a sub-agent, check your memory tab, pair it with Venice for the full censorship-resistant stack. Break it and tell me what broke. If you think this direction matters, the best thing you can do is use it and give feedback. Your AI agent should be yours. Not your provider's. Not your platform's. Yours.

doodlifts

12,172 views • 5 months ago

OpenClaw Now Lives on Solana — Free AI Agents in Your Pocket We've integrated .molt domains with OpenClaw, bringing personal AI agents to the Solana ecosystem. Each .molt domain is a Metaplex Core NFT that unlocks your own AI agent instance. What you get: Wallet-based access — No accounts, no passwords. Connect your Solana wallet, prove NFT ownership, instant access Per-domain agents — Each domain NFT gets its own isolated AI agent with persistent memory Configure your channels — Set up Telegram, Discord, or Slack bots directly from the UI. Enter your bot token, click save, restart your agent Persistent storage — Your agent's memory and conversations persist in R2 storage, tied to your NFT The best part? It's free. You don't need a $600 MacBook. You don't need a $15/month VPS. You don't need to manage servers, Docker containers, or API keys. Just mint a .molt domain, connect your wallet, and you have OpenClaw in your pocket — accessible from any device, anywhere. Your domain. Your agent. Your data. All on-chain, all yours. Live on devnet:
2:06

OpenClaw Now Lives on Solana — Free AI Agents in Your Pocket We've integrated .molt domains with OpenClaw, bringing personal AI agents to the Solana ecosystem. Each .molt domain is a Metaplex Core NFT that unlocks your own AI agent instance. What you get: Wallet-based access — No accounts, no passwords. Connect your Solana wallet, prove NFT ownership, instant access Per-domain agents — Each domain NFT gets its own isolated AI agent with persistent memory Configure your channels — Set up Telegram, Discord, or Slack bots directly from the UI. Enter your bot token, click save, restart your agent Persistent storage — Your agent's memory and conversations persist in R2 storage, tied to your NFT The best part? It's free. You don't need a $600 MacBook. You don't need a $15/month VPS. You don't need to manage servers, Docker containers, or API keys. Just mint a .molt domain, connect your wallet, and you have OpenClaw in your pocket — accessible from any device, anywhere. Your domain. Your agent. Your data. All on-chain, all yours. Live on devnet:

Molt.id

314,996 views • 6 months ago

🚀Exciting News: The Lit Agent Wallet is Now an elizaOS Plugin! 🚀 We’re thrilled to share that the Lit Agent Wallet—a decentralized system that empowers agents with a private key stored securely across an MPC + TEE network (Lit)—is now available as a plugin for ElizaOS!🎉 This integration brings unparalleled flexibility and security to your decentralized workflows. Whether you're an EOA, a smart account, or a DAO, you can now set tools and policies on-chain that your agents can use, all while ensuring your private keys remain secure and decentralized. 🔒 What Does This Mean for You? >Enhanced Security: Private keys are fragmented and stored across the Lit network, leveraging MPC (Multi-Party Computation) and TEE (Trusted Execution Environment) for maximum security. >On-Chain Control: Set and manage tools, policies, and permissions directly on-chain, giving users and DAOs full control over what your agents can do. >Seamless Integration: As an ElizaOS plugin, the Lit Agent Wallet is now easier than ever to integrate into your existing workflows. Check out the video for a walk through of the setup, configuration, and use cases of the Lit Agent Wallet within ElizaOS. We’ll show you just how easy it is to get started and unlock the full potential of decentralized agents. Get Started Today! Ready to take your agent operations to the next level? Install the Lit Agent Wallet plugin on ElizaOS and experience the future of secure, on-chain agent asset management. 🔗 🔗 Let’s build a more intelligent and decentralized future together! 🌐
3:42

🚀Exciting News: The Lit Agent Wallet is Now an elizaOS Plugin! 🚀 We’re thrilled to share that the Lit Agent Wallet—a decentralized system that empowers agents with a private key stored securely across an MPC + TEE network (Lit)—is now available as a plugin for ElizaOS!🎉 This integration brings unparalleled flexibility and security to your decentralized workflows. Whether you're an EOA, a smart account, or a DAO, you can now set tools and policies on-chain that your agents can use, all while ensuring your private keys remain secure and decentralized. 🔒 What Does This Mean for You? >Enhanced Security: Private keys are fragmented and stored across the Lit network, leveraging MPC (Multi-Party Computation) and TEE (Trusted Execution Environment) for maximum security. >On-Chain Control: Set and manage tools, policies, and permissions directly on-chain, giving users and DAOs full control over what your agents can do. >Seamless Integration: As an ElizaOS plugin, the Lit Agent Wallet is now easier than ever to integrate into your existing workflows. Check out the video for a walk through of the setup, configuration, and use cases of the Lit Agent Wallet within ElizaOS. We’ll show you just how easy it is to get started and unlock the full potential of decentralized agents. Get Started Today! Ready to take your agent operations to the next level? Install the Lit Agent Wallet plugin on ElizaOS and experience the future of secure, on-chain agent asset management. 🔗 🔗 Let’s build a more intelligent and decentralized future together! 🌐

Lit Protocol 🔑

41,989 views • 1 year ago

🤯 Building computer-vision applications is never going to be the same again. As Andrej Karpathy says, "English is going to be the new programming-language", and we just made that happen for programming visual AI. 👨‍💻 This past month, the VLM Run team cooked up something magical that I'm especially proud of - a natural-language interface to build and run computer vision workflows (object-detection, OCR, parsing, and so much more) – all via our new VLM Run MCP server. 🔌 It works with any MCP-compatible AI agent (Claude, OpenAI, Cursor, etc.) and abstracts complex visual workflows into simple English commands. No need to write Python or fiddle with bespoke computer-vision code – just say what you want your agent to do, and it does it. Here’s a glimpse into what you can build today ( ☑️ Image AI agents – run detection, tagging, blurring, cropping, and more traditional CV tasks with English ☑️ Document AI agents – extract totals from invoices, search visual content, or act on what’s found ☑️ Video AI agents – understand scene content, trim clips, add subtitles, and create ready-to-share edits ☑️ And best-of-all, it's fully programmable with English. 🧑‍🍳 MCP Showcase: 📚 MCP Cookbooks: 📚 MCP Docs: #computervision #ai #agents #llm #vlm #mcp #vibecoding #genai
1:49

🤯 Building computer-vision applications is never going to be the same again. As Andrej Karpathy says, "English is going to be the new programming-language", and we just made that happen for programming visual AI. 👨‍💻 This past month, the VLM Run team cooked up something magical that I'm especially proud of - a natural-language interface to build and run computer vision workflows (object-detection, OCR, parsing, and so much more) – all via our new VLM Run MCP server. 🔌 It works with any MCP-compatible AI agent (Claude, OpenAI, Cursor, etc.) and abstracts complex visual workflows into simple English commands. No need to write Python or fiddle with bespoke computer-vision code – just say what you want your agent to do, and it does it. Here’s a glimpse into what you can build today ( ☑️ Image AI agents – run detection, tagging, blurring, cropping, and more traditional CV tasks with English ☑️ Document AI agents – extract totals from invoices, search visual content, or act on what’s found ☑️ Video AI agents – understand scene content, trim clips, add subtitles, and create ready-to-share edits ☑️ And best-of-all, it's fully programmable with English. 🧑‍🍳 MCP Showcase: 📚 MCP Cookbooks: 📚 MCP Docs: #computervision #ai #agents #llm #vlm #mcp #vibecoding #genai

Sudeep Pillai

17,789 views • 1 year ago

ZKForge V1 is now live and the source code is public on GitHub: Visit: Users can sign up, log in, and chat privately using zero-knowledge authentication (ZK-STARK) with full end-to-end encryption and non-custodial wallet integration. No passwords, no stored private keys, all encryption and identity verification happen locally on the user’s device. Core Features • Zero-Knowledge Authentication (ZKAuth) Users sign up and log in using a locally generated Ed25519 keypair. Authentication uses zero-knowledge proofs (ZK-STARK-compatible), proving identity ownership without revealing the secret key. The backend never sees or stores private keys , only the derived public key and Solana address. • End-to-End Chat Encryption Every conversation is encrypted with per-room symmetric keys (nacl.secretbox AES-grade security). Keys are sealed and exchanged using ephemeral Curve25519 boxes derived from each user’s Ed25519 keypair. Messages are signed for sender authenticity. The server cannot decrypt messages; all encryption happens client-side. • Global Lounge (Public Encrypted Room) Encrypted public discussion room using a temporary shared key. Messages self-destruct after a defined time window. Rate-limit and anti-spam protections are enforced through Supabase RLS policies. • Wallet Integration (Non-Custodial) Each user derives a Solana wallet from their zero-knowledge secret. Private keys are generated and stored locally, never sent to the backend. Supports in-app USDC transactions signed locally. • WebSocket-Based Real-Time Updates Secure WebSocket channel for live message delivery, typing indicators, and presence tracking. Each message includes cryptographic nonce, ciphertext, and signature validation before render. Architecture Overview Frontend (React + Tailwind): Encryption, proof generation, local key storage, message rendering. Backend (Express + Supabase): Stateless API for sessions, rate limits, and metadata. Crypto Layer (tweetnacl, ed2curve, bs58): Signing, sealing, encryption primitives. Database (Supabase PostgreSQL): Stores ciphertext and public keys only. Realtime (WebSocket): Delivers encrypted payloads instantly. Key Design Principles Zero Storage of Private Keys All signing keys exist only in the user’s local storage. Provable Authentication Login requests include cryptographic proofs verified without revealing secrets. Encrypted-At-Rest and In-Transit All messages are encrypted before leaving the device. Verifiable Sender Identity Each message includes a detached Ed25519 signature verifying authorship. Tech Stack Frontend: React, TailwindCSS, TypeScript, Vite Backend: Node.js (Express), Supabase, MongoDB Cryptography: TweetNaCl, ed2curve, bs58, genSTARK Blockchain: Solana Web3.js Realtime: WebSockets Security: Row-Level Security, JWT Sessions, Proof Verification What’s next x402 protocol implementation
1:01

ZKForge V1 is now live and the source code is public on GitHub: Visit: Users can sign up, log in, and chat privately using zero-knowledge authentication (ZK-STARK) with full end-to-end encryption and non-custodial wallet integration. No passwords, no stored private keys, all encryption and identity verification happen locally on the user’s device. Core Features • Zero-Knowledge Authentication (ZKAuth) Users sign up and log in using a locally generated Ed25519 keypair. Authentication uses zero-knowledge proofs (ZK-STARK-compatible), proving identity ownership without revealing the secret key. The backend never sees or stores private keys , only the derived public key and Solana address. • End-to-End Chat Encryption Every conversation is encrypted with per-room symmetric keys (nacl.secretbox AES-grade security). Keys are sealed and exchanged using ephemeral Curve25519 boxes derived from each user’s Ed25519 keypair. Messages are signed for sender authenticity. The server cannot decrypt messages; all encryption happens client-side. • Global Lounge (Public Encrypted Room) Encrypted public discussion room using a temporary shared key. Messages self-destruct after a defined time window. Rate-limit and anti-spam protections are enforced through Supabase RLS policies. • Wallet Integration (Non-Custodial) Each user derives a Solana wallet from their zero-knowledge secret. Private keys are generated and stored locally, never sent to the backend. Supports in-app USDC transactions signed locally. • WebSocket-Based Real-Time Updates Secure WebSocket channel for live message delivery, typing indicators, and presence tracking. Each message includes cryptographic nonce, ciphertext, and signature validation before render. Architecture Overview Frontend (React + Tailwind): Encryption, proof generation, local key storage, message rendering. Backend (Express + Supabase): Stateless API for sessions, rate limits, and metadata. Crypto Layer (tweetnacl, ed2curve, bs58): Signing, sealing, encryption primitives. Database (Supabase PostgreSQL): Stores ciphertext and public keys only. Realtime (WebSocket): Delivers encrypted payloads instantly. Key Design Principles Zero Storage of Private Keys All signing keys exist only in the user’s local storage. Provable Authentication Login requests include cryptographic proofs verified without revealing secrets. Encrypted-At-Rest and In-Transit All messages are encrypted before leaving the device. Verifiable Sender Identity Each message includes a detached Ed25519 signature verifying authorship. Tech Stack Frontend: React, TailwindCSS, TypeScript, Vite Backend: Node.js (Express), Supabase, MongoDB Cryptography: TweetNaCl, ed2curve, bs58, genSTARK Blockchain: Solana Web3.js Realtime: WebSockets Security: Row-Level Security, JWT Sessions, Proof Verification What’s next x402 protocol implementation

ZKForge

24,207 views • 9 months ago

Google open-sourced MCP Toolbox for Databases. I gave it access to everything else. For context, Google's MCP Toolbox for Databases is an open-source server that lets AI agents securely query structured databases like PostgreSQL and MySQL through the MCP protocol However, most enterprise knowledge doesn't actually live in databases. It's scattered across emails, Slack threads, GitHub repos, Salesforce records, customer reviews, and internal docs. So Agents can't see any of it, which means they're working with a fraction of the context they need. I fixed that using MindsDB. It acts as a universal SQL layer that sits on top of all your data sources: structured, semi-structured, and unstructured. This means you can query Salesforce, Gmail, GitHub, S3 files, Jira, and 200+ more sources using SQL syntax. The clever part is how it connects to the MCP Toolbox. MindsDB exposes everything through MySQL, so from the Agent's perspective, it's just running SQL and getting context back. It doesn't know or care that the data came from five different sources behind the scenes. This setup unlocks some powerful capabilities: → One SQL interface for dozens of enterprise sources → Cross-datasource joins (combine GitHub and CRM data in a single query) → Built-in ML capabilities for working with unstructured data → Simple MCP tools that now have massively expanded reach In the video below, the Agent queries GitHub data and a customer review database in one SQL query. So what used to require ETL pipelines and weeks of engineering effort now happens instantly. At the end of the day, AI agents are only as useful as the data they can access. This gives them a lot more to work with. I have shared the GitHub repo in the replies, where you can find more details about this.
0:22

Google open-sourced MCP Toolbox for Databases. I gave it access to everything else. For context, Google's MCP Toolbox for Databases is an open-source server that lets AI agents securely query structured databases like PostgreSQL and MySQL through the MCP protocol However, most enterprise knowledge doesn't actually live in databases. It's scattered across emails, Slack threads, GitHub repos, Salesforce records, customer reviews, and internal docs. So Agents can't see any of it, which means they're working with a fraction of the context they need. I fixed that using MindsDB. It acts as a universal SQL layer that sits on top of all your data sources: structured, semi-structured, and unstructured. This means you can query Salesforce, Gmail, GitHub, S3 files, Jira, and 200+ more sources using SQL syntax. The clever part is how it connects to the MCP Toolbox. MindsDB exposes everything through MySQL, so from the Agent's perspective, it's just running SQL and getting context back. It doesn't know or care that the data came from five different sources behind the scenes. This setup unlocks some powerful capabilities: → One SQL interface for dozens of enterprise sources → Cross-datasource joins (combine GitHub and CRM data in a single query) → Built-in ML capabilities for working with unstructured data → Simple MCP tools that now have massively expanded reach In the video below, the Agent queries GitHub data and a customer review database in one SQL query. So what used to require ETL pipelines and weeks of engineering effort now happens instantly. At the end of the day, AI agents are only as useful as the data they can access. This gives them a lot more to work with. I have shared the GitHub repo in the replies, where you can find more details about this.

Akshay 🚀

39,331 views • 5 months ago

Base just launched something that changes how AI agents interact with blockchain. It's called Base MCP. Here's what it actually does 🧵 Base MCP is an open-source MCP server built by Coinbase for the Base network. It connects AI clients, Claude, ChatGPT, to Base Network. You type a natural language prompt. The agent prepares the transaction. You approve it. Done. Your keys never touch the server. Nothing moves on-chain without your explicit sign-off. you can use it to Track portfolio balances across Base and any Base Account supported EVM chain. View transaction history. Send funds Swap tokens Use supported apps and protocols on Base through skill plugins Pay for x402 enabled services To test it, I connected it to BlockLottery, an on-chain lottery protocol with NFT tickets and VRF-powered draws. Two questions to the agent: → "What lotteries are open right now?" Queried the factory contract. Matched the partner dashboard exactly. → "Check this wallet's portfolio." Scanned the chain, handled RPC limits, returned a clean breakdown. Spot on. This is what crypto-native AI tooling looks like. Not hype. An actual working MCP server, launched May 26, 2026. Base MCP docs: BlockLottery: Base Build Base #blockchain #AI #Web3
2:40

Base just launched something that changes how AI agents interact with blockchain. It's called Base MCP. Here's what it actually does 🧵 Base MCP is an open-source MCP server built by Coinbase for the Base network. It connects AI clients, Claude, ChatGPT, to Base Network. You type a natural language prompt. The agent prepares the transaction. You approve it. Done. Your keys never touch the server. Nothing moves on-chain without your explicit sign-off. you can use it to Track portfolio balances across Base and any Base Account supported EVM chain. View transaction history. Send funds Swap tokens Use supported apps and protocols on Base through skill plugins Pay for x402 enabled services To test it, I connected it to BlockLottery, an on-chain lottery protocol with NFT tickets and VRF-powered draws. Two questions to the agent: → "What lotteries are open right now?" Queried the factory contract. Matched the partner dashboard exactly. → "Check this wallet's portfolio." Scanned the chain, handled RPC limits, returned a clean breakdown. Spot on. This is what crypto-native AI tooling looks like. Not hype. An actual working MCP server, launched May 26, 2026. Base MCP docs: BlockLottery: Base Build Base #blockchain #AI #Web3

BlockLottery

11,612 views • 2 months ago

Big moment for Postgres! AI agents broke the idea of what a database is supposed to do. Traditional databases were built for humans, and Agents broke that model. - They branch endlessly. - They run ten experiments at once. - They need isolation, context, memory, structured reasoning, and safe sandboxes. Letting agents touch production systems is terrifying because the old model of Postgres was never built for this kind of behavior. Agentic Postgres is an agent-ready version of Postgres by TimescaleDB (by Tiger Data) that solves this. I think it is one of the biggest upgrades to the Agent stack this year and Tiger Data is working with me on this post to share what they did. Some key features: > It instantly creates branches of an entire database, which is perfect for parallel agent evals, safe experiments, migrations, or isolated testing. Forks take seconds and cost almost nothing. > It comes with a built-in MCP server, which agents can use to get schema guidance, best practices, and safe, structured access to Postgres. This is also helpful to run migrations with a real understanding. > It comes with actual hybrid search (vector search and BM25), so Agents can retrieve data directly inside the database. > The database is Memory native. This gives a persistent context for Agents to evolve. This is one of the first times I have seen Postgres feel ready for the AI native era.
0:26

Big moment for Postgres! AI agents broke the idea of what a database is supposed to do. Traditional databases were built for humans, and Agents broke that model. - They branch endlessly. - They run ten experiments at once. - They need isolation, context, memory, structured reasoning, and safe sandboxes. Letting agents touch production systems is terrifying because the old model of Postgres was never built for this kind of behavior. Agentic Postgres is an agent-ready version of Postgres by TimescaleDB (by Tiger Data) that solves this. I think it is one of the biggest upgrades to the Agent stack this year and Tiger Data is working with me on this post to share what they did. Some key features: > It instantly creates branches of an entire database, which is perfect for parallel agent evals, safe experiments, migrations, or isolated testing. Forks take seconds and cost almost nothing. > It comes with a built-in MCP server, which agents can use to get schema guidance, best practices, and safe, structured access to Postgres. This is also helpful to run migrations with a real understanding. > It comes with actual hybrid search (vector search and BM25), so Agents can retrieve data directly inside the database. > The database is Memory native. This gives a persistent context for Agents to evolve. This is one of the first times I have seen Postgres feel ready for the AI native era.

Avi Chawla

94,290 views • 8 months ago

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:
2:06

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:

Andrew Ng

131,850 views • 1 year ago

English is the most powerful language in the world. MongoDB just added support for MCP, and literally anyone can now query data without knowing anything about databases. If you know English, you are all set. I recorded a quick video to show you how I connect to a sample Airbnb database and run different queries: • How many listings? • How many listings in the US? • What's the list of countries in these listings? It takes 10 seconds to configure Claude, Cursor, WindSurf, or any other AI assistant to connect to MongoDB's MCP Server. By the way, the server supports much more than queries: • You can explore your collections • You can fetch schema information • You can generate app code snippets • You can manage your databases • You can handle cluster/user/admin tasks Here is a link to the MCP server GitHub repository: This is huge for developers. It's even bigger for non-developers. Thanks to the MongoDB team for collaborating with me on this post.
3:27

English is the most powerful language in the world. MongoDB just added support for MCP, and literally anyone can now query data without knowing anything about databases. If you know English, you are all set. I recorded a quick video to show you how I connect to a sample Airbnb database and run different queries: • How many listings? • How many listings in the US? • What's the list of countries in these listings? It takes 10 seconds to configure Claude, Cursor, WindSurf, or any other AI assistant to connect to MongoDB's MCP Server. By the way, the server supports much more than queries: • You can explore your collections • You can fetch schema information • You can generate app code snippets • You can manage your databases • You can handle cluster/user/admin tasks Here is a link to the MCP server GitHub repository: This is huge for developers. It's even bigger for non-developers. Thanks to the MongoDB team for collaborating with me on this post.

Santiago

44,842 views • 1 year ago

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.
30:12

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

228,270 views • 3 months ago

Your agents can't keep up with real-time data. Especially when it's scattered across dozens of sources. Most teams waste weeks building custom connectors for every database, API, and data warehouse. Then they build ETL pipelines to sync everything. By the time your agent retrieves the data, it's already outdated. Picture this: Your Postgres database updated 5 minutes ago. Your MongoDB collection changed 2 minutes ago. Your agent is still pulling from yesterday's snapshot. This is why most production RAG systems fail. There's a better approach: MindsDB is an open-source AI platform with a federated data engine that lets you query multiple data sources in real-time using SQL - without moving any data. Here's what makes it different: ↳ Your data stays in place. No ETL pipelines or data duplication ↳ Query Postgres, MongoDB, REST APIs, and more using consistent SQL ↳ JOIN across different sources in real-time with a unified interface ↳ Works with both structured and un-structured data And here's the best part: You don't even need to write SQL. Just describe what you want in plain English, and MindsDB converts it to SQL automatically. The system does all the heavy lifting. The breakthrough for AI agents is simple: When data updates at the source, your agent gets fresh results immediately. No sync delays. No stale embeddings. No custom code for each integration. You can literally write a SQL query that joins a Postgres table with a MongoDB collection and gets live results. This is what production AI applications need but rarely get. In this video, I give you a complete walkthrough of what we just discussed and how to actually do it. Make sure you watch this till the end. I've shared the link to MindsDB's GitHub repo in the next tweet!
9:28

Your agents can't keep up with real-time data. Especially when it's scattered across dozens of sources. Most teams waste weeks building custom connectors for every database, API, and data warehouse. Then they build ETL pipelines to sync everything. By the time your agent retrieves the data, it's already outdated. Picture this: Your Postgres database updated 5 minutes ago. Your MongoDB collection changed 2 minutes ago. Your agent is still pulling from yesterday's snapshot. This is why most production RAG systems fail. There's a better approach: MindsDB is an open-source AI platform with a federated data engine that lets you query multiple data sources in real-time using SQL - without moving any data. Here's what makes it different: ↳ Your data stays in place. No ETL pipelines or data duplication ↳ Query Postgres, MongoDB, REST APIs, and more using consistent SQL ↳ JOIN across different sources in real-time with a unified interface ↳ Works with both structured and un-structured data And here's the best part: You don't even need to write SQL. Just describe what you want in plain English, and MindsDB converts it to SQL automatically. The system does all the heavy lifting. The breakthrough for AI agents is simple: When data updates at the source, your agent gets fresh results immediately. No sync delays. No stale embeddings. No custom code for each integration. You can literally write a SQL query that joins a Postgres table with a MongoDB collection and gets live results. This is what production AI applications need but rarely get. In this video, I give you a complete walkthrough of what we just discussed and how to actually do it. Make sure you watch this till the end. I've shared the link to MindsDB's GitHub repo in the next tweet!

Akshay 🚀

65,672 views • 8 months ago

This is probably the biggest news yet in software going headless, and will bring knowledge work agents to the masses. The new ChatGPT agents have access to any of the tools and data you want to work with, with complete coding and tool use available to them. Here's an example of a custom sales assistant agent uses Box as a knowledge source for accessing enterprise content securely to answer questions and generate new content on the fly. The workflows can obviously vastly far more complex as the agent can use any of the tools within Box available via MCP and CLI. This precisely what agents will start to look like for knowledge work. You'll be able to spin them up in the foreground or background to help augment work. Big opportunity right now for headless platforms, and for all the new builders and designers of these agents in the enterprise.
1:06

This is probably the biggest news yet in software going headless, and will bring knowledge work agents to the masses. The new ChatGPT agents have access to any of the tools and data you want to work with, with complete coding and tool use available to them. Here's an example of a custom sales assistant agent uses Box as a knowledge source for accessing enterprise content securely to answer questions and generate new content on the fly. The workflows can obviously vastly far more complex as the agent can use any of the tools within Box available via MCP and CLI. This precisely what agents will start to look like for knowledge work. You'll be able to spin them up in the foreground or background to help augment work. Big opportunity right now for headless platforms, and for all the new builders and designers of these agents in the enterprise.

Aaron Levie

420,133 views • 3 months ago

8 rules to improve your AI coding agent. All of these rules work with Claude Code, Cursor, VS Code, and with most programming languages. Automating these rules will 10x the code quality and security produced by your AI coding agents. 1. Dependency checks - Prevent your agent from suggesting insecure libraries based on outdated training data. 2. Secret exposure - Auto-fix the use of hardcoded credentials introduced by your coding agent. 3. File and function size - Automatically refactor any files or functions that exceed a reasonable length. 4. Complexity and parameter limits - Simplify overly complex code written by the agent. 5. SQL Injection - Auto-fix all database interactions with unsanitized user input. 6. Unused variables and imports - Detect and remove dead code. 7. Detect invisible unicode characters in AI rules files - Remove zero-width spaces, direction overrides, and other invisible characters that can hide malicious behavior. 8. Insecure OpenAI API usage - Enforce use of secure OpenAI endpoints, proper authentication, and context isolation Here is how you can automate this: Install the Codacy extension. This will give you access to a CLI for local scanning and an MCP server for agent communication. From here on out, every time you need to generate some code: 1. Your agent will write the code 2. It will then call Codacy's CLI to check it 3. It will find any issues in real time 4. Your coding agent will fix the issues 5. When the code passes all checks, you are done Level of effort on your side: literally zero! Code quality and security because of this: 100x better! Here is the link to download the extension for your IDE: Thanks to the Codacy team for collaborating with me on this post.
3:50

8 rules to improve your AI coding agent. All of these rules work with Claude Code, Cursor, VS Code, and with most programming languages. Automating these rules will 10x the code quality and security produced by your AI coding agents. 1. Dependency checks - Prevent your agent from suggesting insecure libraries based on outdated training data. 2. Secret exposure - Auto-fix the use of hardcoded credentials introduced by your coding agent. 3. File and function size - Automatically refactor any files or functions that exceed a reasonable length. 4. Complexity and parameter limits - Simplify overly complex code written by the agent. 5. SQL Injection - Auto-fix all database interactions with unsanitized user input. 6. Unused variables and imports - Detect and remove dead code. 7. Detect invisible unicode characters in AI rules files - Remove zero-width spaces, direction overrides, and other invisible characters that can hide malicious behavior. 8. Insecure OpenAI API usage - Enforce use of secure OpenAI endpoints, proper authentication, and context isolation Here is how you can automate this: Install the Codacy extension. This will give you access to a CLI for local scanning and an MCP server for agent communication. From here on out, every time you need to generate some code: 1. Your agent will write the code 2. It will then call Codacy's CLI to check it 3. It will find any issues in real time 4. Your coding agent will fix the issues 5. When the code passes all checks, you are done Level of effort on your side: literally zero! Code quality and security because of this: 100x better! Here is the link to download the extension for your IDE: Thanks to the Codacy team for collaborating with me on this post.

Santiago

49,331 views • 9 months ago

This guy lost his private keys to an AI agent. Then his passwords leaked online. He wasn't the only one. Reddit threads blew up. Dozens of people saying the same thing. "My credentials got exposed." "The agent ran code I didn't approve." "I don't trust this anymore." That's the OpenClaw problem nobody talks about. Now there's a fix. It's called IronClaw. Here's what makes it different: Built in Rust → fewer bugs, fewer holes for hackers to exploit Web assembly sandboxes → every tool runs in its own sealed room Encrypted credential vault → the AI never sees your passwords. Ever. Policy enforcement → you set the rules, the agent follows them Full audit logs → see exactly what it did, when, and why Side by side: OpenClaw → credentials leaked, no audit trail, tools accessed everything IronClaw → encrypted vault, sandboxed tools, policy guardrails, logs everything It's not for casual use yet. But if you're running a real business with real data? There's only one right answer here. Go to ironclaw.te and read how the credential vault works. The future of AI agents is secure AI agents. Full stop.
8:02

This guy lost his private keys to an AI agent. Then his passwords leaked online. He wasn't the only one. Reddit threads blew up. Dozens of people saying the same thing. "My credentials got exposed." "The agent ran code I didn't approve." "I don't trust this anymore." That's the OpenClaw problem nobody talks about. Now there's a fix. It's called IronClaw. Here's what makes it different: Built in Rust → fewer bugs, fewer holes for hackers to exploit Web assembly sandboxes → every tool runs in its own sealed room Encrypted credential vault → the AI never sees your passwords. Ever. Policy enforcement → you set the rules, the agent follows them Full audit logs → see exactly what it did, when, and why Side by side: OpenClaw → credentials leaked, no audit trail, tools accessed everything IronClaw → encrypted vault, sandboxed tools, policy guardrails, logs everything It's not for casual use yet. But if you're running a real business with real data? There's only one right answer here. Go to ironclaw.te and read how the credential vault works. The future of AI agents is secure AI agents. Full stop.

Julian Goldie SEO

15,686 views • 5 months ago

PREDICTION MARKET RESEARCH JUST GOT KILLED BY ONE .MD FILE. The .md file in the video plugs any AI agent into 1,800 live data sources -> Polymarket orderbooks, satellite imagery, vessel tracking, NOAA weather, SEC filings, sports lines, and the top 100 KOL wallets. It's pref.trade. No APIs, no scraping, no signup and no card. An agent with this installed doesn't ask "What's the price". It pulls the orderbook depth on Polymarket, cross-references vessel positions in the Strait of Hormuz, scans the latest SEC filings on the names mentioned, and watches what the top 100 KOL wallets did in the last 4 hours. Before it makes a single call. The numbers are insane: > $0 in API fees. > $0 in data subscriptions. > 670+ capabilities behind a single endpoint. Every datapoint with full provenance back to the source. The mechanism is wild too: It's called Preference. An MCP server that gives any AI agent structured access to prediction markets -> Polymarket, Kalshi, Hyperliquid, dFlow AND the real-world signals that price them. Your agent asks one question, gets the full picture before it acts. It goes way past Polymarket: Smart-money mirroring on the top 100 wallets in real time. Cross-venue arb scanners and event-driven agents that watch tanker traffic in the Strait of Hormuz and trade oil-linked markets. Backtesting pipelines over historical data plus the world signals that moved each market. The model was never the bottleneck. The data was. One agent, one .md file and Live world data on tap. -> Retail still has 12 CoinGecko tabs open. Agents already have the orderbook. Full info and guide at Don't forget to save.
0:34

PREDICTION MARKET RESEARCH JUST GOT KILLED BY ONE .MD FILE. The .md file in the video plugs any AI agent into 1,800 live data sources -> Polymarket orderbooks, satellite imagery, vessel tracking, NOAA weather, SEC filings, sports lines, and the top 100 KOL wallets. It's pref.trade. No APIs, no scraping, no signup and no card. An agent with this installed doesn't ask "What's the price". It pulls the orderbook depth on Polymarket, cross-references vessel positions in the Strait of Hormuz, scans the latest SEC filings on the names mentioned, and watches what the top 100 KOL wallets did in the last 4 hours. Before it makes a single call. The numbers are insane: > $0 in API fees. > $0 in data subscriptions. > 670+ capabilities behind a single endpoint. Every datapoint with full provenance back to the source. The mechanism is wild too: It's called Preference. An MCP server that gives any AI agent structured access to prediction markets -> Polymarket, Kalshi, Hyperliquid, dFlow AND the real-world signals that price them. Your agent asks one question, gets the full picture before it acts. It goes way past Polymarket: Smart-money mirroring on the top 100 wallets in real time. Cross-venue arb scanners and event-driven agents that watch tanker traffic in the Strait of Hormuz and trade oil-linked markets. Backtesting pipelines over historical data plus the world signals that moved each market. The model was never the bottleneck. The data was. One agent, one .md file and Live world data on tap. -> Retail still has 12 CoinGecko tabs open. Agents already have the orderbook. Full info and guide at Don't forget to save.

slash1s

61,519 views • 2 months ago