mute tool toggles incognito mode for your Hyper account. When muted, Hyper pauses all memory writes — nothing from your conversations gets saved to shared team memory, whether triggered by the Stop lifecycle hook or an explicit remember call. Reads remain fully functional while muted, so you can still use ask and ask-with-history to query existing team knowledge. Call mute again to turn incognito mode off and resume normal memory capture.
Parameters
mute takes no parameters.
Returns
Returns
"MUTED" if incognito mode was just turned on, or "UNMUTED" if it was just turned off. Each call toggles the current state.Example Calls
Turning incognito mode on
Turning incognito mode off
What Mute Affects
| Feature | While Muted | While Unmuted |
|---|---|---|
remember calls | Silently dropped — nothing is written | Written to shared memory normally |
Stop hook memory capture | Paused — observations are not saved | Active — conversations are captured |
ask queries | Work normally | Work normally |
ask-with-history queries | Work normally | Work normally |
connect | Works normally | Works normally |
| Other team members’ writes | Not affected | Not affected |
Mute is account-scoped and persists across sessions and clients. If you mute in Claude Desktop, you’ll also be muted in Cursor until you call
mute() again to unmute. The state is stored server-side in your Hyper account.When to Use Mute
Mute is designed for sessions where you’re doing exploratory, sensitive, or speculative work that you don’t want saved to shared team memory:- Private investigation — exploring a sensitive performance issue or debugging a security incident without polluting shared memory with in-progress hypotheses.
- Drafting mode — working through ideas that aren’t ready to share with the team yet.
- Demo or sandbox sessions — running demo conversations in a shared environment where you don’t want synthetic activity written to real memory.
- Personal context — discussing something with your AI assistant that’s personal and out of scope for team memory.
Checking Your Current Mute State
There’s no dedicated “status” call — the quickest way to check whether you’re muted is to look at theHYPER BRIEFING block at the start of your session (populated by connect), which includes your current mute state. Alternatively, call mute() — if it returns UNMUTED, you were muted; if it returns MUTED, you were unmuted and are now muted again.
Relationship to remember
When incognito mode is active,remember calls are silently acknowledged — the tool returns "Remembered." as usual, but no data is actually written. This preserves the flow of conversation without surfacing an error, while still respecting your privacy preference. If you need to confirm a write actually happened, unmute first, then call remember.