🚧

This feature is in Limited Preview. Please contact your account team for access.

What is a Context Window?

Moveworks Copilot has a short-term memory, which we refer to as its context window. This allows the copilot to remember recent interactions, ensuring responses are relevant and based on the ongoing dialogue. This allows the Copilot to adapt its response to user queries with the most recent information from the previous conversation, and ensures that the user gets a conversational and situation-aware response.

As a result, if two users ask the same question, or if the same user asks a question twice at different times, it is expected that the responses may be somewhat different based on the context. Note that the Copilot does not have a hard time-based cutoff for the context, but retains the last few interactions, allowing a user to ask contextual questions even if there is a gap after the last interaction.

When testing that the Moveworks Next Gen Copilot performs optimally across different scenarios, it’s important to understand when to clear the context window. This is crucial to ensure that any tests accurately mimic real-world scenarios. Ultimately, the decision of when to clear the context window depends on the goals of the testing.

How to clear your context window

Important: This feature is in Limited Preview. Please contact your account team for access.

To clear your context window, simply type copilot clearhistory into your Copilot.

✅ When to clear your context window

1. Testing Plugin Triggering: When testing that the Copilot serves the specific plugin, it’s often useful to start with a clean slate to ensure past interactions & previous plugin selections from the bot do not affect the bot’s current decision. To solve this, and allow for better understanding of plugin selection, you can run copilot clearhistory to ensure prior interactions do not affect the response.
   1. Note that plugin selection is done by the reasoning engine dynamically and if there are multiple plugins that are potentially capable of serving the request, there can be some variation in which plugin gets selected. Clearing context does not eliminate this variation, if it exists.
2. Irrelevant Context Accumulation / Error Correction: When the context accumulated is incorrect or no longer relevant to the ongoing conversation, and you do not want the copilot to leverage it, you can run copilot clearhistory to ensure prior interactions do not affect the subsequent responses.

The most important thing to remember is that users’ experience will be based on their context. So any testing with the use of copilot clearhistory will not capture those effects. When analyzing usage from your users, you should expect to see some differences from testing with cleared context.

❌ When to not clear your context window

1. Context Switching: If a user shifts to an entirely different topic that requires a fresh contextual understanding. It is expected that the nextgen copilot can naturally transition to new topic changes.
2. Leveraging previous inputs to maintain conversation flow: In scenarios where past inputs are crucial for the Copilot to make sense of the current request or query.
   • e.g: when chaining actions together e.g: Lookup of Status of a Record -> Update it to “in process”
3. Leveraging previous language context to minimize repetition: When testing a conversation that benefits from continuity, and to avoid users having to repeat information they have already provided, the context window helps the AI maintain the flow and understand references from prior messages, such as pronouns in subsequent conversations.
   • e.g: “How many offices do we have in San Francisco?” -> “Where are they located?”

Limitations

This tool does not eliminate variations that are not related to previous conversation context. As an example, sometimes more than one plugin (e.g. knowledge and forms) may have a potential option to show to the user. In such cases, the Copilot currently selects one of the plugins, and the plugin selection may be dynamic. Clearing context does not eliminate this source of variation. If you see that the Copilot is selecting other plugins more frequently than expected, please file a support ticket or speak with your CS team to discuss the use and possible options to modify the behavior.