3 ms·
> On the Usage Data side, your code is never stored anywhere other than your machine when you use Memex. And you can enable "Privacy mode" to not have your prom
by tough 2y ago
> On the Usage Data side, your code is never stored anywhere other than your machine when you use Memex. And you can enable "Privacy mode" to not have your prompts stored either.
It would be nice if there's some kind of auto-censoring of secrets if sharing code etc, cursor handling of this is very bad bc if I block .env files, then i can't never add them as context and it thinks they dont exist, instaed of knowing they're secrets and to be treated as such.
hoping a less binary solution for controlling what gets shared and not is possibe
- davidvgilmore 2y agoThat's a good feature idea and something we've considered but not gotten around to yet. We do have a secrets mgmt feature that uses keyring, so you can store secrets through the app in your system keychain, which then requires your approval before Memex uses it. We're hoping to make that feature easier to use with MCP