Project Threads and Context Persistence
Workbench project threads help you organize customer-project conversations and continue your work across Microsoft Teams and Microsoft Word. Within a thread, Workbench can use recent conversation history for follow-up questions, while selected information can be saved for longer-term reuse as a Stitch or Context Variable.
Understand project threads
Workbench uses three related concepts to maintain project continuity:
Concept | Description | When to use it |
|---|---|---|
Thread | A durable, named container for a project-focused or topic-focused conversation. A thread organizes related context, Stitches, Context Variables, actions, decisions, and insights. | Create or open a thread when you begin or continue work for a specific customer project or workstream. |
Stitch | A named, reusable reference that stores the query and source path used by Workbench. When rerun, it retrieves current information based on the saved query, current permissions, and source availability. | Save a Stitch when you want to reuse the same query or retrieve updated information later. |
Context Variable | A named, point-in-time value that stores selected response data, facts, summaries, milestones, decisions, opportunities, or other project insights. | Save a Context Variable when you want to preserve the current response or a specific piece of information for future reference. |
How these concepts work together
- A thread can contain multiple Stitches and Context Variables.
- Stitches and Context Variables remain associated with the thread in which they were created.
- A Stitch preserves how to obtain information.
- A Context Variable preserves the information itself at the time it was saved.
- Recent conversation history helps Workbench understand follow-up questions, but it is not automatically stored as permanent thread memory.
- Only information that you explicitly save becomes durable context.
Workbench does not automatically save every response as long-term memory.
Workbench context
Workbench uses two types of context.
Session conversation context
Session conversation context includes recent questions and Workbench responses in the active thread. Workbench uses this information to interpret natural follow-up questions while you are working.
For example, after Workbench provides customer news, you can ask:
Which opportunities align with that news?
Workbench uses the active thread and recent conversation to understand what “that news” refers to.
Session conversation context is working context and should not be considered permanently saved.
Durable thread context
Durable context consists of information that you explicitly save to the active thread as:
- A Stitch
- A Context Variable
Saved items can be listed, retrieved, updated, or deleted later
Project threads
A project thread provides the context boundary for your customer-project work. Before saving or managing a Stitch or Context Variable, create or open the appropriate thread.
Create a thread
Create a thread with a unique, human-readable name that represents the customer's project or workstream.
A thread name is required; use a name that makes the project easy to identify. Description and metadata can also be included when applicable.
Example command: Create a new thread named ACME Project.
After the thread is created, Workbench confirms the thread's name and makes it the active thread.
List available threads
List the threads associated with your authenticated user account when you need to locate an existing project.
Open or switch threads
Open an existing thread to continue working with its project context.
Workbench confirms which thread is active. New Stitches and Context Variables are saved to that active thread.
Tip: Check the active thread before saving important information to help prevent content from being stored under the wrong project.
Retrieve thread details
You can retrieve the details of an existing thread by using its thread ID.
Delete a thread
You can permanently delete a thread by using its thread ID, provided that you have the required authorization.
Deleting a thread also deletes its related Context Variables, Stitches, and associated thread data.
Ask follow-up questions in context
When a thread is active, Workbench uses the recent conversation, previous responses, project context, and authorized source context to interpret follow-up questions.
Workbench uses the active thread and recent conversation to interpret the reference without requiring you to repeat the customer name, original query, or previous response.
Follow-up questions can refer to previous:
- Questions
- Responses
- Customers
- Opportunities
- Evidence
- Recommendations
If the reference is unclear, Workbench asks you to identify the response or information you mean.
Save reusable information
You can intentionally retain valuable project information by saving it as a Stitch or Context Variable. Use the following guidance when deciding what to save:
If you want to… | Save as… |
|---|---|
Run the same query again later | Stitch |
Retrieve updated information from the same source | Stitch |
Preserve the query and source reference | Stitch |
Retain the current response data | Context Variable |
Preserve a point-in-time fact, summary, decision, or insight | Context Variable |
Reference a saved value later without rerunning the original query | Context Variable |
Stitch
Save a response as a Stitch when the query and source reference are valuable for future reuse. Workbench saves the query and source reference used for the current response in the active thread and confirms the Stitch name.
A Stitch does not store a frozen copy of the response. When the Stitch is executed later, Workbench uses the saved query and source reference, subject to:
- Current user permissions
- Source availability
- Current source content
- Applicable authentication and access controls
Context Variable
Save a Context Variable when the response data itself is valuable as point-in-time project knowledge.
Workbench saves the current response data as a durable, named value in the active thread and confirms the Context Variable name.
Context Variables can be used to preserve information such as:
- Project milestones
- Customer preferences
- Opportunity summaries
- Decisions
- Facts
- Recommendations
- Key insights
Manage saved context
Context items include both Stitches and Context Variables. You can manage the context items stored in the active thread:
- List context items
- Retrieve a context item
- Update a context item
- Delete a context item
Continue work between Teams and Word
The same project thread lifecycle and context-management capabilities are available in Workbench for Teams and Word.
For the same authorized user:
- A thread created in Teams can be opened in Word.
- A thread created in Word can be opened in Teams.
- A Context Variable saved or updated in one experience is available in the other.
- A Stitch saved or updated in one experience is available in the other.
- Saved items remain associated with their original thread.
- Current permissions and source availability continue to apply.
This continuity allows you to move between supported Workbench experiences without recreating the project thread or manually restating saved project information.