Funes Vault

Public preview · v0.1 · for macOS

Give AI agents your memory. Not all of it.

Funes Vault keeps what AI agents should know about you (your preferences, projects, instructions and constraints) in a private vault on your Mac. Each agent gets only what you allow, and you can see everything it received.

Download for Mac Source on GitHub

Free and open source (Apache 2.0) · macOS 15 Sequoia or later · Apple silicon and Intel · Release notes

Or install with Homebrew:

brew install --cask bereciartua/tap/funes-vault
The Funes Vault icon: an open eye, white with a black outline and a black iris, on an orange ground.

How it works

Funes Vault is a menu bar app with a local MCP server. Agents on your Mac connect to it the way they connect to any MCP tool.

  1. Keep your context in one place. Write memories in the vault, capture a thought from any app with a shortcut, or select text and choose Remember in Funes. Funes proposes a title, categories and a sensitivity (on your Mac, unless you choose another AI model), and you review each one in the Inbox.
  2. Connect your agents. Claude Code, Claude Desktop, Cursor, Codex, VS Code and other MCP clients, each with its own key and setup you can apply in one click. They talk to Funes on 127.0.0.1 only.
  3. Agents ask; you decide. When an agent needs context for a task, Funes finds the relevant memories, keeps only the ones that agent may have, and, if you asked to approve, shows you the exact text before anything is shared.

How you stay in control

Consent is the product. Funes is built so that a confused, compromised or over-eager agent gets less, not more.

Every agent starts with nothing

For each agent you choose whether it can read or suggest memories, up to which sensitivity, in which categories, until when, and whether it must ask first. Anything unclear means no.

You approve the exact text

A small panel shows the precise memories an agent would receive. You pick which ones go, and only those leave the vault, once. An agent's own words never change what it may have.

Agents suggest, you decide

Agents can propose new memories. They wait in your Inbox and join the vault only when you approve them.

You can see everything

Activity records every request, decision and release, with ids rather than text. Pause Funes, or pause or remove any agent, instantly.

A look inside

An approval panel listing the memories an agent asked for, each with a checkbox.
An agent asks: you see the exact text and choose what it gets.
The vault window with a list of memories and one memory open, showing its categories and sensitivity.
The vault: short, durable memories with categories and a sensitivity.
An agent's access settings: operations, sensitivity ceiling, categories and expiry.
Per-agent access: what each agent may read or suggest, and until when.
The Inbox with captures and agent suggestions waiting for review.
The Inbox: your captures and agents' suggestions wait for you.
The Activity log listing requests, decisions and releases by agent.
Activity: every request and decision, on your Mac only.

Local first

Your vault lives in ~/Library/Application Support/FunesVault. There's no account, no server of ours, no analytics and no telemetry. Search runs on your Mac with a small embedding model built into the app, and new captures are classified with Apple's on-device model by default.

What leaves your Mac: what you allow agents to have, a daily update check to GitHub, and, only if you add one, the capture text you send to an AI provider of your choice, never above your cloud sensitivity limit and never anything that looks like a secret. Read the privacy statement.

Funes Vault separates the agents you connect from each other and from your vault. Like most Mac apps, it can't protect your data from malicious software already running as you, and it can't recall text once an agent has it. The security policy lists the limits.

Docs

Get started

Install, first run, your first memory and your first agent.

Connect agents

Setups for each agent, the MCP tools, and the limits.

Architecture

How the app, the local MCP server and the vault fit together.

Changelog

What changed in each release.

Verify your download

Every release is notarized by Apple, lists its checksums in SHA256SUMS, and carries a build attestation from GitHub Actions. With the GitHub CLI:

gh attestation verify FunesVault-0.1.0.dmg --repo bereciartua/funes-vault-app