Mixed-Initiative Context: Structuring and Managing Context for Human-AI Collaboration
Organizations: George Mason University Fairfax, Virginia, USA · University of California, San Diego San Diego, California, USA · City University of Hong Kong Hong Kong, China
Abstract
In the human-AI collaboration area, the context formed naturally through multi-turn interactions is typically flattened into a chronological sequence and treated as a fixed whole in subsequent reasoning, with no mechanism for dynamic organization and management along the collaboration workflow. Yet these contexts differ substantially in lifecycle, structural hierarchy, and relevance. For instance, temporary or abandoned exchanges and parallel topic threads persist in the limited context window, causing interference and even conflict. Meanwhile, users are largely limited to influencing context indirectly through input modifications (e.g., corrections, references, or ignoring), leaving their control neither explicit nor verifiable. To address this, we propose Mixed-Initiative Context, which reconceptualizes the context formed across multi-turn interactions as an explicit, structured, and manipulable interactive object. Under this concept, the structure, scope, and content of context can be dynamically organized and adjusted according to task needs, enabling both humans and AI to actively participate in context construction and regulation. To explore this concept, we implement Contextify as a probe system and conduct a user study examining users' context management behaviors, attitudes toward AI initiative, and overall collaboration experience. We conclude by discussing the implications of this concept for the HCI community.
Figures & tables
Appendix figures & tables2 assets
Supplementary material from the paper’s appendix.
Appendix
| ID | Background | Prior structured conversation experience | Prior node-based experience |
|---|---|---|---|
| P1 | PhD student in STEM (non-CS) with solid technical practice in research settings; moderate AI use for literature reading, information organization, and coding support | Some exposure to branching-style interaction; found existing support too coarse-grained for fine context work | Limited platform experience |
| P2 | Master’s student in humanities/social sciences; mainly used AI for casual chat and retrieval-style Q&A, with occasional lightweight content generation | Little to no exposure to structured conversation features; limited sense of their utility | No platform experience |
| P3 | PhD student in STEM; relatively frequent AI use for research problem understanding, concept clarification, and implementation-related tasks | No stable habit of using explicit conversation structure; often managed context by starting new chats | Not familiar with node-based interaction |
| P4 | HCI PhD student with publications at top-tier HCI venues; intensive daily AI use (often 10 hours/day) for information acquisition and system development | Prior exposure to branching-style and structured conversation workflows; found existing support limited in flexibility and convenience | Prior experience with multiple node-based products and prototypes |
| P5 | Member of Technical Staff (MTS) at a North American company focused on large language model systems; deep daily AI use for coding, system building, and technical debugging | Strong context-management needs in daily work, but no prior use of dedicated structured-conversation features | No mature platform experience; familiar with structured tools such as flowcharts |
| P6 | Product lead with product development and UI/UX practice, with multiple shipped products; deep AI use for brainstorming and vibe coding | Prior experience with branching-style workflows for managing conversations | Prior experience with node-based platforms (e.g., Coze) |