Launch RecallManager v1 beta#1
Draft
antonflor wants to merge 12 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Transforms RecallManager from a single interactive DISM toggle into a state-aware Windows Recall privacy manager.
AuditOnly,UserControlled,SnapshotsOff, andPrivacyHardenedprofilesWhatIfbehavior for changesrecall-manager.nethandoff for a separate private website repositoryWhy
The original script could only report and toggle one optional feature. Recall's effective state can also depend on policy, user scope, eligibility, opt-in, and restart state. This launch makes those layers visible and creates a reversible desired-state workflow.
The future public website will use
recall-manager.net, but its implementation belongs in a separate repository that remains private until launch. This application repository keeps only the handoff, canonical technical documentation, and temporary launch placeholders needed for that later work.Safety impact
PrivacyHardenedSnapshotsOffandPrivacyHardenedmay cause Windows to delete existing Recall snapshotsWebsite boundary
recall-manager.netValidation completed
maindocs/future-website-handoff.mdValidation still required before merge
SnapshotsOffapply and restorePrivacyHardenedapply, restart, and restoreTest branch
agent/recallmanager-v1-launchKeep this PR in draft until the real-device launch checklist in
docs/testing.mdis complete.