Use Memory Across Sessions

Use memory for verified facts that should influence future conversations, not for temporary task progress.

#Supported memory commands

Command	Intent
/remember <text>	Save <text> as a durable project memory.
/memory list	List saved memories for the current project.
/memory add <text>	Save <text> as a project memory.
/memory path	Show where the current project's memories are stored.
/memory delete <memory name>	Remove the saved memory named <memory name>.
/forget	List memories so you can select one to remove.
/forget <memory name>	Remove the saved memory named <memory name>.
/memory clear	Remove every memory for the current project.

#Scenario: preserve the generated-output contract

Command	Intent
/remember <text>	Save the verified generated-output contract as a durable project memory.
/memory list	Confirm that Flux saved the generated-output contract.
/memory path	Find the project's memory directory when you need to inspect it.

The tracker writes the same entries to three outputs. Save that stable convention:

/remember main.py writes deprecations to data/deprecations.json, updates the generated README table, and writes deprecations.ics. Scraper changes must preserve all three outputs.

Inspect the saved entry:

/memory list
/memory path

Exit Flux, reopen it from the same Git repository, and ask:

What outputs must I consider before changing a provider scraper?

Flux should recall the convention because memory is scoped from the Git repository root.

#Remove stale knowledge

Command	Intent
/forget	List memories before choosing the outdated entry.
/forget <memory name>	Remove the specific outdated memory named <memory name>.
/memory clear	Remove all project memories when none should be retained.

If the project stops generating one of those outputs, list the memories and remove the outdated entry:

/forget
/forget <memory name>

Replace <memory name> with the memory name shown in the list; for example, /forget generated-output-contract. Use /memory clear only when every project memory should be removed. Do not save current plan steps, branch names, guesses, or one-off errors.

#Expected result

Future tracker sessions begin with the verified output contract without carrying temporary work forward.

Next: Sessions and Memory.