> ## Documentation Index > Fetch the complete documentation index at: https://hmm.heyhyper.ai/llms.txt > Use this file to discover all available pages before exploring further. # Incognito Mode: Pause Memory Writes in Hyper > Pause all memory writes in Hyper without disconnecting. Reads still work. Ideal for sensitive client work, NDAs, or personal projects. Sometimes you're working on something that shouldn't go into shared memory — a client project under NDA, a personal experiment, or code you're not ready for the team to see. Hyper's incognito mode lets you keep your AI tools connected and fully functional while silently pausing everything that would normally be written to memory. You can still look things up; you just won't leave a trace. This guide explains how to toggle incognito mode and when to use it. *** ## What Incognito Mode Does Incognito mode is a **write pause**, not a disconnect. The distinction matters: All memory writes are paused: `remember()` calls, `observe` hooks, and any automatic capture triggered by `UserPromptSubmit` or `Stop` hooks. Nothing from this session is saved to your workspace. Read operations continue normally. `ask()` and `connect()` still retrieve existing memories and load your workspace context — you just won't add to them. Incognito mode stays on until you explicitly toggle it off. Closing your editor, restarting your machine, or starting a new conversation doesn't turn it off. Switching between muted and unmuted takes a single command or one click in the desktop app, with no reconnection needed. Because mute state persists across sessions, it's easy to forget you left it on. Get into the habit of checking your status at the start of sensitive work — and checking again when you're done. *** ## How to Toggle via the Desktop App Launch the Hyper desktop app and ensure you're connected to your workspace. Look for the **Incognito** or **Mute Memory** toggle in the main toolbar or the status area at the bottom of the app window. Click the toggle. The app will show a clear visual indicator — typically a distinct icon or color change — confirming whether writes are currently paused. *** ## How to Toggle via the MCP Tool If you prefer staying in your editor, you can toggle incognito mode directly through Hyper's `mute()` MCP tool. Ask your AI assistant to call it, or trigger it via a prompt: ```text theme={null} Please call the Hyper mute tool. ``` The tool returns a single string indicating the **new state** after the toggle: | Return value | Meaning | | ------------ | ---------------------------------------------------- | | `MUTED` | Incognito mode is now **on** — all writes are paused | | `UNMUTED` | Incognito mode is now **off** — writes have resumed | `mute()` is a toggle, not a setter — each call flips the current state. To check your current state without changing it, call `connect()` and look for a mute indicator in the briefing output. ### Quick Toggle Examples In a Claude conversation, type: ```text theme={null} Call the Hyper mute tool to enable incognito mode. ``` Claude will call `mute()` and report back `MUTED` or `UNMUTED`. To verify the state later without toggling, type: ```text theme={null} Call the Hyper connect tool and tell me if incognito mode is on. ``` In Cursor Chat, type: ```text theme={null} Toggle Hyper incognito mode. ``` Cursor's AI will call `mute()` and display the result. If it returns `MUTED`, writes are paused. If it returns `UNMUTED`, writes have resumed. *** ## When to Use Incognito Mode Proprietary code, data, or architecture details that belong to a client should never end up in your team's shared memory. Enable incognito before you start and disable it when you switch back. Side projects or personal experiments you're running on work hardware don't need to bleed into your team workspace. Early-stage experiments that might never ship — and whose dead ends you don't want cluttering team memory. Vulnerability analysis, penetration testing notes, or exploit research that could be misread out of context. *** ## Checking Your Current Status Incognito mode persists across sessions, so always verify your state before starting sensitive work: Prompt your AI tool with `Call the Hyper connect tool`. The workspace briefing will indicate if mute is active. Open the Hyper desktop app. The incognito indicator in the toolbar reflects the live mute state. When your sensitive session is over, call `mute()` again (which returns `UNMUTED`) or click the toggle in the desktop app to resume normal memory capture. Consider adding a personal reminder to your workflow: put "check Hyper mute status" in your task list at the top of any session involving confidential work, then again when you wrap up. *** ## Incognito Mode vs. Disconnecting You might wonder why not just remove the MCP server when you need privacy. Here's why incognito mode is the better choice: | | Incognito Mode | Disconnecting | | ---------------------------- | ------------------ | -------------------------------- | | `ask()` / memory reads | ✅ Still work | ❌ Unavailable | | `connect()` / workspace load | ✅ Still works | ❌ Unavailable | | Memory writes | ⏸ Paused | ❌ Unavailable | | Time to enable | Instant (one call) | Requires config change + restart | | Time to disable | Instant (one call) | Requires config change + restart | | AI context still available | ✅ Yes | ❌ No | Incognito mode gives you privacy without sacrificing the context and recall that make Hyper valuable.