Loading video...

Video Failed to Load

Go Home

Over the past 6 months, we've rearchitected Cline's agentic loop into a standalone "cline core" gRPC service that runs independently of any editor. This enabled us to decouple from VS code and build - JetBrains (released in GA this week) - CLI built in Go (releasing soon) - Secret...

59,960 views • 11 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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,137 views • 1 year ago

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."

The Pragmatic Engineer

13,258 views • 2 months ago

‼️ Donald Trump just posted the video saying any immigrant that comes to America and demand we change our culture is not an immigrant, they are an invader and must be removed “Just so we we’re clear, if a foreigner comes to your country and demands that you accept their culture as your culture or demands that you change your beliefs, that is not a foreigner, that is not an immigrant. What that is, is an invader. That is someone that is coming over to your space to take over and invade it. So when you sit there and you look at what's happening in New York, you look at what's happening in Texas, you look at what's happening in the places where these people came from, you look at Somalia, you look at all of these individuals who are being put into a position of power who support this type of invasion. You need to understand what's coming next. - They will take away our weapons - They will tell us that we cannot eat certain foods - They will tell us that we cannot go to certain places - They will tell that our women that they have to wear certain clothes - They will tell them that they have to dress modest. They will forced them to do a lot of different things. - You will have to deal with people praying in the middle of the street while you're driving and stopping you and invading your movement, your space You need to understand what's taking place in America so that you can understand that these people are not coming here with good intentions. This is not me saying that I hate people. This is me basically saying, look, if you like the fact that America is a free place where you get the freedom to believe in what religion you want to, to believe in. If you get the freedom to decide what you want to do as long as nobody is getting hurt. If you love that part of America, the freedom of choice part of America, you need to understand when people come over and they say that you don't have a choice, they probably should go because you don't get to tell us what to do in our own country. It's not being rude. It's just saying, hey, look, this country was built in a way where everybody can come here and feel happy and feel blessed. And enjoy the fact that this is a free nation, not a nation that will be enslaved by any Foreigner invading it”

Wall Street Apes

88,662 views • 8 months ago

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

Aaron Levie

24,618 views • 4 months ago

Computing hardware architecture has evolved from maximizing single-core performance to multiplying parallel processing capacity through more cores, more threads, and higher computational density. This transition demands software architectures specifically designed to exploit parallel processing, especially in advanced AI and blockchain-based systems. As Greg Meredith, CEO of our partner F1R3FLY. io, notes, "We need software architectures that can eat physical threads of computation and turn that into throughput." Traditional sequential programming models often struggle to effectively leverage the potential of these multi-core systems, creating a bottleneck in performance scaling. Rholang addresses this challenge through its foundation in the Rho-Calculus, a reflective higher-order process calculus specifically designed for inherent concurrency and reflection. Unlike computational models based on sequential execution or those that bolt on concurrency primitives, Rholang can leverage its process-oriented nature to detect and distribute non-interfering logical computation threads across available physical processing units, creating a more direct correlation between hardware resources and performance scaling. The Rho-Calculus was specifically designed to provide the minimal set of operations needed to model autonomous agents operating in parallel while maintaining the ability to represent their own reasoning processes. This structure mirrors the operational characteristics of intelligent systems, where autonomous processes run independently while communicating and coordinating. For our novel decentralized AI platform, MeTTaCycle, this future-proof architectural foundation enables more than just enhanced transactional throughput; it fosters an environment where independent computational processes can efficiently coexist and interact, forming a critical layer for the Artificial Superintelligence Alliance's decentralized AGI infrastructure and products.

SingularityNET

29,368 views • 1 year ago