A single keystroke should never leak private data. Yet most systems still reveal too much when you hit Tab.
Privacy by Default Tab Completion fixes this. It’s the principle that command-line auto-completion should return only results you are authorized to see, with zero extra exposure. No hidden files revealed. No internal endpoints hinted at. No usernames offered from a shared server unless you own them.
Traditional tab completion is built for speed, not safety. Shells, CLIs, and developer tools often treat the file tree or API list as public knowledge. That design fails in multi-tenant systems, secrets management tools, admin consoles, and internal developer platforms. One unfiltered completion can expose sensitive resource names to anyone with local access.
Implementing privacy-by-default means filtering completions at the source. Scope every completion request through the same permission checks used for direct access. If the user can’t open the file, run the command, or query the API, it should never appear in a completion list. This isn’t a cosmetic setting; it’s an enforcement layer.