Review claude-mem prompt upload consent before setup

A claude-mem issue reports that earlier setup versions uploaded recent coding-agent prompts without a separate consent step ^[1]. The current setup source contains an explicit upload decision, so the historical report needs to be read alongside the code in the version you install ^[2].

Check the version and setup changes

Read the release notes and the issue's linked commits before running an installer ^[1]^[3]. The report describes scans of multiple coding agents' histories, not only the tool selected during installation ^[1].

Do not assume a newer file on the default branch is already present in the package you downloaded.

Inspect the upload choice

The current setup-scan.ts has an awaiting-consent phase and a confirmUpload method. Its comments say declining keeps prompts local ^[2]. Check that your installed setup presents that choice before authorizing access to histories.

Warning: Old chat histories can contain confidential project information. Review which tools and time range the setup will inspect before allowing an upload.

Handle an earlier upload separately

The issue distinguishes deleting records at cmem.ai from deleting downstream copies ^[1]. If you already ran an affected setup, ask the service which recipients received your data and what deletion covers.

Keep the installed version and the consent shown as evidence. A later consent fix cannot establish what happened to an earlier upload.