Kontekstutvikling er grunnen til at kodingsagenter ikke er de beste til alt. Ta nettleserbruk – kode-agenter beholder DOM-ene fra alle besøkte sider, men du trenger bare de siste få.
Aaron Levie
Aaron Levie24. nov. 2025
We’re starting to get a clearer sign of how vast the surface area of context engineering is going to be. To build AI agents, in theory, it should be as simple as having a super powerful model, giving it a set of tools, having a really good system prompt, and giving it access to data. Maybe at some point it really will be this simple. But in practice, to make agents that work today, you’re dealing with a delicate balance of what to give to the global agent vs. a subagent. What things to make agentic vs. just a deterministic tool call. How to handle the inherent limitations of the context window. You had to figure out how to retrieve the right data for the user’s task, and how much compute to throw at the problem. How to decide what to make fast, and suffer potential quality drops, vs. slow but maybe annoying. And endless other questions. So far there’s no one right answer for any of this, and there are meaningful tradeoffs for any given approach you take. And importantly, getting this right requires a deep understanding of the domain you’re solving the problem for. Handling this problem in AI coding is different from law, which is different from healthcare. This is why there’s so much opportunity for AI agent plays right now.
Mer om dette:
55