Prerequisites
To complete this Quick Guide, you’ll need:
The Pieces Desktop App installed and actively running on your device.
Long-Term Memory enabled in the Pieces Desktop App.
Optional—Pieces installed in a Python IDE, such as the VS Code Extension, or the JetBrains PyCharm Plugin.
In This Quick Guide
This Quick Guide will show you how to combine the Pieces Long-Term Memory with code context in a Pieces Copilot chat, demonstrating how you can use AI to help implement a feature in a Python app.
As a developer, a common daily task is reviewing a ticket in a tool like GitHub Issues or Jira and then implementing it in a codebase.
This often involves switching back and forth between the code and the ticket, which can affect your productivity due to constant context switching.
With Pieces, you can use the Long-Term Memory feature to remind you of the ticket details. You can then combine this with your code, allowing Pieces to guide you on implementing the issue, all from within your IDE!
Review a GitHub Issue
The first step is to review the issue by letting Pieces capture it, and then ask the Pieces Copilot about it.
```plaintext
Summarize the create a sign up page issue I was just reading
```
Pieces will respond with a summary of the issue:

Clone the Project
This issue refers to a sci-fi store—a small web application written in Python and Flask for an upcoming retail store that sells themed sci-fi toys.
If you use an IDE like VS Code or JetBrains PyCharm, open this folder in that IDE.
Use the Project as Context
The next step is to add the project as context to the Pieces Copilot chat. This lets you link the project to the Long-Term Memory and ask questions about the code.
Adding the project as context to your Pieces Copilot Chat will look a little different depending on whether you’re using the Pieces Desktop App or an IDE with the respective Pieces plugin or extension installed,such as VS Code.
From the `Manage Copilot Context | Folders` dialog, select `Add Folders`.
Select the `scifi_store` folder in the repository you cloned in the previous step.
<Image src="https://storage.googleapis.com/hashnode_product_documentation_assets/quick_guides/using_pieces_copilot_with_memory_context/new_media/scifi_store_selected_folder.png" alt="" align="center" fullwidth="true" />
<Image src="https://storage.googleapis.com/hashnode_product_documentation_assets/quick_guides/using_pieces_copilot_with_memory_context/new_media/in_ide_folder_Add_scifi.png" alt="" align="center" fullwidth="true" />
Prompt Pieces Copilot
Now that Pieces has the issue from the Long-Term Memory and the project folder as context, you can ask Pieces to implement this issue.
```plaintext
How can I implement this issue in this project?
```
The response will contain relevant instructions on how to implement this issue, such as code for the endpoint, the new page leveraging the existing app templates, and so on.
Review these code changes along with the original codebase.
<Image src="https://storage.googleapis.com/hashnode_product_documentation_assets/quick_guides/using_pieces_copilot_with_memory_context/new_media/asking_to_fix.png" alt="" align="center" fullwidth="true" />
Bonus—Try One Prompt
This Quick Guide showed two prompts: one to get the details about the issue and another to learn how to implement it.
This was done in 2 stages to illustrate the information from the Pieces Long-Term Memory, but is unnecessary. You can do this in a single prompt!
```plaintext
How can I implement the create a sign up page issue I was just reading in this Python project?
```
<Image src="https://storage.googleapis.com/hashnode_product_documentation_assets/quick_guides/using_pieces_copilot_with_memory_context/new_media/extra_example.png" alt="" align="center" fullwidth="true" />