Mercury Agent Ships 5 MB Desktop App

Mercury’s pitch is compelling because it packages persistent, personal agent behavior into a lightweight desktop entry point. The tradeoff is that granting an agent access to files, accounts, and remote channels still demands serious trust.

• –Local SQLite memory keeps preferences, decisions, and context on the user’s machine.
• –Permission prompts and approval-controlled remote devices provide an important safety boundary.
• –Cross-platform installers lower the friction compared with terminal-only agent projects.
• –Mercury can use multiple model providers, including local Ollama models, reducing vendor lock-in.
• –The app is not code-signed yet, which adds installation friction and a noticeable supply-chain trust concern.