1.22.0

New features

MCP tool call approval

• MCP tool calls now require your approval by default. An approval dialog shows the server, tool name, and arguments before the call runs.
• Choose Allow once, Always allow this tool, or Deny. Closing the dialog denies the call.
• Always allow this tool adds the tool to the server's Allowed tools list, which you can review and prune in the MCP server settings. Remove a tool and save to require approval again.
• A new Always approve toggle in MCP server settings skips confirmation for every tool on that server.
• Approvals are bound to the server's URL and headers, so a saved permission never carries over to a different endpoint.
• Workflow command and mcp nodes accept confirm: "false" to skip approval for unattended runs, such as scheduled or event-triggered workflows.

Read-only Vault tools mode

• Added a read only Vault tools mode alongside all / no search / none. It allows searching, listing, and reading notes while blocking any tool that creates, edits, or deletes files.
• Available in the chat input's Vault tools selector and in workflow command nodes via vaultTools: readOnly.
• External MCP and skill tools keep their own separate permissions, so read-only mode does not affect them.

Improvements

• The MCP server settings dialog now locks all controls while a connection test or save is in progress, and keeps error messages visible so you can fix the configuration without reopening the dialog.
• Editing the server URL or headers invalidates a previous connection test, so Save requires a fresh successful test.
• Save failures now surface an error in the dialog instead of closing silently.