Private chat
Turn off Memory use and saving for a conversation while understanding what still persists and leaves your Mac.
Turn it on#
- Open the composer's + menu.
- Enable Private chat.
- Check for Private · memory off above the composer before sending.
- Use Turn off private chat on that chip to return to ordinary Memory-enabled work.
Private chat skips Memory reads and saves together. It also skips Bot's own working memory when used in Bot. There is no read-only Memory choice in the composer.
What still happens#
| Item | With Private chat on |
|---|---|
| Chat history | Still saved locally |
| Messages | Still sent to your selected AI provider |
| Saved Memory | Not read or added to by the turn |
| Native workspace file changes | Can still occur and persist |
| Loupist instructions and tone | Still apply |
Private chat does not create an unsaved conversation and does not make remote AI inference stay on your Mac. Numbers or other information you type remain part of the message you send.
Choose defaults for new conversations#
Remember new conversations in Chat defaults or Loupist settings is on by default. Turning it off changes new conversations; existing chats retain their saved policy. Check the visible privacy chip in the conversation you are about to use.
Scheduled work keeps its own saved Memory selections. Private chat is not a global switch that turns off all background activity.
Check connection-specific limits#
A custom Data connection starts with Don't save results to Memory on. That policy can prevent saving a turn that used its result even outside Private chat. A refusal names the connection policy; changing Chat privacy does not bypass it.
Use What leaves your Mac and security for provider requests, local credentials, and the limits of the file and code boundaries.
Based on the app’s source documentation and English interface labels. Report a docs issue.