# Separate user-visible UI state from model-visible context

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Separate user-visible UI state from model-visible context

ID: MHC-D-RESEARCH-1174 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/separate-user-visible-ui-state-from-model-visible-context

What the user can see and what the model must receive are different design decisions.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An interactive AI tool shows rich application state but the model does not need every displayed field to continue the task.

### Avoid when

- Client implementations and protocol features differ. Verify the actual host's context-sharing behavior rather than assuming a privacy boundary exists.

### Explanation

Define which UI changes must return to the model, which can stay local to the interactive component and which require explicit user action before sharing. This can reduce context noise and unnecessary exposure while keeping the interface useful.

### Example

A planning widget can display all editable form fields to the user while sending only the changed date and selected option back to the model.

### Check

Every model-visible UI update has a task reason; rich display state is not copied into context by default.

### Limits

- Client implementations and protocol features differ. Verify the actual host's context-sharing behavior rather than assuming a privacy boundary exists.

### Evidence and sources

- supports: Interactive agent applications can separate information displayed to the user from information sent back into the model context. — RS-ECDEF17A94432233. Exact MCP App capabilities vary by client and protocol revision; privacy still depends on the host and tool implementation honoring the boundary. (10:01-16:36, application messages, streamed inputs and separation of user-visible state from model-visible context)
- RS-ECDEF17A94432233: MCP Apps: Primitives, Discovery, and the Future of Software — https://ai.engineer/talks/sAOBXCDiDOs-mcp-apps-primitives-discovery-future-software

No review details supplied.
