Gemini Memory Settings: View, Add, and Update Saved Context

Find Gemini memory settings on the web under Settings & help, then Personal context or Personal Intelligence, depending on your screen. Review Memory separately from your instructions and Activity: those controls concern different ways information is retained or used, and your account may not show every option.

For project requirements that need a reviewed home, fenbs keeps the work record outside personal memory. You can maintain that record alongside Gemini’s settings without expecting Gemini to remember every approved decision or unfinished task.

How do you find the controls for your account?

1. Open Gemini in a browser and confirm the Google Account you intend to use. Check whether it is a personal account or one managed by work or school.
2. Open Settings & help, then Personal context or Personal Intelligence, using the label your screen shows. Review the Memory control if it is available.
3. Look for Your instructions for Gemini or Instructions for Gemini in the same area; some interfaces use Saved info. On mobile, follow the help page for your platform rather than assuming the web menu is identical.
4. Open Activity separately when you want to review saved conversations or activity retention. Decide what you want to change before changing several controls at once.

Google’s past-chat memory guide↗ (opens in a new tab) documents the web path and current eligibility. A missing switch does not by itself prove your information was deleted. Compare the account and feature you are using with the relevant documentation.

Make a short note of your starting settings before making changes. This helps you recognize which adjustment affected a test. Use a harmless preference, such as a preferred answer format, rather than client information to check the result.

What is the difference between memory, instructions, and activity?

These are different questions even when the interface places the controls close together. A saved conversation is not automatically an approved instruction. A preference about answer length is not a reliable place for the current status of a proposal.

For the broader capability, see the Gemini memory feature guide.

Imagine a student using Gemini for several courses. A preference for worked examples could help broadly. A professor’s specific requirements belong with the assignment, where the student can verify the current version before submitting any work.

The same separation helps teams: AI memory for teams concerns shared work that personal settings alone cannot organize.

How do you add, edit, or remove instructions?

Google’s instruction management guide↗ (opens in a new tab) describes opening your instructions, choosing Add, entering the guidance, and submitting it. Use the entry’s More menu to edit or delete it. The same area has an on/off control for using instructions; match the menu labels to your screen.

Write one clear instruction at a time so you can review its effect. “Begin explanations with a short summary, then give the steps” is easier to test than a long paragraph mixing tone, personal background, and rules for unrelated projects. Remove obsolete guidance when your needs change.

• Choose preferences that remain useful across different conversations.
• Give enough detail to recognize success, such as the expected structure of an explanation.
• Keep project-specific approvals and source documents with the project.
• Review the saved text after editing so the previous instruction does not remain as a conflicting entry.

For example, replace “Explain everything for my beginner class” when that course ends. A new instruction could say “Ask which level I need when the topic is unfamiliar.” The point is to make the preference accurate rather than accumulate a history of every preference you ever had.

How should you correct remembered information?

Where the remembered-facts feature is available, Google documents correcting an outdated fact directly in chat. Its eligibility differs from simply adding instructions, so follow the current help page rather than assuming every account has the same controls. State the corrected fact plainly and review a later answer.

Make the correction specific. “I now want explanations for an intermediate reader” is clearer than “Stop forgetting what I like.” If the change applies only to one task, say that explicitly instead of asking for a preference that would affect unrelated work.

Test in a fresh conversation using a question where the preference should matter. Ask what earlier context contributed if the answer surprises you. Keep the result modest: one successful answer checks that example, not every future use of memory.

A project correction should also reach the authoritative record. If a person changes the approved scope, record who made that choice and what it replaces. fenbs Decisions and rules keep that approval separate from a personal preference or an assistant’s suggestion.

What changes when you edit activity settings?

Google’s activity management guide↗ (opens in a new tab) explains how to review and delete Gemini Apps Activity and manage Keep Activity. It also distinguishes personal-account controls from settings managed by a Workspace administrator. Use that guide for activity changes instead of treating instruction deletion as a history reset.

For information drawn from previous conversations, Google’s memory guide directs you to delete chats containing it; stopping use can involve a delay. If connected-app information is involved, review both the past chats and the app connection. Changing just one source may leave the other available.

Before changing retention, decide whether your goal is to stop personalization, remove a particular conversation, or change saved instructions. Those actions have different effects. The Gemini Privacy Hub↗ (opens in a new tab) is the primary reference for data handling; a settings change should match your actual goal.

Do not test a deletion by repeatedly typing the information you want removed. That adds the same detail back into the current discussion. Keep any troubleshooting note free of the private information itself and record only which setting or source you checked.

How to do this with fenbs

1. Create a free account, free for one person with no credit card, and add a project that needs continuing context.
2. Add the current tasks and a short context note. Include the goal, approved source references, and any uncertainty the next session should know.
3. Record human-approved choices in Decisions and rules. Keep personal preferences in the assistant where you manage them, and project requirements with the work.
4. Connect a supported assistant using Integrations. For Google’s supported connection, follow the Gemini CLI guide; do not assume the consumer Gemini memory screen connects to fenbs.
5. Ask that assistant to read the project context before starting and save progress before stopping. Review Where we left off before the next task.

fenbs does not edit Gemini’s memory settings or import its saved information. If your whole need is a personal answer-style preference, Gemini’s own controls may be sufficient. Use a separate work record when approved decisions and task progress need an inspectable home.

Our Gemini vs. ChatGPT comparison and Claude vs. Gemini guide cover broader assistant choices. The AI memory hub covers the related context questions without making one app’s personal settings responsible for your whole project.