Skip to content

feat: polluted memories#13008

Merged
jif-oai merged 4 commits intomainfrom
jif/mcp-kill-memories
Mar 2, 2026
Merged

feat: polluted memories#13008
jif-oai merged 4 commits intomainfrom
jif/mcp-kill-memories

Conversation

@jif-oai
Copy link
Copy Markdown
Collaborator

@jif-oai jif-oai commented Feb 27, 2026

Add a feature flag to disable memory creation for "polluted"

@jif-oai
Copy link
Copy Markdown
Collaborator Author

jif-oai commented Feb 27, 2026

@codex review

Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0fa571cbe3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

}
};
let mut metadata = outcome.metadata;
let memory_mode = outcome.memory_mode.unwrap_or_else(|| "enabled".to_string());
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Preserve memory_mode when reconcile lacks rollout metadata

Do not default to "enabled" here. For rollouts without session_meta.memory_mode (legacy files, or threads later marked polluted only in DB), this path overwrites the current DB value and re-enables memory generation. A read-repair/reconcile can therefore silently undo disabled/polluted state.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't do

);
}
let mut metadata = outcome.metadata;
let memory_mode = outcome.memory_mode.unwrap_or_else(|| "enabled".to_string());
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid forcing enabled mode during backfill replay

Backfill now defaults missing rollout memory_mode to "enabled" and writes it back unconditionally. On any backfill pass over legacy rollouts, existing threads.memory_mode values can be clobbered, causing polluted/disabled threads to become eligible for stage1/phase2 processing again.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't happen

Copy link
Copy Markdown
Contributor

@wendyjiao-openai wendyjiao-openai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jif-oai jif-oai merged commit b649953 into main Mar 2, 2026
52 of 55 checks passed
@jif-oai jif-oai deleted the jif/mcp-kill-memories branch March 2, 2026 11:57
@github-actions github-actions bot locked and limited conversation to collaborators Mar 2, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

2 participants