mindin 0.17.0

What's new

• One claude.ai connector or signed-in machine reaches all your vaults: your own, the shared vaults you belong to and your organisations' vaults, named with vault; connect again to get it.
• search, move_file and delete_file take vault, and the server's instructions list the vaults a connection reaches.
• A vault's page decides whether your other connections search it by default; one left out is still reached by name.
• Session start also lists pages about the repo from shared vaults you belong to.

Fixed

• The stop hook's reminder shows in Claude Code as hook feedback, not as a hook error.
• The sign-in page spaces each way to sign in apart, with the first one highlighted.

mindin 0.16.0

What's new

• An organisation lets everyone at its verified email domain in on their first sign-in.
• An organisation admin can invite someone with an account, and send again or withdraw the invitation.
• An organisation's vault is a wiki with Areas, Teams, Guides, Decisions, Projects and Incidents.
• An admin can lock an organisation's vault so only its editors write.
• An organisation decides whether members may share their own vaults with people outside it.
• Removing someone from an organisation ends their access at once and keeps or deletes their account.
• A removed member who signs in before the deletion date keeps their account.
• The organisation page lists removed members and what happens to each account.
• search covers a member's own vault and the organisation's vaults, each row labelled with its vault.
• read_file, list_files, write_file and append_file take vault to reach another vault.
• Session start lists up to five organisation pages about the repo.
• The rules tool gives every member's Claude the rules a vault's schema carries.
• A vault can refuse writes that hold a secret, a card number or a personnummer.
• mindin schema check lists a schema's problems and which tools its layout turns on, also for a file before you save it.
• A vault's page lists what a Custom layout supports, and what to add to turn each part on.
• Custom can start from a copy of the Built-in, PARA, Simple or Journal layout, on the vault's page or with mindin init --preset custom --from para.
• Only the owner or an organisation admin changes a shared vault's schema, and without one it takes no writes.
• The plugin's team-wiki skill drafts a wiki page when work is finished and writes it on a yes.
• A trusted proxy's identity token can name the proxy's own host, listed in VAULT_IDENTITY_AUDIENCE.
• mindin move copies this machine's vault to a folder, a bucket or a server and switches to it.
• mindin setup --server offers to bring the folder or bucket it replaces along.
• mindin accounts import leaves .git/ and Mac leftovers behind, and --dry-run lists what it would do.
• GET /api/vault/limits tells a signed-in machine its vault's storage limits and usage.
• mindin support request asks an account to open a vault, and the account approves or declines on its Account page.
• Extensions can add background work, storage limits, an email-link check and organisation page sections.
• Extensions can decide on every new account and hear of each write the storage limits refuse.
• mindin.extension_api exports every name an extension and its tests use.
• server.sh sets up a server with Docker in one command and invites its first account.
• The Docker images run on arm64 too, such as Apple Silicon, Graviton and a Raspberry Pi.
• Each release attaches a CycloneDX SBOM of the Python package and of both container images.

Fixed

• /vault:login signs in with the same mindin version the plugin runs.
• The stop hook asks to log commits only when the vault's layout has a log folder.

mindin 0.15.2

Fixed

• Deleting a note on an S3 server that ignores the etag on deletes is refused when the note changed meanwhile.

mindin 0.15.1

Fixed

• Removing two ways in at once on a hosted server always leaves the account one way in.
• A write with a local vault's etag is refused whenever the note changed, also when a same-size edit lands within the same instant.
• search and mindin search without a limit return as many notes as the schema's search.default_limit.
• mindin read in a terminal shows the title once when the note opens with the same # heading.

mindin 0.15.0

What's new

• mindin setup asks whether to share anonymous usage data, and nothing is sent until you say yes.

mindin 0.14.3

What's new

• Sign-in and invitation emails come as branded HTML with one button, in light and dark, and a plain-text part.

mindin 0.14.2

Fixed

• mindin without a vault starts the server and answers each tool call with how to run mindin setup.

mindin 0.14.1

What's new

• The install script answers at curl -fsSL https://mindin.dev/install.sh | sh, and mindin.dev is the package's homepage.
• The Claude Code plugin runs mindin itself instead of the notes-vault-mcp package, like a fresh install.

mindin 0.14.0

What's new

• Renamed from notes-vault-mcp to mindin: the package, the command and the image are mindin. The notes-vault-mcp package and command keep working and run mindin, the image is published under both names, and ~/.config/notes-vault-mcp and ~/.cache/notes-vault-mcp move to mindin on the first run, so no machine is signed out or indexed again. Extensions register in the mindin.extensions entry point group and import from mindin.extension_api.
• mindin setup asks where the vault lives, a folder, an S3 bucket or a vault server, and saves it for every command and client on the machine; --folder, --s3 and --server do it from a script. The environment still wins, and the Claude Code plugin's settings are read when mindin has none. status names which one decided in source.
• curl -fsSL https://github.com/gronare/mindin/releases/latest/download/install.sh | sh installs mindin with uv, runs setup and offers to add the vault to Claude Code, Codex and Cursor.
• mindin about --json tells a tool the name, version, contract and the commands this install has.

notes-vault-mcp 0.13.0

What's new

• The documentation lives in docs/, sorted into install guides, how-tos, reference and explanation, with a page listing every environment variable.
• deploy/docker/ holds the Docker Compose setup, and each GitHub release carries its compose.yml, Caddyfile and example.env, so a server installs with two curl lines. Its .env keeps the vaults in the container's volume unless you set a bucket.
• VAULT_HTTP_STATELESS=on serves MCP without sessions, so a server restart drops no session a client holds.
• notes-vault-mcp embed-worker --listen host:port runs the model for search by meaning in a process of its own that the server reaches through VAULT_EMBED_URL, with VAULT_EMBED_TOKEN as its secret, so the server restarts fast and stays small.
• GET /ready answers 200 when the server is ready for requests and 503 with the names of the failing checks, for a load balancer or a readiness probe.
• VAULT_INDEX_SNAPSHOTS=on keeps a sealed copy of each vault's search index in storage, so a restarted or moved server restores a vault's index instead of indexing and embedding every note again. A busy vault's copy is written at most once per VAULT_INDEX_SNAPSHOT_MINUTES (default 10) and only when the index changed, plus once when it goes idle and once when the server stops.
• VAULT_FORWARDED_ALLOW_IPS names the reverse proxies, as addresses or CIDR ranges, whose X-Forwarded-For the server trusts, so rate limits count each real client; the limits are kept in the account store and survive a restart.
• Extensions import what they build on from notes_vault_mcp.extension_api; Extensions describes each hook.
• A vault server has one address, /mcp; another vault than the one picked when connecting is /mcp?vault=<slug>, and a slug is one lowercase word, unique among the vaults an account reaches. A new account's first vault is notes, and existing slugs that break the rule are rewritten on the first start.

Fixed

• Two writes to one note at the same moment both land: append_file, set_status, close, log_append, write_file and the monthly log pages write over the version they read and read again when the note changed meanwhile, two backlog_add calls with one title get two notes, and a new vault's first files never overwrite a file already there.
• WebDAV PUT honours If-Match and If-None-Match: * and answers 412 when the file changed.
• A note's age counts calendar days in local time, so a note from five days back reads "5 days" also just after midnight.
• A vault server's root address opens the account page instead of answering not found.
• The access log leaves out query strings, so sign-in and invitation links never land in it.
• An unknown vault address answers like a known one the caller cannot reach.
• WebDAV opens vaults and talks to storage off the event loop, so a slow vault never stalls other requests or /up.
• An edit from Obsidian over WebDAV shows in search at once instead of after up to 20 seconds.
• close keeps a change that lands on the note while it is being archived.