chore(docker): disable Mem0 telemetry in container config by Aureliolo · Pull Request #531 · Aureliolo/synthorg

Aureliolo · 2026-03-17T22:25:06Z

Summary

Set MEM0_TELEMETRY=false in Docker compose, CLI compose template, and .env.example
Mem0's telemetry initializes an extra vector store to stage usage data before shipping to Mem0's servers — disabling it reduces startup overhead and keeps all data local
Identified during review of PR chore: bump the minor-and-patch group across 1 directory with 2 updates #527 (mem0ai 1.0.5 → 1.0.6), which fixed telemetry vector store init still running when MEM0_TELEMETRY is disabled

Changes

docker/.env.example — added MEM0_TELEMETRY=false with documentation comment
docker/compose.yml — added MEM0_TELEMETRY: "false" to backend environment
cli/internal/compose/compose.yml.tmpl — added MEM0_TELEMETRY: "false" to CLI-generated compose
cli/testdata/compose_*.yml — updated 3 golden files to match template

Test plan

Go CLI compose generation tests pass (go test ./internal/compose/)
go vet ./... clean
Full Go test suite passes
CI passes

Set MEM0_TELEMETRY=false in Docker compose, CLI template, and .env.example. Mem0's telemetry initializes an extra vector store to stage usage data before shipping to Mem0's servers — disabling it reduces startup overhead and keeps all data local.

github-actions · 2026-03-17T22:25:15Z

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

coderabbitai · 2026-03-17T22:25:19Z

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b8c50aaa-88dd-4160-9db9-4ed9488962be

📥 Commits

Reviewing files that changed from the base of the PR and between a602cf7 and fdc6d72.

📒 Files selected for processing (1)

docker/compose.yml

📝 Walkthrough

Summary by CodeRabbit

Chores
- Telemetry is disabled by default across deployment and local Docker configurations via a new environment setting. This adds a configurable flag that can be overridden to enable telemetry if desired.

Walkthrough

Adds a new environment variable MEM0_TELEMETRY=false to backend service definitions and examples across docker-compose templates and related files.

Changes

Cohort / File(s)	Summary
Compose template `cli/internal/compose/compose.yml.tmpl`	Inserted `MEM0_TELEMETRY: "false"` into the backend service environment block.
Compose testdata `cli/testdata/compose_custom_ports.yml`, `cli/testdata/compose_default.yml`, `cli/testdata/compose_digest_pins.yml`	Added `MEM0_TELEMETRY: "false"` to backend environment in all test compose fixtures.
Docker env and compose `docker/.env.example`, `docker/compose.yml`	Added `MEM0_TELEMETRY=false` to `.env.example` (with comment) and `${MEM0_TELEMETRY:-false}` entry in `docker/compose.yml` backend environment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

chore(docker): disable Mem0 telemetry in container config #531 — Makes the same change adding MEM0_TELEMETRY=false to backend environment in compose files.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: disabling Mem0 telemetry in container configuration. It is directly related to the changeset and specific enough to understand the primary modification.
Description check	✅ Passed	The description is well-structured and directly related to the changeset, providing context about the motivation (reducing startup overhead), the changes made across multiple files, and the test status.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch chore/disable-mem0-telemetry

✨ Simplify code

Create PR with simplified code
Commit simplified code in branch chore/disable-mem0-telemetry

📝 Coding Plan

Generate coding plan for human review comments

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

gemini-code-assist · 2026-03-17T22:25:21Z

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the Docker container configuration by explicitly disabling Mem0 telemetry. This change is crucial for optimizing application startup performance and reinforcing data privacy by ensuring that no additional vector stores are initialized for telemetry data collection, keeping all operational data local to the deployment.

Highlights

Telemetry Disablement: The MEM0_TELEMETRY environment variable is now explicitly set to "false" across Docker Compose configurations and templates.
Performance and Data Locality: Disabling Mem0's telemetry prevents the initialization of an extra vector store for usage data, reducing startup overhead and ensuring all data remains local.
Contextual Fix: This change addresses an issue identified during the review of PR chore: bump the minor-and-patch group across 1 directory with 2 updates #527, where telemetry vector store initialization could still occur even when telemetry was intended to be disabled.

Changelog

cli/internal/compose/compose.yml.tmpl
- Added MEM0_TELEMETRY: "false" to the backend service environment.
cli/testdata/compose_custom_ports.yml
- Updated the golden file to reflect the telemetry setting.
cli/testdata/compose_default.yml
- Updated the golden file to reflect the telemetry setting.
cli/testdata/compose_digest_pins.yml
- Updated the golden file to reflect the telemetry setting.
docker/.env.example
- Added MEM0_TELEMETRY=false with a comment explaining its purpose.
docker/compose.yml
- Added MEM0_TELEMETRY: "false" to the backend service environment.

Activity

Go CLI compose generation tests passed.
go vet ./... clean.
Full Go test suite passed.
CI passes (pending).

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request disables Mem0 telemetry by default across Docker configurations, which is a good change for privacy and performance. The implementation is mostly correct, but I've found one area for improvement in docker/compose.yml where the configuration is hardcoded, preventing users from easily overriding it. My suggestion makes the setting configurable via the .env file, which is a common practice in docker-compose setups.

gemini-code-assist · 2026-03-17T22:26:31Z

docker/compose.yml

+      # Disable Mem0 telemetry (extra vector store init overhead).
+      MEM0_TELEMETRY: "false"


Hardcoding MEM0_TELEMETRY to "false" prevents users from overriding this setting in their .env file, because environment values in docker-compose.yml override values from an env_file. To allow for user configuration, it's better to use Docker Compose variable substitution. This provides a default while still allowing overrides, which is a more flexible approach.

# Disable Mem0 telemetry by default. Override in .env to enable. MEM0_TELEMETRY: "${MEM0_TELEMETRY:-false}"

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docker/compose.yml`:
- Around line 22-23: The environment variable MEM0_TELEMETRY is set to the
lower-case string "false" which does not match Mem0's documented expected value;
change the value for the MEM0_TELEMETRY entry to use a capitalized "False" so
Mem0 will correctly interpret telemetry as disabled (update the MEM0_TELEMETRY
value in the docker compose service definition).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c0f03980-f1e8-4001-8572-5603e2eb92a2

📥 Commits

Reviewing files that changed from the base of the PR and between 0715910 and a602cf7.

📒 Files selected for processing (6)

cli/internal/compose/compose.yml.tmpl
cli/testdata/compose_custom_ports.yml
cli/testdata/compose_default.yml
cli/testdata/compose_digest_pins.yml
docker/.env.example
docker/compose.yml

📜 Review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

GitHub Check: Build Backend
GitHub Check: Build Web
GitHub Check: CLI Test (windows-latest)
GitHub Check: CLI Test (macos-latest)
GitHub Check: Analyze (python)

🧰 Additional context used

📓 Path-based instructions (1)

docker/compose.yml

📄 CodeRabbit inference engine (CLAUDE.md)

docker/compose.yml: Docker image versions are tagged from pyproject.toml via [tool.commitizen].version (semver + SHA). Use git tags for release versions (v*)
All Docker Compose services must be defined in docker/compose.yml. Use .env.example for environment variable documentation

Files:

docker/compose.yml

🧠 Learnings (1)

📚 Learning: 2026-03-17T22:03:39.493Z

Learnt from: CR
Repo: Aureliolo/synthorg PR: 0
File: CLAUDE.md:0-0
Timestamp: 2026-03-17T22:03:39.493Z
Learning: Applies to docker/compose.yml : All Docker Compose services must be defined in `docker/compose.yml`. Use `.env.example` for environment variable documentation

Applied to files:

docker/compose.yml

🔇 Additional comments (5)

docker/.env.example (1)

36-40: LGTM — well-documented environment variable.

Clear explanation of what the telemetry setting does and why it's disabled by default. This follows the coding guideline to use .env.example for environment variable documentation.

cli/testdata/compose_custom_ports.yml (1)

18-18: LGTM — testdata file updated consistently with template.

cli/testdata/compose_digest_pins.yml (1)

18-18: LGTM — consistent with template and other golden files.

cli/testdata/compose_default.yml (1)

18-18: LGTM — default golden file updated consistently.

cli/internal/compose/compose.yml.tmpl (1)

18-18: LGTM — hardcoding the telemetry disable is appropriate.

Using a static value rather than a template variable makes sense since this is a deliberate default policy (keep data local, reduce overhead) rather than a user-configurable option.

coderabbitai · 2026-03-17T22:28:56Z

docker/compose.yml

+      # Disable Mem0 telemetry (extra vector store init overhead).
+      MEM0_TELEMETRY: "false"


⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

mem0ai MEM0_TELEMETRY environment variable disable telemetry

💡 Result:

To disable Mem0 (mem0ai) telemetry, set the environment variable MEM0_TELEMETRY to False (do this before initializing/using Mem0). [1]

Shell

export MEM0_TELEMETRY=False

Python

import os os.environ["MEM0_TELEMETRY"] = "False"

[1]

Sources

[1] Mem0 Docs – FAQs (section “How do I disable telemetry in Mem0?”) (docs.mem0.ai)

Citations:

1: https://docs.mem0.ai/platform/faqs

Fix value casing to match Mem0 documentation.

The variable name MEM0_TELEMETRY is correct, but according to Mem0's official documentation, the value should be "False" (capital F), not "false". In Python, the string "false" is truthy (non-empty string), which may prevent telemetry from actually disabling. Update line 23 to:

Suggested fix

MEM0_TELEMETRY: "False"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed. In `@docker/compose.yml` around lines 22 - 23, The environment variable MEM0_TELEMETRY is set to the lower-case string "false" which does not match Mem0's documented expected value; change the value for the MEM0_TELEMETRY entry to use a capitalized "False" so Mem0 will correctly interpret telemetry as disabled (update the MEM0_TELEMETRY value in the docker compose service definition).

Allow users to override the default (false) via .env file. Hardcoded environment values in compose override env_file.

🤖 I have created a release *beep* *boop* --- ## [0.3.2](v0.3.1...v0.3.2) (2026-03-17) ### Features * **settings:** route structural data reads through SettingsService ([#525](#525)) ([289f604](289f604)) ### Bug Fixes * **cli:** add fallback arch detection in PowerShell installer ([#529](#529)) ([0250afb](0250afb)), closes [#521](#521) ### CI/CD * bump the minor-and-patch group with 2 updates ([#517](#517)) ([46bdd1a](46bdd1a)) * bump wrangler from 4.73.0 to 4.74.0 in /.github in the minor-and-patch group ([#511](#511)) ([903b71a](903b71a)) ### Maintenance * bump node from `7a4ef57` to `44bcbf4` in /docker/sandbox ([#515](#515)) ([3cbddd1](3cbddd1)) * bump python from `6a27522` to `584e89d` in /docker/backend ([#513](#513)) ([0715910](0715910)) * bump python from `6a27522` to `584e89d` in /docker/sandbox ([#514](#514)) ([787dfe1](787dfe1)) * bump the minor-and-patch group across 1 directory with 2 updates ([#527](#527)) ([e96c0d4](e96c0d4)) * bump the minor-and-patch group across 2 directories with 3 updates ([#512](#512)) ([b95ba3d](b95ba3d)) * **docker:** disable Mem0 telemetry in container config ([#531](#531)) ([9fc29eb](9fc29eb)) * improve GitHub issue templates with structured forms ([#528](#528)) ([4fb66cf](4fb66cf)), closes [#522](#522) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).

gemini-code-assist bot reviewed Mar 17, 2026

View reviewed changes

coderabbitai bot requested changes Mar 17, 2026

View reviewed changes

fix(docker): use variable substitution for MEM0_TELEMETRY

fdc6d72

Allow users to override the default (false) via .env file. Hardcoded environment values in compose override env_file.

Aureliolo merged commit 9fc29eb into main Mar 17, 2026
37 of 38 checks passed

Aureliolo deleted the chore/disable-mem0-telemetry branch March 17, 2026 22:38

Aureliolo mentioned this pull request Mar 17, 2026

chore(main): release 0.3.2 #530

Merged

coderabbitai bot mentioned this pull request Mar 17, 2026

fix(cli): add fallback arch detection in PowerShell installer #529

Merged

4 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(docker): disable Mem0 telemetry in container config#531

chore(docker): disable Mem0 telemetry in container config#531
Aureliolo merged 2 commits intomainfrom
chore/disable-mem0-telemetry

Aureliolo commented Mar 17, 2026

Uh oh!

github-actions bot commented Mar 17, 2026 •

edited

Loading

Uh oh!

coderabbitai bot commented Mar 17, 2026 •

edited

Loading

Review failed

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Uh oh!

gemini-code-assist bot commented Mar 17, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Mar 17, 2026

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot Mar 17, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

		# Disable Mem0 telemetry (extra vector store init overhead).
		MEM0_TELEMETRY: "false"

Conversation

Aureliolo commented Mar 17, 2026

Summary

Changes

Test plan

Uh oh!

github-actions bot commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Dependency Review

Scanned Files

Uh oh!

coderabbitai bot commented Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review failed

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Uh oh!

gemini-code-assist bot commented Mar 17, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

github-actions bot commented Mar 17, 2026 •

edited

Loading

coderabbitai bot commented Mar 17, 2026 •

edited

Loading