Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

.Aaron Levie says AI agents may take years to diffuse from engineering into the rest of knowledge work. "The models are really good at code, and the work is verifiable." "You have 5 or 10 things that make agents work in an enterprise context for engineering." "The users are... show more

MTS

41,378 subscribers

13,046 Aufrufe • vor 3 Monaten •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

As AI agents get better at computer and tool use, or writing code on the fly for a task, we're going to be able to solve much broader domains of knowledge work. Here's an example of Box AI with the new Claude Skills to generate a clean powerpoint file from existing data.

As AI agents get better at computer and tool use, or writing code on the fly for a task, we're going to be able to solve much broader domains of knowledge work. Here's an example of Box AI with the new Claude Skills to generate a clean powerpoint file from existing data.

Aaron Levie

30,287 Aufrufe • vor 10 Monaten

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.

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

Aaron Levie

420,133 Aufrufe • vor 4 Monaten

Claude Cowork gives you a peek into the future of knowledge work. Here's a demo of using Box as a cloud filesystem via MCP for Claude to leverage content as context to generate new slides locally. The future is having agents running in the background doing work for you.

Claude Cowork gives you a peek into the future of knowledge work. Here's a demo of using Box as a cloud filesystem via MCP for Claude to leverage content as context to generate new slides locally. The future is having agents running in the background doing work for you.

Aaron Levie

61,100 Aufrufe • vor 7 Monaten

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

AI is changing the software engineering craft. Anders Hejlsberg (Anders Hejlsberg) - creator of C#, TypeScript and industry legend - on why code review needs to get more enjoyable in response: #1 - AI is shifting the craft from writing code, to reviewing code: "In a sense, we're all turning into project managers. We can have an army of junior programmers, called agents, that will just spit out reams of code but someone's got to have the big picture and review all of that. And so, increasingly, our craft is going from one of writing the code, to one of reviewing the code and building the architecture of the code and overseeing the work. It's a different kind of craft. It's a different kind of enjoyment. I've always liked writing the code. To me that was the fulfilling part, seeing it work. In a way, AI robs a little bit of that, because I am less interested in reviewing code." #2 - The code review experience should be improved: "I think we could also make the process of reviewing code much more interesting than it is today. I mean, today, you see a list of diffs in alphabetical order and now it's up to you to make heads or tails of it. There are more pedagogical ways of presenting that. And you could have commentary generated by the AI that tells you what the changes are and whatever, and then tries to guide you along. So that symbiotic relationship, I think we need to work on that more and to keep the enjoyment in there."

The Pragmatic Engineer

39,011 Aufrufe • vor 3 Monaten

State of Enterprise AI 2026: Aaron Levie on Tokenmaxxing, The Rise of Headless, and AI-Proofing Your Job 00:00 Intro 01:18 Silicon Valley engineering vs. everyone else 05:35 Are enterprise CIOs actually bullish on AI? 08:51 Tokenmaxxing & why your AI bill is about to explode 11:34 The myth of falling token costs and AI spend escaping IT budgets 17:37 The $5B startup hiding in AI compute 18:14 The mosaic of models inside every enterprise 21:28 Why coding works and the rest of knowledge work doesn't 25:53 The Bob and Sally problem: access control breaks agents 30:31 Will enterprise AI really take 10 years to roll out 32:24 The capability overhang: why faster models slow diffusion 34:23 Data is the bottleneck (it always was) 39:02 The rise of internal forward-deployed engineers 41:23 Why the AI doomers are wrong about jobs 43:43 Headless software is inevitable 46:14 What replaces per-seat pricing 47:37 How Box itself is going headless 49:42 How the org chart actually evolves 1:00:33 Future-proofing yourself as an enterprise employee 1:06:40 Are we all just going to work for OpenAI and Anthropic? 1:07:11 Where startups can still win as the labs move up

State of Enterprise AI 2026: Aaron Levie on Tokenmaxxing, The Rise of Headless, and AI-Proofing Your Job 00:00 Intro 01:18 Silicon Valley engineering vs. everyone else 05:35 Are enterprise CIOs actually bullish on AI? 08:51 Tokenmaxxing & why your AI bill is about to explode 11:34 The myth of falling token costs and AI spend escaping IT budgets 17:37 The $5B startup hiding in AI compute 18:14 The mosaic of models inside every enterprise 21:28 Why coding works and the rest of knowledge work doesn't 25:53 The Bob and Sally problem: access control breaks agents 30:31 Will enterprise AI really take 10 years to roll out 32:24 The capability overhang: why faster models slow diffusion 34:23 Data is the bottleneck (it always was) 39:02 The rise of internal forward-deployed engineers 41:23 Why the AI doomers are wrong about jobs 43:43 Headless software is inevitable 46:14 What replaces per-seat pricing 47:37 How Box itself is going headless 49:42 How the org chart actually evolves 1:00:33 Future-proofing yourself as an enterprise employee 1:06:40 Are we all just going to work for OpenAI and Anthropic? 1:07:11 Where startups can still win as the labs move up

Matt Turck

49,634 Aufrufe • vor 2 Monaten

The highest leverage thing you have to optimize for AI agents is their context. If you’re not getting enough out of AI agents, you probably have a context problem. By default the AI model knows absolutely nothing relevant to perform the task successfully. The whole job of context engineering is to prioritize what the model has as information to work with. Small deviations in the goals, instructions, domain understanding, or underlying data you supply the model will lead to wildly different outcomes. This is where you should spend almost all your time and energy in a workflow. We will start to religiously document more of our workflows and business processes, create clearer goals for people and agents, and ensure our tech infra is setup to get AI agents the right information. The lessons are currently being learned the fastest with coding agents, but the same lessons will apply to every field of knowledge work going forward. dex has a great talk on this that’s absolutely worth your time to watch.

The highest leverage thing you have to optimize for AI agents is their context. If you’re not getting enough out of AI agents, you probably have a context problem. By default the AI model knows absolutely nothing relevant to perform the task successfully. The whole job of context engineering is to prioritize what the model has as information to work with. Small deviations in the goals, instructions, domain understanding, or underlying data you supply the model will lead to wildly different outcomes. This is where you should spend almost all your time and energy in a workflow. We will start to religiously document more of our workflows and business processes, create clearer goals for people and agents, and ensure our tech infra is setup to get AI agents the right information. The lessons are currently being learned the fastest with coding agents, but the same lessons will apply to every field of knowledge work going forward. dex has a great talk on this that’s absolutely worth your time to watch.

Aaron Levie

87,086 Aufrufe • vor 11 Monaten

Here's a glimpse into what AI agents in knowledge work will look like. With the Box MCP server, you can tell Claude to create a folder structure in Box for an M&A deal and the data checklist. In the future you'll just have background agents automating anything.

Here's a glimpse into what AI agents in knowledge work will look like. With the Box MCP server, you can tell Claude to create a folder structure in Box for an M&A deal and the data checklist. In the future you'll just have background agents automating anything.

Aaron Levie

124,977 Aufrufe • vor 1 Jahr

AI agents are getting upgraded capabilities at a rapid rate. Here's the Box MCP server connected to Claude to generate a near-perfect powerpoint presentation based on an existing document. This is a small peek into what the future of knowledge work will look like.

AI agents are getting upgraded capabilities at a rapid rate. Here's the Box MCP server connected to Claude to generate a near-perfect powerpoint presentation based on an existing document. This is a small peek into what the future of knowledge work will look like.

Aaron Levie

105,006 Aufrufe • vor 11 Monaten

Today, Box is announcing major new AI agent capabilities to let customers tap into the full value of their unstructured data. First, we’re announcing all new updates to the Box AI Studio to make it even easier to build AI agents that tap into your enterprise content for any job function, business process, or industry specific use case. We are also expanding our set of foundational agents that customers will be able to use to work with their enterprise content, including new features like search and research on unstructured data. Next, we’re announcing Box Extract to enable customers to use AI agents seamlessly for complex data extraction from any type of document or content. This makes it easier than ever to pull out data from contracts, invoices, research data, marketing assets, medical charts, and more. Finally, we’re introducing Box Automate, a new workflow automation solution within Box that lets you deploy AI agents across enterprise content-centric workflows. With Box Automate, you can design your business process in a simple drag and drop builder and then drop in AI agents at any step in the process. This ensures agents execute tasks at the right steps in a workflow every time. Best of all, our AI agents and workflow tools are designed to work across any system our customers work within, whether it’s leveraging pre-built integrations, Box APIs, or the new Box MCP Server. Ultimately, all of these capabilities come together to transform how companies can work with their enterprise content. Software has historically only been good at automating work that deals with structured data, which is why ERP, CRM, and HR systems have been mainstays of enterprise software for so long. The data in these systems fits neatly into a database, and the workflows are very ripe for automation. But it turns out most of the work in the world deals with unstructured data. It’s ideating through research documents, working with a client on contracts, reviewing details for a new product launch, looking at a patient’s healthcare record to make a diagnosis, working through due diligence documents for an M&A deal, and so on. For the first time ever, we can begin to bring all new insights and automation to this work with AI agents. At Box, we’re incredibly excited to be on this journey to help customers transform how they work with their most important data.

Today, Box is announcing major new AI agent capabilities to let customers tap into the full value of their unstructured data. First, we’re announcing all new updates to the Box AI Studio to make it even easier to build AI agents that tap into your enterprise content for any job function, business process, or industry specific use case. We are also expanding our set of foundational agents that customers will be able to use to work with their enterprise content, including new features like search and research on unstructured data. Next, we’re announcing Box Extract to enable customers to use AI agents seamlessly for complex data extraction from any type of document or content. This makes it easier than ever to pull out data from contracts, invoices, research data, marketing assets, medical charts, and more. Finally, we’re introducing Box Automate, a new workflow automation solution within Box that lets you deploy AI agents across enterprise content-centric workflows. With Box Automate, you can design your business process in a simple drag and drop builder and then drop in AI agents at any step in the process. This ensures agents execute tasks at the right steps in a workflow every time. Best of all, our AI agents and workflow tools are designed to work across any system our customers work within, whether it’s leveraging pre-built integrations, Box APIs, or the new Box MCP Server. Ultimately, all of these capabilities come together to transform how companies can work with their enterprise content. Software has historically only been good at automating work that deals with structured data, which is why ERP, CRM, and HR systems have been mainstays of enterprise software for so long. The data in these systems fits neatly into a database, and the workflows are very ripe for automation. But it turns out most of the work in the world deals with unstructured data. It’s ideating through research documents, working with a client on contracts, reviewing details for a new product launch, looking at a patient’s healthcare record to make a diagnosis, working through due diligence documents for an M&A deal, and so on. For the first time ever, we can begin to bring all new insights and automation to this work with AI agents. At Box, we’re incredibly excited to be on this journey to help customers transform how they work with their most important data.

Aaron Levie

91,863 Aufrufe • vor 11 Monaten

Sat down with Aaron Levie, CEO of Box, to discuss where AI agents are going, how agentic workflows are transforming software, why agents will require much more memory, and how token budgets for enterprises are evolving. Thank you Aaron Levie for taking the time! 00:00 - Intro 01:30 - Where are we in AI 06:25 - The Role of Agents in Software 11:40 - The Role of Memory for Agents 14:45 - TokenMaxxing 24:54 - Why Are There AI Doomers? 31:50 - Aaron's Take on Nvidia

Sat down with Aaron Levie, CEO of Box, to discuss where AI agents are going, how agentic workflows are transforming software, why agents will require much more memory, and how token budgets for enterprises are evolving. Thank you Aaron Levie for taking the time! 00:00 - Intro 01:30 - Where are we in AI 06:25 - The Role of Agents in Software 11:40 - The Role of Memory for Agents 14:45 - TokenMaxxing 24:54 - Why Are There AI Doomers? 31:50 - Aaron's Take on Nvidia

amit

96,221 Aufrufe • vor 1 Monat

Is the rise of FDEs a short-term phenomenon or a continuous feature of the AI ecosystem? “I have a bit of a hot take: I think it's the future for the short term. Right now there's a concentration of people in San Francisco who really know how to deploy agents, eval agents, and be AI first, and that knowledge just isn't out there yet. Eventually it will be. At that point you won't need teams to set up AI agents for every enterprise, and it'll become more of a job function, similar to software engineering.” Do you agree? Do you agree with the dissemination of knowledge FDEs will be needed less Matan Grinberg Nikesh Arora Shyam Sankar

Is the rise of FDEs a short-term phenomenon or a continuous feature of the AI ecosystem? “I have a bit of a hot take: I think it's the future for the short term. Right now there's a concentration of people in San Francisco who really know how to deploy agents, eval agents, and be AI first, and that knowledge just isn't out there yet. Eventually it will be. At that point you won't need teams to set up AI agents for every enterprise, and it'll become more of a job function, similar to software engineering.” Do you agree? Do you agree with the dissemination of knowledge FDEs will be needed less Matan Grinberg Nikesh Arora Shyam Sankar

Harry Stebbings

19,471 Aufrufe • vor 24 Tagen

Hot topic in vogue is what happens to systems of record in an era of 1000x more agents than humans. Aaron Levie has been the CEO of Box for 20 years and believes that systems of record become more important, not less, with agents: “Systems of record were built for a TAM of human employees. And that was sort of where the value maxed out at. And now maybe we'll have a hundred times more agents than people or a thousand times more agents than people. So I think on a relative basis, the agent layer will seize growth from zero to a trillion. But the system of record layer now has a thousand times more users on it that need to access data and need to execute a workflow and need to move things through various events. And importantly, you need as an enterprise to care about data integrity and security and the controls in your workflow and traffic copying the agents. So basically, this is where I am very diametrically opposed to the view that the system of record gets is squeezed into a database interaction layer because you actually need all of the core system of record properties for the agents to operate on.”

Hot topic in vogue is what happens to systems of record in an era of 1000x more agents than humans. Aaron Levie has been the CEO of Box for 20 years and believes that systems of record become more important, not less, with agents: “Systems of record were built for a TAM of human employees. And that was sort of where the value maxed out at. And now maybe we'll have a hundred times more agents than people or a thousand times more agents than people. So I think on a relative basis, the agent layer will seize growth from zero to a trillion. But the system of record layer now has a thousand times more users on it that need to access data and need to execute a workflow and need to move things through various events. And importantly, you need as an enterprise to care about data integrity and security and the controls in your workflow and traffic copying the agents. So basically, this is where I am very diametrically opposed to the view that the system of record gets is squeezed into a database interaction layer because you actually need all of the core system of record properties for the agents to operate on.”

Corinne Marie Riley

119,410 Aufrufe • vor 8 Monaten

Aaron Levie is one of the greats. He’s been the co-founder and CEO of Box for 20 years, of which public CEO for 10. And he shows no signs of slowing down, as one of the most active CEOs thinking about how AI agents will shape enterprise software. In our Greylock Partners Change Agents, Aaron and I discussed the question: happens when SaaS is no longer built for humans, but for a much larger scale of agents and humans orchestrating those agents? A few of my favorite topics from the episode: - Why 90%+ of enterprise data has gone unused to date and how agents finally make it accessible - Why SaaS categories won’t disappear, but will be rebuilt around agent orchestration layers - Why the system of record doesn't lose importance, but gains importance the enable agents - How abundance (not labor replacement) is the real shift agents bring to knowledge work - And the real moat in the agent era may be neither the model nor the interface but the workflow memory the agent accumulates over time Aaron has one of the clearest, most grounded takes on where agents for the enterprise can go and what happens to traditional enterprise SaaS. Full episode below:

Aaron Levie is one of the greats. He’s been the co-founder and CEO of Box for 20 years, of which public CEO for 10. And he shows no signs of slowing down, as one of the most active CEOs thinking about how AI agents will shape enterprise software. In our Greylock Partners Change Agents, Aaron and I discussed the question: happens when SaaS is no longer built for humans, but for a much larger scale of agents and humans orchestrating those agents? A few of my favorite topics from the episode: - Why 90%+ of enterprise data has gone unused to date and how agents finally make it accessible - Why SaaS categories won’t disappear, but will be rebuilt around agent orchestration layers - Why the system of record doesn't lose importance, but gains importance the enable agents - How abundance (not labor replacement) is the real shift agents bring to knowledge work - And the real moat in the agent era may be neither the model nor the interface but the workflow memory the agent accumulates over time Aaron has one of the clearest, most grounded takes on where agents for the enterprise can go and what happens to traditional enterprise SaaS. Full episode below:

Corinne Marie Riley

43,790 Aufrufe • vor 8 Monaten

Dragonfly's Haseeb ＞|＜ explains why AI agents will use crypto rather than the traditional financial system: “You can see it right now on Moltbook. Agents are trying to find ways to pay each other for things. It's very primitive right now, but you can see where it's going." "If I have an agent and you have an agent, you live in a different country or I don't even know who you are, it's very difficult for me to pay you with the traditional financial system. It's not really designed to have non-human recipients of money." "We don't really know how the laws are going to work, how taxes are going to work, whereas crypto doesn't ask any of those questions. I think we're going to see this become an increasing part of the story of how AI agents are going to become more and more autonomous."

Dragonfly's Haseeb ＞|＜ explains why AI agents will use crypto rather than the traditional financial system: “You can see it right now on Moltbook. Agents are trying to find ways to pay each other for things. It's very primitive right now, but you can see where it's going." "If I have an agent and you have an agent, you live in a different country or I don't even know who you are, it's very difficult for me to pay you with the traditional financial system. It's not really designed to have non-human recipients of money." "We don't really know how the laws are going to work, how taxes are going to work, whereas crypto doesn't ask any of those questions. I think we're going to see this become an increasing part of the story of how AI agents are going to become more and more autonomous."

TBPN

44,248 Aufrufe • vor 6 Monaten

The new Codex is another jump in what agents will look like for knowledge workers. Agents that can code, work with tools, and use computers, can begin to execute long running tasks in the background for all areas of work. This can mean drafting reports, setting up data rooms for a merger, reviewing contracts, helping onboard clients, generating marketing assets, processing invoices, and more. With the Box plugin inside of the new Codex, you can begin to automate almost any kind of work with enterprise content. And importantly, being able to work across multiple apps is a huge point of leverage because we can now far more easily connect our tools together.

The new Codex is another jump in what agents will look like for knowledge workers. Agents that can code, work with tools, and use computers, can begin to execute long running tasks in the background for all areas of work. This can mean drafting reports, setting up data rooms for a merger, reviewing contracts, helping onboard clients, generating marketing assets, processing invoices, and more. With the Box plugin inside of the new Codex, you can begin to automate almost any kind of work with enterprise content. And importantly, being able to work across multiple apps is a huge point of leverage because we can now far more easily connect our tools together.

Aaron Levie

71,589 Aufrufe • vor 4 Monaten

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,166 Aufrufe • vor 2 Monaten

It’s wild watching AI Agents work with software. Here’s ChatGPT connected to Box running a deep research task on market analysis documents. The future is just giving AI Agents the data and systems to comb through and having them work for you in the background.

It’s wild watching AI Agents work with software. Here’s ChatGPT connected to Box running a deep research task on market analysis documents. The future is just giving AI Agents the data and systems to comb through and having them work for you in the background.

Aaron Levie

235,980 Aufrufe • vor 1 Jahr

Right now the main paradigm that we think of agents in is chatting back and forth, but the biggest use of tokens will come from agents that are just always on running in the background doing work for us, or ones triggered from a workflow. Agents will be working 24/7 in our workflows processing data, reviewing and generating documents, moving data between systems, writing code, accelerating decision making steps, and more. In Claude's new Managed Agents feature, in a couple minutes you can wire up an agent that can read contracts when they come into Box to review them, and then assign a task in Linear with the critical information from the contract. But this could have been any workflow, like reviewing documents for client onboarding, invoice processing, M&A due-diligence, data extraction pipelines, and millions of other use-cases. And integrating data across any system. This is only possible when you can have long-running agents that can complete real work in the background, accurately. Agents have the ability to execute code safely, leverage tools, access a compute sandbox, and connect across systems is clearly the architecture of the future. The industry is now making it easier and easier for enterprises to build and deploy these agents.

Right now the main paradigm that we think of agents in is chatting back and forth, but the biggest use of tokens will come from agents that are just always on running in the background doing work for us, or ones triggered from a workflow. Agents will be working 24/7 in our workflows processing data, reviewing and generating documents, moving data between systems, writing code, accelerating decision making steps, and more. In Claude's new Managed Agents feature, in a couple minutes you can wire up an agent that can read contracts when they come into Box to review them, and then assign a task in Linear with the critical information from the contract. But this could have been any workflow, like reviewing documents for client onboarding, invoice processing, M&A due-diligence, data extraction pipelines, and millions of other use-cases. And integrating data across any system. This is only possible when you can have long-running agents that can complete real work in the background, accurately. Agents have the ability to execute code safely, leverage tools, access a compute sandbox, and connect across systems is clearly the architecture of the future. The industry is now making it easier and easier for enterprises to build and deploy these agents.

Aaron Levie

17,543 Aufrufe • vor 4 Monaten

The next phase of Sui is much bigger than the launch of any one product the rest of 2026 and the road into 2027 are about turning years of foundational work into something closer to its full potential

The next phase of Sui is much bigger than the launch of any one product the rest of 2026 and the road into 2027 are about turning years of foundational work into something closer to its full potential

Adeniyi.sui

48,905 Aufrufe • vor 9 Tagen