Chat Thread Context Restoration Across Web Pages and Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing chat-based interactions with generative AI models fail to maintain a holistic context when resumed, as web pages and applications launched during conversations are not restored, leading to an incomplete user experience.

Innovation Solution

Storing data related to web and application activity during conversations and restoring this context when the conversation is resumed, including opening web pages and launching applications as part of the thread's context.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of moving object

If chat-based interactions are resumed after closure, then conversation continuity is improved, but contextual completeness deteriorates because web pages and applications are not restored

Engineering Contradiction:
Improveconversation continuityVSAvoidcontextual completeness
Core Design Contradiction:
Duration of action of moving objectVSLoss of information

Solution Approach 1:

The system performs preliminary actions by storing web page URLs and application identifiers during the active conversation phase. When the conversation is resumed, these pre-stored data enable automatic restoration of the original context without requiring users to manually recreate the environment, thus resolving the contradiction between conversation continuity and contextual completeness

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of the conversation context by storing metadata (URLs, application identifiers) that represent the external resources accessed during the conversation. These copies allow the system to reconstruct the original working environment upon resumption, maintaining both continuity and contextual completeness

Inventive Principle:
Principle #26Copying

2Loss of information

If web pages and applications are tracked during conversations, then contextual completeness is improved, but system complexity increases

Engineering Contradiction:
Improvecontextual completenessVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system extracts only the essential identifying information (URLs and application identifiers) from complex web pages and applications, rather than tracking entire resource states. This extraction approach maintains contextual completeness while minimizing system complexity by focusing on key identifiers that enable resource restoration

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system introduces a context database as an intermediary layer between the chat interface and external resources. This mediator stores and manages references to web pages and applications, simplifying the tracking process by centralizing context management in a dedicated storage mechanism rather than requiring complex integration across multiple systems

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260017329A1Threading chats with application activity
Publication Date: 2026.01.15 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20260017329A1 patent drawing
  • US20260017329A1 patent drawing
  • US20260017329A1 patent drawing

AI summary

Examples relate to systems and methods for restoring threads including context of the threads outside of a chat interface. During a thread including multiple queries and responses, one or more of the responses may include links to web pages and/or to other applications (e.g., presentation applications, word-processing applications). During interactions with the thread, one or more of the links may be selected. The selection of the links causes the corresponding web pages to be loaded and/or the corresponding applications to be launched. The web pages that are opened and/or the applications that are launched during an ongoing thread are stored as thread data for the ongoing thread. Then, when the thread is resumed at a later time, not only is the chat interface populated with the prior queries and responses of the thread, but the web pages and/or applications are also restored.