fixes mem0 with valkey/redis issue

[MatthiasHowellYopp]

changes to support using mem0 with valkey/redis as external memory provider for crewai

fixes #4031

---

Note

Medium Risk
Changes request shaping for Mem0 search filters with provider-specific behavior, which could alter query results for Valkey/Redis users; test coverage is expanded to reduce regressions.

Overview
Fixes Mem0Storage search filters for local Mem0 vector stores that don’t support nested AND/OR filter structures (Valkey/Redis) by flattening single-condition AND filters to a plain dict, while leaving multi-condition/OR filters and cloud MemoryClient behavior unchanged.

Adds targeted tests covering Valkey/Redis flattening, non-flattening cases, None config edge cases, and the cloud-vs-local guard; also updates pytest setup to reset the last event id between tests for better isolation.

^{Written by Cursor Bugbot for commit 7a255c9. This will update automatically on new commits. Configure here.}

[Vidit-Ostwal]

Hey @MatthiasHowellYopp, maybe you can collapse all the commits into one for a cleaner git history

Try this

git checkout feature-branch
git reset --soft main
git commit -m "Add <feature-name>"
git push --force-with-lease

I am not a maintainer, feel free to ignore this...

[greysonlalonde]

Hey @MatthiasHowellYopp, maybe you can collapse all the commits into one for a cleaner git history

Try this

git checkout feature-branch
git reset --soft main
git commit -m "Add <feature-name>"
git push --force-with-lease

I am not a maintainer, feel free to ignore this...

This would be great!

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[MatthiasHowellYopp]

@greysonlalonde changes done, looks like I need you (or someone) to let the checks run.

[MatthiasHowellYopp]

@greysonlalonde can you review - or recommend someone who can? tks.

[MatthiasHowellYopp]

@greysonlalonde Can we try again? looks lIke I need workflow approval and a review.

[MatthiasHowellYopp]

@greysonlalonde Is there something I can do to get this to the other side of merged? Seems I'm back to needing the checks permitted.

[MatthiasHowellYopp]

@greysonlalonde Can you approve the awating workflows, please?

[MatthiasHowellYopp]

fixes #4030

[MatthiasHowellYopp]

no longer relevant

[Vidit-Ostwal]

no longer relevant

[MatthiasHowellYopp]

working on a version that works with the new memory architecture.

[Vidit-Ostwal]

working on a version that works with the new memory architecture.