Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for...

OrenMe's profile picture

Oren Melamed

2,557 subscribers

29,555 görüntüleme • 5 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

You told us you’re running multiple AI agents and wanted a better UX. We listened and shipped it! Here’s what’s new in the latest Visual Studio Code release: 🗂️ Unified agent sessions workspace for local, background, and cloud agents 💻 Claude and Codex support for local and cloud agents 🔀 Parallel subagents 🌐 Integrated browser And more...
1:09

You told us you’re running multiple AI agents and wanted a better UX. We listened and shipped it! Here’s what’s new in the latest Visual Studio Code release: 🗂️ Unified agent sessions workspace for local, background, and cloud agents 💻 Claude and Codex support for local and cloud agents 🔀 Parallel subagents 🌐 Integrated browser And more...

Visual Studio Code

586,771 görüntüleme • 4 ay önce

Introducing multi-agent orchestration in Oz, with support for Claude Code, Codex and the Warp Agent. Use /orchestrate to delegate complex tasks across a team of agents, locally or in the cloud.
2:17

Introducing multi-agent orchestration in Oz, with support for Claude Code, Codex and the Warp Agent. Use /orchestrate to delegate complex tasks across a team of agents, locally or in the cloud.

Warp

1,184,772 görüntüleme • 26 gün önce

Postman is going all-in on AI! Their AI Agent Builder is live (and it's pretty powerful!) Postman's API Network has 100,000+ APIs and they just released a suite of tools for building AI Agents that can automatically discover and connect to any of these APIs. Think about it for a second: You can now build an AI agent that searches the network, discovers an API, processes its documentation, connects to it, and evaluates whether everything worked at the end of the process. This is a huge deal. Every person I know uses the Postman client to work with APIs. Now, they will have access to the AI Agent Builder, a complete suite for designing, building, testing, and deploying agents. I've built a few simple agents myself, and it's tough. The ability to discover and use an API automatically is really exciting (and a huge time saver if it works as promised!) In collaboration with the Postman team, who is sponsoring this post, I recorded a video with my thoughts about the Postman AI Agent Builder.
3:38

Postman is going all-in on AI! Their AI Agent Builder is live (and it's pretty powerful!) Postman's API Network has 100,000+ APIs and they just released a suite of tools for building AI Agents that can automatically discover and connect to any of these APIs. Think about it for a second: You can now build an AI agent that searches the network, discovers an API, processes its documentation, connects to it, and evaluates whether everything worked at the end of the process. This is a huge deal. Every person I know uses the Postman client to work with APIs. Now, they will have access to the AI Agent Builder, a complete suite for designing, building, testing, and deploying agents. I've built a few simple agents myself, and it's tough. The ability to discover and use an API automatically is really exciting (and a huge time saver if it works as promised!) In collaboration with the Postman team, who is sponsoring this post, I recorded a video with my thoughts about the Postman AI Agent Builder.

Santiago

230,532 görüntüleme • 1 yıl önce

HERMES JUST FIXED THE BIGGEST PROBLEM WITH BROWSER AGENTS Most AI agents still click around websites like confused interns. This new setup gives them the map. Hermes + → Hermes now connects to Browserbase’s new Browse hub → Browse launched with 100+ browser skills → Each skill is a plain-text playbook for a specific website or task → Your agent can search, preview, and install skills inside Hermes Why This Matters: ✓ Less random clicking ✓ Fewer timeouts ✓ Better form filling ✓ More reliable website navigation ✓ Skills can be edited, reused, bundled, and shared The Real Stack: → Hermes runs the agent → Browserbase handles cloud browser infrastructure → gives the agent site-specific skills → Vision helps when pages get weird → Bundles let you load repeat workflows faster The killer detail: If a website breaks, you don’t wait for the model to magically improve. You update the skill. Now your agent gets better forever. That’s the difference between an AI tool and an actual agent system.
8:19

HERMES JUST FIXED THE BIGGEST PROBLEM WITH BROWSER AGENTS Most AI agents still click around websites like confused interns. This new setup gives them the map. Hermes + → Hermes now connects to Browserbase’s new Browse hub → Browse launched with 100+ browser skills → Each skill is a plain-text playbook for a specific website or task → Your agent can search, preview, and install skills inside Hermes Why This Matters: ✓ Less random clicking ✓ Fewer timeouts ✓ Better form filling ✓ More reliable website navigation ✓ Skills can be edited, reused, bundled, and shared The Real Stack: → Hermes runs the agent → Browserbase handles cloud browser infrastructure → gives the agent site-specific skills → Vision helps when pages get weird → Bundles let you load repeat workflows faster The killer detail: If a website breaks, you don’t wait for the model to magically improve. You update the skill. Now your agent gets better forever. That’s the difference between an AI tool and an actual agent system.

Julian Goldie SEO

43,063 görüntüleme • 21 gün önce

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.
2:14

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,582 görüntüleme • 2 ay önce

Tempo's Dan Romero explains why the future of AI agents will be "stablecoin-native." John: "Why wouldn't I just give OpenClaw my credit card?" Dan Romero: "The credit card itself is kind of a private key, having that get prompt-injected out, maybe not the best thing in the world." “If you have agent swarms, the idea of spinning up a new credit card for each individual sub-agent doesn’t make sense. With wallets, you can spin up as many as you want and manage the balances for each agent.” “An API call to any of these frontier labs right now is pay-per-call. You’re eventually going to get to a point where, for every single API call, you can just pay some amount of stablecoins in the background and keep moving.”
1:39

Tempo's Dan Romero explains why the future of AI agents will be "stablecoin-native." John: "Why wouldn't I just give OpenClaw my credit card?" Dan Romero: "The credit card itself is kind of a private key, having that get prompt-injected out, maybe not the best thing in the world." “If you have agent swarms, the idea of spinning up a new credit card for each individual sub-agent doesn’t make sense. With wallets, you can spin up as many as you want and manage the balances for each agent.” “An API call to any of these frontier labs right now is pay-per-call. You’re eventually going to get to a point where, for every single API call, you can just pay some amount of stablecoins in the background and keep moving.”

TBPN

41,311 görüntüleme • 3 ay önce

Tempo's Dan Romero explains why the future of AI agents will be "stablecoin-native." John: "Why wouldn't I just give OpenClaw my credit card?" Dan Romero: "The credit card itself is kind of a private key, having that get prompt-injected out, maybe not the best thing in the world." “If you have agent swarms, the idea of spinning up a new credit card for each individual sub-agent doesn’t make sense. With wallets, you can spin up as many as you want and manage the balances for each agent.” “An API call to any of these frontier labs right now is pay-per-call. You’re eventually going to get to a point where, for every single API call, you can just pay some amount of stablecoins in the background and keep moving.”
1:39

Tempo's Dan Romero explains why the future of AI agents will be "stablecoin-native." John: "Why wouldn't I just give OpenClaw my credit card?" Dan Romero: "The credit card itself is kind of a private key, having that get prompt-injected out, maybe not the best thing in the world." “If you have agent swarms, the idea of spinning up a new credit card for each individual sub-agent doesn’t make sense. With wallets, you can spin up as many as you want and manage the balances for each agent.” “An API call to any of these frontier labs right now is pay-per-call. You’re eventually going to get to a point where, for every single API call, you can just pay some amount of stablecoins in the background and keep moving.”

TBPN

155,348 görüntüleme • 4 ay önce

File systems are quickly becoming a core abstraction for AI agents for knowledge work. By having access to a file system, agents can effectively manage context, process any amount of information, and create new files and data. The challenge is that local file systems are inherently limited in size, lack governance capabilities, and are inherently personal -not collaborative- in nature. Now, with the Box API and LangChain's deepagent SDK, you can bring the full power of a secure, collaborative cloud file system to your AI agents. Repo ↓
0:37

File systems are quickly becoming a core abstraction for AI agents for knowledge work. By having access to a file system, agents can effectively manage context, process any amount of information, and create new files and data. The challenge is that local file systems are inherently limited in size, lack governance capabilities, and are inherently personal -not collaborative- in nature. Now, with the Box API and LangChain's deepagent SDK, you can bring the full power of a secure, collaborative cloud file system to your AI agents. Repo ↓

Box

227,222 görüntüleme • 4 ay önce

Finally, a proper chat UI for Hermes Agent (open-source)! Hermes ships an official dashboard, but it's primarily built for management, and its chat is just a terminal piped into a browser tab. Hermes Web UI is an open-source chat-first alternative. It's self-hosted and points at your existing ~/.hermes state, so there's nothing new to configure. - It's a native web chat, not a terminal in a tab - Sessions group by date with a context ring - Kanban renders the agent's task board - Spaces manages your workspaces - Skills panel lists the full catalog - Tasks panel shows cron jobs - Insights show usage and activity - Memory shows MEMORY and SOUL files - Logs tails the agent, gateway, and error logs The whole setup runs 100% locally, binds to localhost by default, and you reach it over an SSH tunnel or Tailscale from your phone. I have shared the Hermes Web UI GitHub repo in the replies. Do note that it's a community project, not official, so expect occasional rough edges (concurrent profile runs are blocked for now). To dive deeper into Hermes Agent, my co-founder wrote a full masterclass about it, covering the learning loop, the memory tiers, self-evolving skills, GEPA, and running multiple isolated agents. Read it below.
0:23

Finally, a proper chat UI for Hermes Agent (open-source)! Hermes ships an official dashboard, but it's primarily built for management, and its chat is just a terminal piped into a browser tab. Hermes Web UI is an open-source chat-first alternative. It's self-hosted and points at your existing ~/.hermes state, so there's nothing new to configure. - It's a native web chat, not a terminal in a tab - Sessions group by date with a context ring - Kanban renders the agent's task board - Spaces manages your workspaces - Skills panel lists the full catalog - Tasks panel shows cron jobs - Insights show usage and activity - Memory shows MEMORY and SOUL files - Logs tails the agent, gateway, and error logs The whole setup runs 100% locally, binds to localhost by default, and you reach it over an SSH tunnel or Tailscale from your phone. I have shared the Hermes Web UI GitHub repo in the replies. Do note that it's a community project, not official, so expect occasional rough edges (concurrent profile runs are blocked for now). To dive deeper into Hermes Agent, my co-founder wrote a full masterclass about it, covering the learning loop, the memory tiers, self-evolving skills, GEPA, and running multiple isolated agents. Read it below.

Avi Chawla

75,866 görüntüleme • 15 gün önce

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.
1:18

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

50,822 görüntüleme • 11 gün önce

I wanted to share a quick demo of what we've been working on with our ai agent cloud. This enables fast deployment of agents that have access to a suite of tools, and was designed with agent interoperability in mind. This demo shows how you can go from nothing to an AI twitter agent in a couple minutes. This is what we are using internally to manage deployments, so we will consistently upgrading its capabilities. The next goals are to enable simple TEE deployments for agents, and focus on building out feature for agent interoperability to simplify agent to agent collaboration.
4:16

I wanted to share a quick demo of what we've been working on with our ai agent cloud. This enables fast deployment of agents that have access to a suite of tools, and was designed with agent interoperability in mind. This demo shows how you can go from nothing to an AI twitter agent in a couple minutes. This is what we are using internally to manage deployments, so we will consistently upgrading its capabilities. The next goals are to enable simple TEE deployments for agents, and focus on building out feature for agent interoperability to simplify agent to agent collaboration.

Johnny

26,738 görüntüleme • 1 yıl önce

happy friday. sneak peek at some new features i'm building for the bankr agent: > sandboxed filesystem (your agent gets its own secure file system in the browser. you control what it can access. no agent running loose on your actual computer) > skill uploads (plugin new capabilities so your agent learns new things) > cli download & access > secure environment variables for api keys > github integration (connect your repo for reads and writes directly from your agent) all of this runs in a secure browser environment. no desktop app. no messy configuration. no downloading agent harnesses from the terminal. just a sandbox you control. in the video: i download an audit skill, run it against a smart contract, and save the report straight to the filesystem. then i ask the agent to pull all my 2026 transactions and write a csv for my accountant.
0:58

happy friday. sneak peek at some new features i'm building for the bankr agent: > sandboxed filesystem (your agent gets its own secure file system in the browser. you control what it can access. no agent running loose on your actual computer) > skill uploads (plugin new capabilities so your agent learns new things) > cli download & access > secure environment variables for api keys > github integration (connect your repo for reads and writes directly from your agent) all of this runs in a secure browser environment. no desktop app. no messy configuration. no downloading agent harnesses from the terminal. just a sandbox you control. in the video: i download an audit skill, run it against a smart contract, and save the report straight to the filesystem. then i ask the agent to pull all my 2026 transactions and write a csv for my accountant.

deployer

45,631 görüntüleme • 2 ay önce

Preview of our DeepResearchSwarm™ It's incomprehensibly fast as it leverages a multi-agent architecture instead of just one agent. It utilizes a joint hierarchical-parallel architecture that creates a plan and then concurrently executes the plan with multiple search agents. Workflow: Task → Research Director → multiple search agents → final summary by summarization agent. Stay tuned for the release ↓
1:09

Preview of our DeepResearchSwarm™ It's incomprehensibly fast as it leverages a multi-agent architecture instead of just one agent. It utilizes a joint hierarchical-parallel architecture that creates a plan and then concurrently executes the plan with multiple search agents. Workflow: Task → Research Director → multiple search agents → final summary by summarization agent. Stay tuned for the release ↓

swarms

17,729 görüntüleme • 1 yıl önce

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch
58:55

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

374,753 görüntüleme • 2 ay önce

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

419,721 görüntüleme • 1 ay önce

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base
1:47

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base

Malte Ubl

124,713 görüntüleme • 5 ay önce

For 40 years the file browser hasn’t changed. Today, we’re launching with $8 million in seed funding to rebuild the file browser into something more intelligent, searchable, and delightful. The world is in the middle of a data explosion. We’re generating and using more files than ever, but the apps we’re using to manage our files don’t even understand them. It’s time for file browsers to become useful. When you search for “dog”, it should show you content with dogs in it, not just files with “dog” in the name! When you want to edit, convert, summarize, or organize a file, your browser should do that, too. Your files tell the story of your life, but when you need a specific one, you usually can’t even find it anymore. Why can’t your file browser find it for you, or cross-reference it when you have a question? Prompting can give an LLM a million tokens of context. With Poly, you can give it the next trillion. As long as we can afford it, all new users receive 100GB of free cloud storage. We can’t wait for you to try it out!
1:25

For 40 years the file browser hasn’t changed. Today, we’re launching with $8 million in seed funding to rebuild the file browser into something more intelligent, searchable, and delightful. The world is in the middle of a data explosion. We’re generating and using more files than ever, but the apps we’re using to manage our files don’t even understand them. It’s time for file browsers to become useful. When you search for “dog”, it should show you content with dogs in it, not just files with “dog” in the name! When you want to edit, convert, summarize, or organize a file, your browser should do that, too. Your files tell the story of your life, but when you need a specific one, you usually can’t even find it anymore. Why can’t your file browser find it for you, or cross-reference it when you have a question? Prompting can give an LLM a million tokens of context. With Poly, you can give it the next trillion. As long as we can afford it, all new users receive 100GB of free cloud storage. We can’t wait for you to try it out!

Abhay Agarwal

1,775,909 görüntüleme • 6 ay önce

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11
43:20

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

Dan Shipper 📧

66,256 görüntüleme • 1 ay önce

Cloud agents and automations now support multi-repo environments. Configure a single environment with all the repos an agent needs, and reuse it across sessions.
0:44

Cloud agents and automations now support multi-repo environments. Configure a single environment with all the repos an agent needs, and reuse it across sessions.

Cursor

46,988 görüntüleme • 1 ay önce