SYNTHESIS NOTE
Topics›this note

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.

Synthesis note · 2026-04-14

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 read this note 92

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

What makes agent memory systems durable and reusable across sessions? Why do language models struggle to implement user intent accurately from prompts? How do philosophical assumptions about AI consciousness affect practical harms and design? How should agents coordinate through shared persistent code artifacts? How can emotionally responsive AI maintain reliability and healthy boundaries? What design features sustain romantic bonds with AI companion systems? Do individually safe AI actions create unsafe outcomes in integrated systems? What are the fundamental limits of prompting for language models? Should GUI agents use structured screen representations instead of end-to-end vision? What explains the gap between benchmark scores and true reasoning capability? What structural biases does transformer attention architecture inherently introduce? What enables conversational agents to guide rather than just respond? Why do confident AI outputs mislead human trust calibration? Does augmenting symbolic reasoning improve LLM logical reasoning ability? Can inference-time computation adaptively substitute for static model capacity? How should human-AI contributions be measured, disclosed, and verified? How should humans and AI agents share control and decision-making? How does AI adoption reshape collaboration patterns in knowledge work? How do hallucinated citations emerge in AI scholarly output? What limits language model accuracy in evaluating ideas? Does AI assistance help or harm professional skill development? How should AI agents balance proactive engagement with conversational respect? Should governance of agentic AI systems be runtime or design-time? Can smaller specialized models match frontier models on key metrics? How can persistent memory architectures preserve information across ultra-long contexts? What prevents LLMs from applying their reasoning knowledge to improve outputs? How do writers navigate authorship and delegation with AI? Why do standard evaluation practices obscure safety-critical AI failures? Does AI-assisted work increase total productivity or just shift time? How do users confuse explanation quality with actual system accuracy? Can AI systems achieve real improvement without external human feedback? Do AI coding tools measurably improve developer productivity and code quality? How do clinicians calibrate trust in AI medical recommendations? Can readers reliably distinguish AI-written text from human writing? Can AI research automation sustain progress through accelerating feedback loops? How do AI systems determine and balance multiple competing objectives? How can AI systems reliably guide voters without introducing political bias?

Related concepts in this collection 3

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
15 direct connections · 133 in 2-hop network ·medium cluster Open in graph ↗
How does AI context differ from conventional sof… Is the LLM a tool or a new form of intelligence it… Why does AI output change with every prompt and co… Why don't conversational AI systems mirror their u…

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Search by related questions 4

Suggested questions this note speaks to — click to search the collection, or type your own.

Can designers hide AI context complexity behind a stable user interface?What design discipline replaces navigation and layout in AI systems?Why do conventional mental models fail when applied to AI interaction?How should designers make invisible AI state legible to users?
Original note title

context in AI is mutable dynamic and ephemeral unlike the fixed stable context conventional software provides