Apps that saw no tools can see them now

Fixed

• Some apps, ChatGPT connectors in particular, signed in and then reported that the site had no actions they could use. Saddle now serves apps that do not hold a session between requests. If you hit this, delete the connector in your AI app and create a new one, because most apps ask for the tool list once and remember the answer.

New

• Client traffic, under Connections. Records what a connected app asked for and what it got back, so “it says it cannot see any tools” can be answered without guesswork. Off by default, stops after an hour, and records no keys or content.

Improved

• Tools now tell an app what they do before they run: a readable name, and whether a tool only reads, can destroy anything, or is safe to repeat.
• A refused tool call returns its reason as a readable answer instead of a protocol error, so your assistant can tell you which control to change.
• Saddle no longer bundles the MCP Adapter library. It speaks the protocol itself, at the same address, with the same tools and the same safety model. If you have the separate MCP Adapter plugin active, Saddle uses it automatically.

Security

• Your active plugins and theme name are shared with an AI only at the highest access level, matching the level already needed to list them. The connection handshake also respects the pause switch.