Skip to content

v1.65.0: chore: cut 1.65.0 (#2905)

Choose a tag to compare

@DEENUU1 DEENUU1 released this 11 Nov 16:17
33acae8

Added

  • Approval per MCP tool. In a server's settings in the Builder, each tool
    can run freely or ask first on its own, whatever its group and the server's
    readOnlyHint say. A server that marks no tool read-only can let its reads
    run while its writes ask, and one write can run unasked without none
    releasing every other one. The spec keeps these in a new tool_approval on
    organization and personal MCP bindings, keyed by the tool's name on the
    server; a group whose tools differ reads Per tool. In a chat app a tool
    without a read-only hint still asks, a watch leaves out a read its binding
    asks before, and a routine's standing consent can cover a tool set to run
    freely. Stored agents dump unchanged, so reviewed routine sources and eval
    baselines stay valid (#2884).

Fixed

  • A further account on an MCP server takes the server's settings.
    Add another account bound the new account with every tool and no
    approval, while the settings showed, and applied to every account, the first
    account's tools and approval. Under Changes things: Ask first, the second
    account's writes ran unasked (#2884).