Skip to main content
Glama
AppLock

AppLock

by Harmantaj

AppLock

Lock and hide the AI chats you choose, behind Touch ID or a password — like Locked Notes on a Mac.

  • Browser extension hides chosen ChatGPT, Claude.ai and Gemini chats from the sidebar and shows a lock screen if one is opened directly.

  • MCP server encrypts local Claude Code and Google Antigravity sessions out of their history, and lets any MCP client (Claude Code, Antigravity, ChatGPT developer mode) hide chats for you.

Website with the full guide: https://harmantaj.github.io/applock-mcp/ (source in website/).

Why two pieces

ChatGPT, Claude.ai and Gemini keep chats on their servers. An MCP server only gives a model tools; it can't change what a web page shows. So the extension does the hiding in the browser, and the MCP server handles local history plus a lock-only bridge to the extension.

Related MCP server: sieve-map

Install

npm install -g https://github.com/Harmantaj/applock-mcp/releases/download/v0.6.4/applock-mcp-0.6.4.tgz
applock-mcp setup                 # passphrase + optional Touch ID
applock-mcp install claude        # or: antigravity | chatgpt

Browser extension: download applock-chrome.zip or applock-firefox.zip from the latest release. Chrome/Edge/Brave/Arc: unzip, chrome://extensions › Developer mode › Load unpacked. Firefox: about:debugging › This Firefox › Load Temporary Add-on (a permanent install needs the addons.mozilla.org listing). Build both with node scripts/build-extensions.mjs.

On your phone

No app or extension can change the ChatGPT/Claude/Gemini phone apps, so AppLock covers phones in layers:

  1. Hide on your phone too (setting, ChatGPT only): locking also archives the chat through ChatGPT's own API, so it leaves the chat list in the iPhone/Android/Mac apps; removing the lock unarchives it. Jobs sync, so a lock made anywhere is archived by whichever computer next has ChatGPT open.

  2. Per-chat lock in a phone browser: Firefox for Android, or Orion (Kagi) on iPhone/iPad, with the Firefox build installed. A lock button appears on chat pages on touch screens.

  3. Face ID for the whole app: iOS 18 Require Face ID; Android 15 Private space.

  4. Move to vault (ChatGPT, Claude): saves an encrypted transcript in the vault on your computer, then deletes the chat at the provider, so it's gone from every app and device. Read it on your phone in the AppLock Vault web app (/vault/<secret>/ on your tunnel address; add it to the Home Screen). Deletion only happens after the vault confirms the copy is stored.

  5. Phone connector (below) to control your Mac from Claude on the phone.

Claude everywhere (web, desktop, iPhone, Android) and ChatGPT on the web

Custom connectors added on claude.ai work in the Claude desktop and phone apps too; ChatGPT allows them only on chatgpt.com. On a Mac with Tailscale installed and signed in:

applock-mcp install phone

This starts AppLock in the background (launchd), turns on Tailscale Funnel for AppLock only — it never reuses a port another program is serving, and never replaces someone else's Funnel route — verifies it from the internet, and copies the connector URL. Add it on claude.ai › Customize › Connectors › Add custom connector. From a phone, unlock_vault returns a one-time link to your Mac's unlock page, so the passphrase never passes through the AI. It can't hide chats inside the phone apps; it's a remote control for your Mac, which must be awake.

applock-mcp remote url · applock-mcp remote rotate · applock-mcp uninstall phone

Tools

Tool

Purpose

Needs unlock

applock_status

Vault state, hidden count, extension connection

no

list_sessions

Visible Claude Code / Antigravity sessions

no

hide_session

Encrypt a session into the vault (current = when this session ends)

no

list_browser_chats

Web chats seen by the extension

no

hide_browser_chat

Lock a web chat (current = the open one; everywhere also archives it in ChatGPT)

no

copy_to_vault

Copy locked ChatGPT/Claude chats into the vault without deleting them (readable in the phone Vault)

no

hide_on_phone

Turn on ChatGPT archiving for locked chats so they leave the phone apps' lists

no

unlock_vault

Touch ID prompt, local passphrase page, or (remote) a one-time unlock link

—

lock_vault

Lock now

no

list_hidden

Everything in the vault

yes

read_hidden

Read a hidden transcript

yes

restore_hidden

Put a session back

yes

Security model

  • Sessions are sealed to an X25519 public key (ephemeral ECDH + HKDF-SHA256 + AES-256-GCM), so hiding never needs the passphrase. The private key is wrapped with scrypt(passphrase); with Touch ID a copy lives in the macOS Keychain and a Swift helper releases it after LAContext authentication.

  • The passphrase is never passed through the model: unlocking uses the Touch ID sheet or a one-time page on 127.0.0.1.

  • The bridge on 127.0.0.1:47521 accepts only browser-extension origins, pins the first extension that pairs, and is lock-only — nothing it sends can reveal a chat.

  • The extension uses PBKDF2-SHA256 (600k) with lockout, and WebAuthn (platform authenticator) with local signature verification.

  • Locks and the password hash live in chrome.storage.sync, so they follow your Chrome profile to your other computers; chat titles and the Touch ID key stay on each computer.

  • Forgot the extension password? Forgot password? on the lock screen or popup resets it with Touch ID or the one-time recovery code (100 bits, stored hashed, rotated on use).

  • Not protected: the provider's servers, the ChatGPT/Claude/Gemini phone apps (use iOS Require Face ID on the app instead), removing the extension, malware running as you. The Claude desktop app keeps its own session title list.

Development

npm install
npm test                          # build + unit + MCP client tests (stdio and HTTP)
npx playwright install chromium
npm run test:e2e                  # extension on mocked ChatGPT/Claude/Gemini, bridge, website

docs/REQUIREMENTS.md has the research notes and requirements.

License

MIT

Available Tools

12 tools
applock_statusAppLock statusA
Read-only

Shows whether AppLock is set up, locked or unlocked, how many chats are hidden, and whether the browser extension is connected.

Inputs: no named parameters.

copy_to_vaultCopy web chats into the vaultA

Saves the full transcript of ChatGPT or Claude chats into the encrypted AppLock vault, WITHOUT deleting them anywhere, so they can be read in the AppLock Vault phone app or with read_hidden. Use chat_id "locked" for every locked ChatGPT/Claude chat. Needs the browser extension with that site signed in.

Inputs: site, chat_id.

hide_browser_chatLock a ChatGPT / Claude / Gemini web chatA

Tells the AppLock browser extension to lock a web chat: it disappears from the sidebar and shows a lock screen if opened, until unlocked with Touch ID or the password. Use chat_id "current" for the chat open in the browser.

Inputs: chat_id (required), site, everywhere.

hide_on_phoneHide locked ChatGPT chats on the phone tooA
Idempotent

Turns AppLock's 'Hide on your phone too' on or off. When on, locked ChatGPT chats are also archived in the user's ChatGPT account, so they disappear from the chat list in the ChatGPT iPhone/Android/desktop apps (still listed under ChatGPT's Archived chats). Removing a lock in the browser unarchives it. Claude and Gemini have no archive. Needs the AppLock browser extension.

Inputs: on, apply_to_locked.

hide_sessionHide a chat sessionA

Encrypts a Claude Code or Antigravity session into the vault and removes it from the app's history. Works while locked. Use id "current" for the Claude Code session you are running in; it is hidden as soon as that session ends.

Inputs: id (required).

list_browser_chatsList web chats seen by the extensionB
Read-only

Lists ChatGPT, Claude.ai and Gemini chats visible in the sidebar of the user's browser, as reported by the AppLock extension. Also says which chat is open right now.

Inputs: query.

list_hiddenList hidden chatsA
Read-only

Lists everything in the vault (titles, sources, dates). Requires the vault to be unlocked.

Inputs: no named parameters.

list_sessionsList visible chat sessionsA
Read-only

Lists local Claude Code and Antigravity chat sessions that are currently visible (not hidden), newest first, so you can find the one to hide.

Inputs: limit, query, source.

lock_vaultLock the vault nowA
Idempotent

Forgets the vault key immediately and re-locks web chats in the browser extension.

Inputs: no named parameters.

read_hiddenRead a hidden chatA
Read-only

Returns the transcript of a hidden local session without restoring it. Requires unlock. Note: the text becomes part of the current, visible conversation.

Inputs: id (required), max_chars.

restore_hiddenRestore a hidden chatA

Decrypts a hidden session back to its original place so it shows up in the app again (or unlocks a web chat in the extension). Requires unlock.

Inputs: id (required).

unlock_vaultUnlock the vaultA
Read-only

Unlocks hidden chats for a few minutes. Shows the Touch ID prompt on the user's Mac, or opens a local passphrase page in their browser. The user authenticates on their own device; never ask for the passphrase in chat. Waits up to 2 minutes.

Inputs: method.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    The 'hide' family (hide_session, hide_browser_chat, hide_on_phone, copy_to_vault) and the 'list' family (list_hidden, list_sessions, list_browser_chats) could initially look overlapping, but descriptions clearly scope each to a distinct target (local session vs browser chat vs vault vs phone archive). read_hidden vs list_hidden vs restore_hidden are also well differentiated by their stated effects.

    Naming Consistency4/5

    Names follow a consistent snake_case verb_noun pattern (list_hidden, hide_session, restore_hidden, lock_vault, unlock_vault), which makes the set predictable. The lone deviation is applock_status, a noun-first status tool, but it's a recognizable convention for a query tool.

    Tool Count5/5

    12 tools sit comfortably in the well-scoped 3-15 range. Each tool maps to a concrete operation (hide, list, read, restore, lock/unlock, copy, status) with no filler.

    Completeness4/5

    The set covers the full lifecycle: hide, list, read, restore, copy, lock, unlock, and status, with per-surface variants for local sessions and browser chats. Minor gaps exist (e.g. no way to permanently delete/clear a vault entry or search within hidden items), but core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Secrets vault for Claude Code. Encrypt API keys, tokens and passwords with AES-256. Full audit logs, MCP access rules, and zero-knowledge mode. Secrets never appear in chat.
      17
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Local MCP server for macOS that scans AI coding tool history (Claude Code, Cursor, Copilot, Cline, Codex, Gemini CLI) for leaked secrets. Finds API keys in chat transcripts, redacts with sieve:// placeholders, and runs commands with Keychain-injected secrets - no plaintext values ever returned.
      9
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Encrypted token store for Claude Code sessions, providing MCP tools for secure secret management with macOS Keychain integration, per-project allowlists, and native dialog input.
      6
      56 npm
      6
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables macOS users to securely connect AI assistants such as Notion AI, Claude, and Cursor to their local files and terminal through an MCP server protected by a Bearer token and Cloudflare Tunnel.
      MIT