正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

Finally. I shipped a side-project. Introducing inbrowser. Pluggable AI architecture totally in the browser. site: repo: @inbrowser/model: on-device w/ transformers.js & webgpu. Cloud model proxies and OpenRouter BYOK flows. @inbrowser/agent: pluggable client-side agent architecture @inbrowser/resumable: pick up and resume across refreshes @inbrowser/relay: when you need a server, syncs resumable... show more

David East

25,267 subscribers

18,605 次观看 • 1 个月前 •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

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,343 次观看 • 1 年前

Today we shipped a new Search experience in Chrome to help you explore the web without constant back and forth between tabs. Now, when you click a link from AI Mode, the website opens side-by-side. It's a game changer for comparing details and products across sites, discovering new content & asking follow up Qs about what you’re seeing – all in one view. If you're in the U.S. try it on Chrome desktop today! Just make sure you’ve got the latest version of Chrome to try it out⚡️

Today we shipped a new Search experience in Chrome to help you explore the web without constant back and forth between tabs. Now, when you click a link from AI Mode, the website opens side-by-side. It's a game changer for comparing details and products across sites, discovering new content & asking follow up Qs about what you’re seeing – all in one view. If you're in the U.S. try it on Chrome desktop today! Just make sure you’ve got the latest version of Chrome to try it out⚡️

Robby Stein

120,687 次观看 • 3 个月前

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

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

ℏεsam

62,794 次观看 • 22 天前

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

Vaibhav Sisinty

36,661 次观看 • 29 天前

Meet WebBrain: An Open-Source, Local-First AI Browser Agent That Reads Pages and Automates Tasks in Chrome and Firefox WebBrain lives inside your browser and can run entirely on your own local model — no cloud, no account, no data leaving your machine. Most "AI browser agents" are a chat box that pastes your page into someone else's server. That's not an agent that lives where you browse — and WebBrain draws a very clear line between the two. It's an open-source (MIT), local-first browser agent for Chrome and Firefox. It runs inside your existing authenticated session, on a model you pick — so with llama.cpp or Ollama, nothing leaves your machine. Here's what's actually interesting: → Two modes, cleanly separated. Ask reads the page (read-only, content scripts). Act clicks and types through the Chrome DevTools Protocol (chrome.debugger) — trusted input events that modern sites honor, reaching cross-origin iframes and shadow DOM. → UI-first by design. For anything that submits, sends, or buys, it drives the visible UI and refuses to hit REST/GraphQL endpoints directly. It starts read-only and asks before consequential actions. → Bring any model. llama.cpp, Ollama, LM Studio, vLLM — or OpenAI, Claude, Gemini, DeepSeek, Groq, OpenRouter. Recommended local: Qwen 3.6 35B (Qwen3.6-35B-A3B), which beat Gemma 4 on the project's screenshot benchmark. → Tuned for cost and privacy. Token-conscious screenshots, oldest-first context trimming, a dedicated vision model, 40+ tools (~20 in Compact mode). No telemetry. No accounts. Full analysis: GitHub Repo: Chrome Extension: Firefox Add-on: Portal:

Meet WebBrain: An Open-Source, Local-First AI Browser Agent That Reads Pages and Automates Tasks in Chrome and Firefox WebBrain lives inside your browser and can run entirely on your own local model — no cloud, no account, no data leaving your machine. Most "AI browser agents" are a chat box that pastes your page into someone else's server. That's not an agent that lives where you browse — and WebBrain draws a very clear line between the two. It's an open-source (MIT), local-first browser agent for Chrome and Firefox. It runs inside your existing authenticated session, on a model you pick — so with llama.cpp or Ollama, nothing leaves your machine. Here's what's actually interesting: → Two modes, cleanly separated. Ask reads the page (read-only, content scripts). Act clicks and types through the Chrome DevTools Protocol (chrome.debugger) — trusted input events that modern sites honor, reaching cross-origin iframes and shadow DOM. → UI-first by design. For anything that submits, sends, or buys, it drives the visible UI and refuses to hit REST/GraphQL endpoints directly. It starts read-only and asks before consequential actions. → Bring any model. llama.cpp, Ollama, LM Studio, vLLM — or OpenAI, Claude, Gemini, DeepSeek, Groq, OpenRouter. Recommended local: Qwen 3.6 35B (Qwen3.6-35B-A3B), which beat Gemma 4 on the project's screenshot benchmark. → Tuned for cost and privacy. Token-conscious screenshots, oldest-first context trimming, a dedicated vision model, 40+ tools (~20 in Compact mode). No telemetry. No accounts. Full analysis: GitHub Repo: Chrome Extension: Firefox Add-on: Portal:

Marktechpost AI

203,011 次观看 • 29 天前

The Vercel fluid × Upstash agents framework just solved one of the trickiest issues in chatbots/agents and one of my biggest pet peeves 😆 Notice that right after submitting my message, it immediately assigns an uuid (`/wfr_KgW5x…`) to the job. At this point, my internet might flake out, I might shut my laptop lid, I might go to my phone and open the chat from there… What you're looking at is a resumable, durable agentic workflow that's fault tolerant on the server and on the client. On the server side, Fluid functions on Vercel will be invoked for each step, and they can fail and get retried. On the client, polling for changes ensures eventual consistency even in the presence of very long network partitions. Shoutout to yunus for collaborating with me on shipping these improvements. Check out the OSS Next.js repo to learn these patterns and the demo at: ps: it's actually impressive what a wide range of questions this simple demo agent can answer by choosing between Exa / Wikipedia / Wolfram

The Vercel fluid × Upstash agents framework just solved one of the trickiest issues in chatbots/agents and one of my biggest pet peeves 😆 Notice that right after submitting my message, it immediately assigns an uuid (`/wfr_KgW5x…`) to the job. At this point, my internet might flake out, I might shut my laptop lid, I might go to my phone and open the chat from there… What you're looking at is a resumable, durable agentic workflow that's fault tolerant on the server and on the client. On the server side, Fluid functions on Vercel will be invoked for each step, and they can fail and get retried. On the client, polling for changes ensures eventual consistency even in the presence of very long network partitions. Shoutout to yunus for collaborating with me on shipping these improvements. Check out the OSS Next.js repo to learn these patterns and the demo at: ps: it's actually impressive what a wide range of questions this simple demo agent can answer by choosing between Exa / Wikipedia / Wolfram

Guillermo Rauch

56,799 次观看 • 1 年前

I got Llama 3 running in my browser using only my GPU with my Wi-Fi switched OFF completely client-side WebGPU is a new feature in browsers where JS can use the GPU of the device and apparently you can run LLMs on it too, and it's fast! My end goal for 🧠 is a locally run client side 100% private conversation where nothing gets sent to, processed in or stored in the cloud This will be helpful because I prefer making it web based instead of coding for 4 different native platforms (iOS, Android, MacOS, Windows) Two challenges still: 1) the user has to download the LLM model first and the smallest model is still ~3GB, but they only have to download it once 2) not all devices have fast GPUs yet for LLMs, but it's starting to become a default in most devices e.g.s smartphones

I got Llama 3 running in my browser using only my GPU with my Wi-Fi switched OFF completely client-side WebGPU is a new feature in browsers where JS can use the GPU of the device and apparently you can run LLMs on it too, and it's fast! My end goal for 🧠 is a locally run client side 100% private conversation where nothing gets sent to, processed in or stored in the cloud This will be helpful because I prefer making it web based instead of coding for 4 different native platforms (iOS, Android, MacOS, Windows) Two challenges still: 1) the user has to download the LLM model first and the smallest model is still ~3GB, but they only have to download it once 2) not all devices have fast GPUs yet for LLMs, but it's starting to become a default in most devices e.g.s smartphones

@levelsio

261,416 次观看 • 2 年前

Introducing the new Box Agent. The Box Agent works across your entire Box file system, maintaining all your security and access controls, and is hyper tuned for working with enterprise content. This means you can now ask questions from all your enterprise content, search for files that were impossible to find before, deploy an agent on specific tasks on subsets of documents, analyze complex data sets, and generate or edit documents and spreadsheets via the agent. You can have the Box Agent search across your Box account to prepare for a sales meeting, analyze customer sentiment reports, process a large set of contracts for legal risk, provide insights into product development, leverage existing knowledge to answer RFPs, and thousands of other use-cases. 90% of enterprise data is unstructured data. This means most enterprise knowledge is sitting in inside of research reports, marketing assets, presentations, roadmap files, contracts, HR documents, and more. This is the critical context that agents need to be able to answer questions about a business, automate workflows, or serve up to other agents. We’ve been grinding on this for a quite a bit, and due to recent AI model advancements we’re now ready to release it to customers. Previous model generations had a difficult time knowing when to give up or keep going on a search, when to browse for files vs. use queries, how to rank files appropriately to know which version of content to use, how to handle large amounts of context to comb through, and more. Due to recent breakthroughs from models like GPT-5.4, Opus 4.6, and Gemini 3, we’ve seen major gains in tool calling, code execution, advanced reasoning, and more. Combined with an agent harness tuned to Box context, now it’s finally possible to have an agent that can work across your file system on long running tasks and actually deliver high quality results. Best of all, because the Box Agent works with any leading AI model, you’ll quickly get the gains coming out of the major labs as major new models are released. Further, openness at Box is key, so you’ll be able to call up the Box Agent from Box’s APIs and MCP server, so you can interact with Box intelligently from any other AI system. We know work happens everywhere, and we want to ensure you can access to the content you need from those places. The new Box Agent is available starting today, rolling out now for Enterprise Plus and Enterprise Advanced customers.

Introducing the new Box Agent. The Box Agent works across your entire Box file system, maintaining all your security and access controls, and is hyper tuned for working with enterprise content. This means you can now ask questions from all your enterprise content, search for files that were impossible to find before, deploy an agent on specific tasks on subsets of documents, analyze complex data sets, and generate or edit documents and spreadsheets via the agent. You can have the Box Agent search across your Box account to prepare for a sales meeting, analyze customer sentiment reports, process a large set of contracts for legal risk, provide insights into product development, leverage existing knowledge to answer RFPs, and thousands of other use-cases. 90% of enterprise data is unstructured data. This means most enterprise knowledge is sitting in inside of research reports, marketing assets, presentations, roadmap files, contracts, HR documents, and more. This is the critical context that agents need to be able to answer questions about a business, automate workflows, or serve up to other agents. We’ve been grinding on this for a quite a bit, and due to recent AI model advancements we’re now ready to release it to customers. Previous model generations had a difficult time knowing when to give up or keep going on a search, when to browse for files vs. use queries, how to rank files appropriately to know which version of content to use, how to handle large amounts of context to comb through, and more. Due to recent breakthroughs from models like GPT-5.4, Opus 4.6, and Gemini 3, we’ve seen major gains in tool calling, code execution, advanced reasoning, and more. Combined with an agent harness tuned to Box context, now it’s finally possible to have an agent that can work across your file system on long running tasks and actually deliver high quality results. Best of all, because the Box Agent works with any leading AI model, you’ll quickly get the gains coming out of the major labs as major new models are released. Further, openness at Box is key, so you’ll be able to call up the Box Agent from Box’s APIs and MCP server, so you can interact with Box intelligently from any other AI system. We know work happens everywhere, and we want to ensure you can access to the content you need from those places. The new Box Agent is available starting today, rolling out now for Enterprise Plus and Enterprise Advanced customers.

Aaron Levie

44,515 次观看 • 4 个月前

We’re pushing cross-chain automation to a new level. Our backend Motoko architecture now lets an $ICP smart contract directly execute $NEAR transactions without any client-side code. The contract itself becomes the agent fully autonomous, programmable, and always on. To complement this, we introduced a NEAR-specific on-chain RPC Oracle canister that cryptographically verifies NEAR data and transactions. This dramatically improves reliability, reduces latency, and unlocks 24/7 trust-minimized execution across NEAR. But we’re not stopping there. Our backend execution layer is already designed to operate seamlessly across chains like $Monad, $TRON, $SUI, and $ADA, with Motoko-driven workflows and cross-chain messaging. The RPC Oracle is purpose-built for $NEAR today, while all these ecosystems—and more—can leverage our autonomous backend compute model.

We’re pushing cross-chain automation to a new level. Our backend Motoko architecture now lets an $ICP smart contract directly execute $NEAR transactions without any client-side code. The contract itself becomes the agent fully autonomous, programmable, and always on. To complement this, we introduced a NEAR-specific on-chain RPC Oracle canister that cryptographically verifies NEAR data and transactions. This dramatically improves reliability, reduces latency, and unlocks 24/7 trust-minimized execution across NEAR. But we’re not stopping there. Our backend execution layer is already designed to operate seamlessly across chains like $Monad, $TRON, $SUI, and $ADA, with Motoko-driven workflows and cross-chain messaging. The RPC Oracle is purpose-built for $NEAR today, while all these ecosystems—and more—can leverage our autonomous backend compute model.

ICP HUB Egypt

12,353 次观看 • 7 个月前

We keep defaulting to the biggest model in the room every time we touch AI in our apps. Claude, GPT, Gemini. Cloud or nothing. But the browser is already more capable than most people realize: WebAI and WebMCP may change this. With WebAI you can run models client-side. With WebMCP, your site can expose real actions as JavaScript functions. Agents don't need screenshots, DOM scraping, or blind clicking. They can just use your app. I talked about this with Guy Podjarny on Tessl AI Native Dev podcast: the browser is turning into an AI runtime. Links in first reply :)

We keep defaulting to the biggest model in the room every time we touch AI in our apps. Claude, GPT, Gemini. Cloud or nothing. But the browser is already more capable than most people realize: WebAI and WebMCP may change this. With WebAI you can run models client-side. With WebMCP, your site can expose real actions as JavaScript functions. Agents don't need screenshots, DOM scraping, or blind clicking. They can just use your app. I talked about this with Guy Podjarny on Tessl AI Native Dev podcast: the browser is turning into an AI runtime. Links in first reply :)

Maximiliano Firtman

14,824 次观看 • 4 个月前

This is THE moment of Physical AI! We are officially announcing Cosmos 3: Omnimodal World Models for Physical AI 🚀 - Cosmos 3 is an omnimodal world model: within a unified architecture, it can understand and generate language, images, video, audio, and actions. - It is not just a VLM, not just a video generator, not just an audio-visual generative model, and not just a physics simulator / world-action model. It can understand images and videos, generate images, videos, and audio, simulate future worlds, predict actions, and generate robot policies—enabling models to truly begin to “touch the world.” - Cosmos 3 is the #1 open-weight reasoner / T2I / I2V / robot policy across many benchmarks. Huge thanks to every teammate who fought side by side on this journey—from architecture, data, training, infra, serving, and evaluation to post-training. Every part of this project carries an incredible amount of hard work. This was my first time leading a project as Tech Lead, and I feel truly fortunate. The future of Physical AI needs models that can not only “see” and “describe” the world, but also “imagine,” “simulate,” and “act”—and eventually close the loop with the real world. I hope Cosmos 3 can become an important starting point for this direction, and I’m excited to push Physical AI into its next stage together with the open-source community. Welcome to the era of Physical AI. HuggingFace: Project Website: Code:

This is THE moment of Physical AI! We are officially announcing Cosmos 3: Omnimodal World Models for Physical AI 🚀 - Cosmos 3 is an omnimodal world model: within a unified architecture, it can understand and generate language, images, video, audio, and actions. - It is not just a VLM, not just a video generator, not just an audio-visual generative model, and not just a physics simulator / world-action model. It can understand images and videos, generate images, videos, and audio, simulate future worlds, predict actions, and generate robot policies—enabling models to truly begin to “touch the world.” - Cosmos 3 is the #1 open-weight reasoner / T2I / I2V / robot policy across many benchmarks. Huge thanks to every teammate who fought side by side on this journey—from architecture, data, training, infra, serving, and evaluation to post-training. Every part of this project carries an incredible amount of hard work. This was my first time leading a project as Tech Lead, and I feel truly fortunate. The future of Physical AI needs models that can not only “see” and “describe” the world, but also “imagine,” “simulate,” and “act”—and eventually close the loop with the real world. I hope Cosmos 3 can become an important starting point for this direction, and I’m excited to push Physical AI into its next stage together with the open-source community. Welcome to the era of Physical AI. HuggingFace: Project Website: Code:

Max Zhaoshuo Li 李赵硕

1,078,268 次观看 • 2 个月前

i tested a fully local ai coding setup: gemma4 from Google DeepMind running through LM Studio, paired with pi which is a minimal open source coding harness this is part 1 of a two part series. here we cover the why and the complete hands-on setup 0:00 - Running a coding agent fully local 0:47 - Why Pi as the coding agent harness 1:39 - Why Gemma 4 and which variant to pick 2:44 - Architecture: Pi, LM Studio and Gemma 4 3:45 - LM Studio setup and model download 5:01 - Starting the local server 5:19 - API sanity check with curl 6:08 - Installing the Pi coding agent 6:20 - Configuring models.json for local models 8:20 - First run: selecting the model in Pi 8:58 - Fixing the context length error 10:16 - Testing the working setup 10:50 - What is coming in Part 2

i tested a fully local ai coding setup: gemma4 from Google DeepMind running through LM Studio, paired with pi which is a minimal open source coding harness this is part 1 of a two part series. here we cover the why and the complete hands-on setup 0:00 - Running a coding agent fully local 0:47 - Why Pi as the coding agent harness 1:39 - Why Gemma 4 and which variant to pick 2:44 - Architecture: Pi, LM Studio and Gemma 4 3:45 - LM Studio setup and model download 5:01 - Starting the local server 5:19 - API sanity check with curl 6:08 - Installing the Pi coding agent 6:20 - Configuring models.json for local models 8:20 - First run: selecting the model in Pi 8:58 - Fixing the context length error 10:16 - Testing the working setup 10:50 - What is coming in Part 2

Nidhi Singh

16,289 次观看 • 1 个月前

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!

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 次观看 • 1 年前

Coding agents shouldn't run on a laptop. That's why I've been building Cave. It's a self-hosted platform for running OpenCode agents in isolated sandboxes on your own server. You give it a GitHub repo, it creates an isolated sandbox, clones the code, sets everything up, and gives you a coding agent. Check in from your phone, run multiple agents side by side. It's not open source yet (it will be), but I'm opening a private beta so you can install it on your own server already. I've been dogfooding it since day one. If you're running a software factory: multiple agents working in parallel across repos, Cave gives you one place to monitor and manage all of it. Now, I'm looking for people who want to give it a spin. DM me, happy to set you up 😊 🚀

Coding agents shouldn't run on a laptop. That's why I've been building Cave. It's a self-hosted platform for running OpenCode agents in isolated sandboxes on your own server. You give it a GitHub repo, it creates an isolated sandbox, clones the code, sets everything up, and gives you a coding agent. Check in from your phone, run multiple agents side by side. It's not open source yet (it will be), but I'm opening a private beta so you can install it on your own server already. I've been dogfooding it since day one. If you're running a software factory: multiple agents working in parallel across repos, Cave gives you one place to monitor and manage all of it. Now, I'm looking for people who want to give it a spin. DM me, happy to set you up 😊 🚀

André König

36,102 次观看 • 3 个月前

Today, we’re introducing Skills in Chrome, a new way to build one-click workflows for your most frequently used AI prompts — like asking for ingredient substitutions to make a recipe vegan, generating side-by-side shopping comparisons across multiple tabs, or scanning long docs to get the info you need quickly. When you write a prompt that you want to use again, you can save it as a Skill directly from your chat history. The next time you need it, select your saved Skill in Gemini in Chrome by typing forward slash ( / ) or clicking the plus sign ( + ) button, and your Skill will run on the page you’re viewing, along with any other tabs you select.

Today, we’re introducing Skills in Chrome, a new way to build one-click workflows for your most frequently used AI prompts — like asking for ingredient substitutions to make a recipe vegan, generating side-by-side shopping comparisons across multiple tabs, or scanning long docs to get the info you need quickly. When you write a prompt that you want to use again, you can save it as a Skill directly from your chat history. The next time you need it, select your saved Skill in Gemini in Chrome by typing forward slash ( / ) or clicking the plus sign ( + ) button, and your Skill will run on the page you’re viewing, along with any other tabs you select.

Google

1,280,693 次观看 • 3 个月前

We're winning the AI browser wars, and we're not even trying. Our mission isn't to build a browser. We're an agent company, not a browser company. We've seen firsthand how teams struggle to get started with AI. The tools they tried are too complex and lack the context you need. We decided to build a browser since it's already the tool you work in. We all know how to use a browser. You can pick up Strawberry and start using AI agents from day one. By building a browser we are also positioning ourselves to build towards the internet of the future. An internet where trillions of agents will be communicating with each other. This is the biggest opportunity of our lifetime. But someone has to make sure it is safe, effective and accessible to teams across the world. That is our mission.

We're winning the AI browser wars, and we're not even trying. Our mission isn't to build a browser. We're an agent company, not a browser company. We've seen firsthand how teams struggle to get started with AI. The tools they tried are too complex and lack the context you need. We decided to build a browser since it's already the tool you work in. We all know how to use a browser. You can pick up Strawberry and start using AI agents from day one. By building a browser we are also positioning ourselves to build towards the internet of the future. An internet where trillions of agents will be communicating with each other. This is the biggest opportunity of our lifetime. But someone has to make sure it is safe, effective and accessible to teams across the world. That is our mission.

Charles Maddock

38,357 次观看 • 1 个月前

New episode of The Information Bottleneck is out, this time with Zhuang Liu (Princeton). We talked about ConvNeXt and whether architecture still matters; dataset bias and what "good data" actually looks like; ImageBind and why vision is the natural bridge across modalities; CLIP's blind spots; memory as the real bottleneck behind the agent hype; whether LLMs have world models; and Transformers Without Normalization. For years, the vision community debated what actually matters: architecture, inductive bias, self-attention vs convolution. After a lot of back-and-forth, we ended up in a funny place: ViT and ConvNet give roughly the same performance once you tune the details. What I find interesting is that once you reach a certain performance level, it becomes much easier to swap and tweak components without really changing the outcome. Talking to Zhuang on this episode, I kept wondering whether the same is now true for LLMs. If we wil spent serious time on an alternative architecture today, would you actually get a meaningfully different model, or just land on the same Pareto curve with extra steps? I'm starting to suspect it's the latter. Architecture matters less than we think. Data, compute, and a handful of pillars do most of the work.

New episode of The Information Bottleneck is out, this time with Zhuang Liu (Princeton). We talked about ConvNeXt and whether architecture still matters; dataset bias and what "good data" actually looks like; ImageBind and why vision is the natural bridge across modalities; CLIP's blind spots; memory as the real bottleneck behind the agent hype; whether LLMs have world models; and Transformers Without Normalization. For years, the vision community debated what actually matters: architecture, inductive bias, self-attention vs convolution. After a lot of back-and-forth, we ended up in a funny place: ViT and ConvNet give roughly the same performance once you tune the details. What I find interesting is that once you reach a certain performance level, it becomes much easier to swap and tweak components without really changing the outcome. Talking to Zhuang on this episode, I kept wondering whether the same is now true for LLMs. If we wil spent serious time on an alternative architecture today, would you actually get a meaningfully different model, or just land on the same Pareto curve with extra steps? I'm starting to suspect it's the latter. Architecture matters less than we think. Data, compute, and a handful of pillars do most of the work.

Ravid Shwartz Ziv

26,083 次观看 • 3 个月前

Today we're introducing Postman Fabric Gateway—an AI-native agent gateway. Here's why it matters: agents will consume APIs at several orders of magnitude beyond traditional apps. Traditional API Gateways are not designed for AI agents. While many legacy vendors have tried to support agentic workloads, Postman customers have been asking us about something that is AI-native and doesn’t have the baggage of pre-AI architecture. Postman Fabric has been designed from the ground-up for agents with support for MCPs, CLIs, as well as APIs - both AI and deterministic APIs. We are building this with a modular architecture as we are still in the early innings of AI and there are many new patterns that are likely to emerge. One thing is certain though, agents are driven by APIs, and you can’t have agent-ready APIs without a purpose-built gateway. Through Postman Fabric, customers will be able to: 1️⃣ Have a single plane to manage all MCP servers - public or private 2️⃣ Expose internal APIs as MCP tools 3️⃣ Centralize SaaS credentials 4️⃣ Govern agent traffic and run policies at a consumer, route, or service level 5️⃣ Deploy on cloud or in a hybrid model We are opening up early access soon - let me know if you are interested in the comments or a DM!

Today we're introducing Postman Fabric Gateway—an AI-native agent gateway. Here's why it matters: agents will consume APIs at several orders of magnitude beyond traditional apps. Traditional API Gateways are not designed for AI agents. While many legacy vendors have tried to support agentic workloads, Postman customers have been asking us about something that is AI-native and doesn’t have the baggage of pre-AI architecture. Postman Fabric has been designed from the ground-up for agents with support for MCPs, CLIs, as well as APIs - both AI and deterministic APIs. We are building this with a modular architecture as we are still in the early innings of AI and there are many new patterns that are likely to emerge. One thing is certain though, agents are driven by APIs, and you can’t have agent-ready APIs without a purpose-built gateway. Through Postman Fabric, customers will be able to: 1️⃣ Have a single plane to manage all MCP servers - public or private 2️⃣ Expose internal APIs as MCP tools 3️⃣ Centralize SaaS credentials 4️⃣ Govern agent traffic and run policies at a consumer, route, or service level 5️⃣ Deploy on cloud or in a hybrid model We are opening up early access soon - let me know if you are interested in the comments or a DM!

Abhinav Asthana

18,140 次观看 • 2 个月前

I built Caduceus for Hermes Desktop Nous Research Two snakes, one staff Caduceus runs parallel AI agents in perfect sync, on any model you already have It sizes up every task and picks the path: • Easy → answered instantly • Hard → a live to-do plan + agents fanned out in parallel, verified before it calls it done Caduceus has a UI right inside Hermes so you watch every agent build your project in real time Full demo 👇

I built Caduceus for Hermes Desktop Nous Research Two snakes, one staff Caduceus runs parallel AI agents in perfect sync, on any model you already have It sizes up every task and picks the path: • Easy → answered instantly • Hard → a live to-do plan + agents fanned out in parallel, verified before it calls it done Caduceus has a UI right inside Hermes so you watch every agent build your project in real time Full demo 👇

Terp

16,919 次观看 • 1 个月前

💥AI is no longer confined to the cloud. At Computex, Jack Huynh showcased the AMD Ryzen AI Halo and Ryzen AI Max PRO 400 Series processors. The next wave of innovation will be built, trained, and run locally. As AI evolves from chatbots to intelligent agents, developers and enterprises need the performance, memory capacity, and flexibility to bring these experiences to life directly on the device. ⚡ Ryzen AI Halo enables local AI development with support for models up to 200B parameters, up to 128GB of unified memory, ROCm optimization, and Windows + Linux support. ⚡ Ryzen AI Max PRO 400 Series combines AI, graphics, and compute in a single architecture, delivering workstation-class performance for next-gen Agent Computers and AI PCs. Some of the most impactful AI experiences will happen right at your desk, where latency, privacy, and control matter most. We're just getting started.

💥AI is no longer confined to the cloud. At Computex, Jack Huynh showcased the AMD Ryzen AI Halo and Ryzen AI Max PRO 400 Series processors. The next wave of innovation will be built, trained, and run locally. As AI evolves from chatbots to intelligent agents, developers and enterprises need the performance, memory capacity, and flexibility to bring these experiences to life directly on the device. ⚡ Ryzen AI Halo enables local AI development with support for models up to 200B parameters, up to 128GB of unified memory, ROCm optimization, and Windows + Linux support. ⚡ Ryzen AI Max PRO 400 Series combines AI, graphics, and compute in a single architecture, delivering workstation-class performance for next-gen Agent Computers and AI PCs. Some of the most impactful AI experiences will happen right at your desk, where latency, privacy, and control matter most. We're just getting started.

AMD

24,315 次观看 • 1 个月前