Project memory
Decisions you make are remembered for the project, so the Copilot does not undo them.
Always use 0603 passives on this board
"Use the 0805 version." "Keep USB on the left." Decisions like these are stored with the project and recalled in later conversations, so a new request does not quietly reverse an earlier choice. Older decisions are superseded, not deleted, so the history stays readable.
What it does
Per project
Memory lives beside the project file, not in a cloud account.
Decisions and constraints
Requirements, constraints, corrections and preferences each have a place.
History kept
A changed decision supersedes the old one instead of erasing it.
Full transcripts
Every conversation is kept; summaries only shorten what the model is sent.
Facts that outlive the chat
The Copilot keeps durable facts per project — requirements, constraints, decisions, corrections and preferences — and they survive closing the chat, starting a new session and reopening the project. /memory lists what the project has established, each with an id; /remember pins a fact the Copilot must not forget, such as "/remember no electrolytic capacitors"; /forget drops one by its id.
Decisions are superseded, not erased
A newer decision about the same subject replaces the older one, but the history is kept, so what was decided before is still there to read. An applied /fix is recorded the same way, so a later run does not undo it.
Your hand edits count as decisions too
Once a design is on the sheet, every edit on the undo stack carries who made it. Change a value, delete a part or move a pin to another net, and the change is carried back into the plan and reported in the chat. The agents are told what you changed and never to undo it — in testing, a fix on a net disconnected on purpose made the agent ask whether to reconnect it rather than wire it back.
The details
| Commands | /memory · /remember <text> · /forget <id> |
|---|---|
| Kinds of fact | Requirements · constraints · decisions · corrections · preferences |
| Scope | The project, across every conversation about it |
| History | Newer facts supersede older ones; the older ones are kept |
How to start
- Work with the Copilot as usual; applied fixes are recorded.
- State a preference in the chat to make it a project decision.
- Ask what was decided about a part to see the history.
Questions
Is this memory shared between projects?
No — it belongs to the project. What is learned about a part, its electrical contract, belongs to the part and is reused on every board that uses it.
How do I make the Copilot forget something?
Run /memory to see the facts with their ids, then /forget the id.
Do I need a paid plan?
It comes with the Max and Pro plans, on the plan's monthly AI credit. The Free plan has the design tools and no AI Copilot.