@jdegoes: The immediate future of ALL agents is coding agents, and although I could be wrong, I believe this surprising fact is g…

The immediate future of ALL agents is coding agents, and although I could be wrong, I believe this surprising fact is going to be a HUGE boost for @typescript in particular. Let me explain. If your business wants an agent to assist with customer support, employee onboarding, outbound sales, or payroll, then the agent they need is actually a coding agent. The reason for this is quite simple: coding agents have an ability to leverage their training data to solve general-purpose problems, in ways shapes by the tools they have access to. An outbound sales agent assistant can talk to your knowledge base, pull some contacts from your CRM, analyze conversation history, do a web search to learn about each prospect, and then send email through your Gmail account to each prospect. Doing all of this stuff, and doing even more that the agent was never explicitly designed to do, requires the ability to write, test, and execute code for ad hoc, one-off problems. Only a coding agent can do that, and thanks to innovation at the level of the model and harness, a coding agent can do it well. Now, a true general-purpose coding agent can work in any code base, in any language, in any operating system, and with any tech stack. Of course, that type of coding agent is very useful to developers. However, it's overkill for most agentic systems. Most custom agents do not actually need to work with any code base or any language and on any operating system. They just need the ability to write code in some language (which has a lot of libraries) and execute on some platform. What is the ideal language and platform? I'd argue that @typescript fits the bill PERFECTLY. Since TypeScript compiles to Javascript, it can run securely, in a completely sandboxed way, inside V8 isolates, WASM, etc., all of which creates a compelling story for secure, efficient, and scalable custom agent execution. Moreover, because TypeScript adds types to Javascript, those types can be used to catch a lot of common bugs and runtime errors that a Javascript coding agent would have trouble catching in advance--allowing for far faster and more efficient solution of general-purpose problems. So, while general-purpose coding agents will of course need to support all programming languages, platforms, and tech stacks, custom agents are likely to be specialized -- while they will be coding agents, they don't need to work with any programming language, platform, or tech stack. They just need to work with one, and currently, the best option appears to be @TypeScript, for reasons of security, portability, type-safety, and efficiency. Is it any wonder TypeScript is home to some of the most amazing innovations currently happening in AI?