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 62

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.

How should designers communicate what AI systems truly are and can do? What design and behavioral factors drive false consciousness attribution to AI? What determines appropriate intervention timing and manner for AI agents? How do prompting refinements mask underlying biases and model frequency patterns? How do standardized protocols improve multi-agent coordination and reliability? Does warmth and empathy training systematically degrade model reliability? When should work require human-AI partnership versus full automation? How should agents manage memory granularity to improve long-term performance? Why can't prompting alone inject genuinely new knowledge into models? Should GUI agents use structured representations over raw visual input? How does evaluation scope and dimensionality affect what we measure? What structural properties of attention create systematic model biases? How does dialogue structure affect linguistic grounding and shared meaning? How effectively can language models perform reasoning, especially combined with symbolic methods? How should inference compute be allocated based on problem difficulty? How can humans maintain meaningful oversight as AI systems become increasingly autonomous and complex? What prevents conversational agents from taking initiative in dialogue? How can we prevent synthetic data from contaminating statistical inference and corpora? Why don't LLMs reliably translate capability into accurate outputs? Does AI assistance promote real skill development or substitute for independent learning? Should AI communication design follow human conversation norms or develop distinct machine-specific principles? What reasoning architectures enable models to solve complex problems efficiently? Can compression size predict model complexity better than parameter count alone? Do language models reason like humans or mimic surface patterns? Should agents decouple planning from perception grounding for better performance? Do writers recognize when AI writing assistance alters their expressed stance? How do evaluation practices shape which failures stay visible? Do reasoning benchmarks predict model performance in long-horizon workflows? Why does polished presentation create unearned authority in AI outputs?

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 · 131 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