Context Is a Runtime Control, Not a Configuration

Every AI tool today treats context as a setup step. You configure your system prompt, connect your tools, maybe set up a RAG pipeline, and then you use it. The context is fixed. But real work changes minute to minute. You're debugging a Linear ticket now, migrating Stripe data in an hour. The agent doesn't need to know about Stripe while you're debugging Linear. In fact, knowing about Stripe while debugging Linear makes it worse.

Context should work like a mixing board, not a config file. You bring modules in and out of scope as the task changes. The primary user action isn't typing in the chat, it's deciding what the agent can see before you type. What the agent knows determines how well it answers.