To be 100% clear: we do not prevent anyone from using Memex to build a Memex competitor. That clause was boilerplate our lawyers included, and it doesn't reflect how we operate or what we intend to enforce. I should have caught it and we'll fix it.
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
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
That's a great reply and hoping for it to give memex a try, not that i want to give a competitor but I can use and give back to OpenAIs codex codebase because its MIT, it would suck to use an app you cannot modify for your own pleasure or build your own specific itching solving version of, most so as a tool for builders
will check memex out and give any concrete feedback on that regards if i have it