# The Context Tax of Agentic Development

DevFeed: [The Context Tax of Agentic Development](<https://devfeed.tech/articles/the-context-tax-of-agentic-development-19738.md>)

Original publisher: [Read original article](<https://medium.com/expedia-group-tech/the-context-tax-of-agentic-development-0bb9de03237c?source=rss----38998a53046f---4>)

Author: A Talhan

Published: 2026-08-25T11:01:02Z

Content type: opinion

Language: en

Sources: [Expedia](<https://devfeed.tech/sources/expedia.md>)

Topics: [Agentic development](<https://devfeed.tech/topics/agentic-development.md>), [Development](<https://devfeed.tech/topics/development.md>), [networking](<https://devfeed.tech/topics/networking.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [agents](<https://devfeed.tech/tags/agents.md>), [context](<https://devfeed.tech/tags/context.md>), [context-engineering](<https://devfeed.tech/tags/context-engineering.md>), [development](<https://devfeed.tech/tags/development.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [networking](<https://devfeed.tech/tags/networking.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [teamwork](<https://devfeed.tech/tags/teamwork.md>)

## AI overview

An Expedia Group engineering team describes how hidden context can cause agentic development to accelerate technically plausible work aimed at the wrong system. Using AI Workbench's multi-environment model handling as an example, the article argues that context must be explicit and structured so humans and agents share the same understanding.

## Source excerpt

Expedia Group Technology -- EngineeringMissing context used to slow a team down, with agents in the loop it speeds up the wrong work insteadPhoto by Harley-Davidson on Unsplash When we started using agents more seriously inside the team, the first bottleneck was not code generation -- It was context coordination. That sounds like a documentation problem, but it did not feel like one. It felt like a delivery problem. A human engineer who is missing context usually slows down. They ask someone, search through old notes, or wait for the next sync. An agent does not always slow down. It can keep moving and produce work that is technically plausible, well formatted, and aimed at the wrong reality. That is the agentic velocity trap: unclear context does not just delay work; it can accelerate the wrong work. Rick Fast recently wrote about the broader Expedia Group™ platform shift toward agent-friendly interfaces and operating surfaces. This is the ground-level version from one team: what did we have to change in our own planning loop so humans and agents could work from the same understanding? The problem was hidden context One of the clearest examples came from multi-environment handling in AI Workbench (our web console for machine learning (ML) artifacts and workload management). From the outside, an AI Workbench URL appeared to represent one backend environment. Under the hood, it was backed by another. A team saw their model in the UI, reasonably assumed it existed in the environment implied by the URL, and then hit "model not found" when downstream jobs queried that expected backend. Internally, the concrete case was a machine learning scientist team onboarding a model. It appeared in the .prodA AI Workbench URL, but that deployment was serving model registry prodB data rather than model registry prodA data. The platform services were not simply broken. The hidden semantic mapping was because of networking and access nuances. That distinction matters. A human team lost