Feature Request - Temporal Context Awareness Across Multi-Day Conversations for Copilot

Dear Microsoft Copilot Team,

I would like to share small feedback regarding a recurring issue experienced while using Copilot for day-to-day research, drafting, and legal work.

Copilot appears to treat a conversation thread as a single continuous interaction, even when the same chat is resumed after a significant passage of time, including on the following day. As a result, events, discussions, and tasks from prior days are occasionally merged with those of the current day, creating confusion regarding chronology and context.

By way of example, a user may conclude a discussion on one day and resume the same chat thread the following day. However, Copilot may continue to reference events from the previous day as though they had occurred earlier on the same day or assume continuity between separate work sessions without adequately accounting for the intervening passage of time.

While this may appear to be a minor issue, it can have a meaningful impact in professional environments where chronology is critical. In most cases, compliance, and research workflows, dates, timelines, and the sequence of events are often as important as the underlying content itself. When discussions from different days are inadvertently merged, users may need to spend additional time re-establishing the timeline and correcting contextual assumptions before work can continue.

The issue appears to arise from Copilot assigning greater weight to conversational continuity than to temporal continuity. In practice, users often expect a resumed conversation to retain prior context while simultaneously recognizing that a new day represents a new point in time, with new tasks, new developments, and new priorities.

Accordingly, it may be worth considering enhancements that:

1. Give greater weight to date and time metadata when existing conversations are resumed.
2. Clearly distinguish events occurring on different days within the same chat thread.
3. Treat the passage of significant periods of time as a contextual reset factor, while still preserving historical context.
4. Incorporate stronger temporal awareness when generating greetings, summaries, and references to prior discussions.

Copilot remains an exceptionally useful tool for research, drafting, and analytical work. However, improved handling of chronology and temporal context would significantly enhance its effectiveness in professional workflows where accuracy of timelines is essential.

Thank you for your consideration.