How does AI context differ from conventional software context?
Explores whether the ephemeral, session-by-session nature of AI context requires fundamentally different design approaches than the stable interfaces users internalize in traditional software.
A spreadsheet's context is its rows, columns, formulas, and toolbar. A user learns this context once and operates within it for years. The context is fixed across sessions, identical across users, persistent across uses. Software UX practice evolved within this assumption: design a stable context users can internalize, then design interactions within that context. Information architecture, navigation, mental models — all presuppose a fixed substrate.
AI changes this substrate. The context of an AI interaction is what is in the model's working window at the moment of generation: prompt, system instructions, retrieved documents, conversation history, persistent memory if any, tool outputs. Each of these can change between turns. The context for turn N is not the context for turn N+1. The user cannot internalize the context the way they internalize a UI, because the context is being constructed and reconstructed in real time, often invisibly.
This has three design consequences. First, mental models built on stable substrate fail. Users who expect "the AI" to remember things consistently are operating with a software-era assumption that does not hold. Second, the unit of design shifts from "the interface" to "the context as it evolves" — context engineering becomes the design substrate, not navigation or layout. Third, the design surface includes things users cannot see (system prompts, retrieved chunks, hidden state) — making the context legible to users becomes a design problem of its own.
Context-engineering tools are emerging as the practitioner response: prompt structure, memory management, retrieval orchestration, tool integration. These are not extensions of UI; they are a different design discipline whose object is the model's evolving working window rather than the user's screen. The discipline has no analog in conventional UX, which means existing UX competencies do not transpose without translation. Designers entering AI work need to learn what they are designing in addition to learning new patterns.
The strongest counterargument: a sufficiently good agent will hide the context and present the user a stable interface. Possible at the margin, but stability requires either constraining the AI's capability (defeating its flexibility) or solving every memory and consistency problem that has so far resisted solution. The mutable context is not a temporary state of the technology; it is a structural property of generative interaction.
Inquiring lines that use this note as a source 50
This note is a source for these synthesized inquiries. Follow a line forward into its question, or open it to trace back to all of its sources.
- Does state persistence in AI systems create the same temporal presence as human waiting?
- How do users perceive attention from systems that lack continuous temporal presence?
- Can timing and context awareness reduce the cognitive cost of AI suggestions?
- Can better AI interfaces eliminate the attention cost of prompt composition and evaluation?
- What role does user interface framing play in consciousness perception?
- How much does autonomous action without prompting affect user perception?
- Why do rigid orchestration frameworks fail where generative environment specifications succeed?
- Why do AI model updates cause genuine grief in users?
- What role do material artifacts play in solidifying AI relationships?
- Why do persistent companion designs require different safety approaches than temporary assistants?
- What memory and planning capabilities do AI companions need for evolving user needs?
- How does prompt optimization differ from building persistent activation context?
- What execution feedback signals drive context updates without supervision labels?
- What design discipline replaces navigation and layout in AI systems?
- Can designers hide AI context complexity behind a stable user interface?
- How should designers make invisible AI state legible to users?
- Can contextual design decisions resist formalization into evaluation rubrics?
- What does attentional state look like in a static context window?
- How does AI's inability to sustain temporal attention limit its capacity for expert roles?
- What second- and third-order interpretations actually govern AI adoption decisions?
- How does API-first interaction compare to generative interface approaches?
- Can prompt engineering overcome the gulf between user intent and AI interpretation?
- Does the absence of entrainment make AI systems safer from user manipulation?
- What design signals help users know when AI is acting on their behalf?
- Can algorithmic control flow over prompts simulate traditional programming languages?
- How does precomputing context reasoning reduce latency in stateful applications?
- Why do a-priori procedural specifications fail as environments change and interfaces evolve?
- How should systems design transparency to make human-machine contribution boundaries visible?
- Can prompt engineering close the gap between AI structure and evaluative commitment?
- Why do AI models treat user intent as binary rather than evolving?
- Which AI capabilities matter most for human-facing deployment contexts?
- How does rising AI capability change what users expect from their tools?
- What ecosystem conditions beyond technical capability determine whether users adopt AI features?
- Can intellectual property law apply to unfixed, context-dependent outputs?
- Why does single-turn Q&A framing not match real user deployment patterns?
- Why does context work differently in AI than in conventional software?
- Can users adapt their competencies to match how AI actually operates?
- How should AI interfaces signal their non-communicative nature to users?
- How does machine agency spectrum explain tool design mismatches with user behavior?
- Can interface design scaffold human participation in tools designed for hands-off autonomy?
- Why does sandboxed execution matter more than monolithic prompting?
- Does encoding governance into runtime loops scale as deployment environments become more complex?
- What concrete governance structures could embed oversight into AI systems at runtime?
- Why do high-level design guidelines fail to capture real-world deployment nuance?
- When should architects prioritize consolidation compute over larger context windows?
- How does externalizing tacit expertise into structured rules differ from prompt engineering?
- How does context engineering bridge human intent and machine understanding?
- Why is digital context more volatile than conventional software context?
- How does external context control compare to agents managing their own state internally?
- What design changes could reduce unhelpful AI reliance in collaborative writing tools?
Related concepts in this collection 3
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Is the LLM a tool or a new form of intelligence itself?
Does framing AI as merely delivering pre-existing intelligence miss what's actually happening? This explores whether the model itself constitutes a fundamentally new intelligence-medium with distinct cultural effects.
the medium-theoretic claim that context-as-substrate follows from
-
Why does AI output change with every prompt and context?
Explores whether the variability of AI-generated intelligence across contexts and audiences is a fundamental feature or a flaw to be fixed. Examines what this mutability means for how we should evaluate and understand AI systems.
companion mutability claim at the output level
-
Why don't conversational AI systems mirror their users' word choices?
Explores whether current dialogue models exhibit lexical entrainment—the human tendency to align vocabulary with conversation partners—and what's needed to bridge this gap in AI communication.
a specific consequence of mutable context for dialogue
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- A Survey of Context Engineering for Large Language Models
- Context Engineering 2.0: The Context of Context Engineering
- Agentic Context Engineering: Evolving Contexts for Self-Improving Language Models
- Canvil: Designerly Adaptation for LLM-Powered User Experiences
- Bridging the gulf of envisioning: Cognitive design challenges in llm interfaces.
- Real-Time Procedural Learning From Experience for AI Agents
- Externalization in LLM Agents: A Unified Review of Memory, Skills, Protocols and Harness Engineering
- Large Language Models for User Interest Journeys
Original note title
context in AI is mutable dynamic and ephemeral unlike the fixed stable context conventional software provides