Keep project decisions when you switch agents.
Say a decision once. Winskel keeps it in Project Memory and gives it to
Claude Code and
Codex before they start.
How a decision travels
Say it
State it in chat, such as "Remember that new tests go in the tests folder", or add it in Settings, Context and memory.
It is kept
Winskel answers in the chat that it kept the fact in Project Memory. No objective is created.
Both agents get it
Before a run starts, Winskel adds a short brief to the request, so
Claude Code and
Codex start from the same decisions.Change your mind
Say the new decision, such as "Actually, use npm instead." It replaces the old fact, which stays in the history.
What each run receives
The brief is kept short, and its parts stay labeled, so a guess never reads as a fact.
- From you
- Facts you wrote or approved, and your decisions, with their dates.
- Observed by Winskel
- Earlier requests and what Winskel saw happen: the model that ran, the commit, and the checks that passed.
- Unfinished
- Work that is still waiting, such as a result that is not in your project folder yet.
- Agents' notes
- What an agent reported that nobody has accepted, labeled unverified.
Yours to correct, forget or limit
- Correct
- A correction replaces the old fact. For settings with one value, such as the package manager or the test command, the new decision replaces the old one instead of leaving two.
- Forget
- Forget a fact and its text is removed. A forgotten fact reaches no agent.
- Choose who receives it
- Send each fact to
Claude Code,
Codex or both. Settings, Context and memory shows what was sent. - What memory cannot do
- It cannot change permissions, security rules or a provider's restrictions. Text that looks like a key, token or password is refused and never stored.