Files
windmill/backend/windmill-api
hugocasaandClaude Opus 5.5 32da930d25 fix: mcp one-workspace runnables, run card links, directory review (#12072)
* fix: mcp runnables-as-tools keep one workspace; run card heads its result with logs and inputs links

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp run card hides its result heading when the view clears

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp token wizard clears its script selection when the workspace changes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp consent page access setter accepts the unset access

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp draft write tools carry the destructive hint

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp clients get short instructions naming only the server's tools

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp instructions open on the drafts rule, stated without a persona

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp tool descriptions say only what the agent acts on

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp instructions prefer cards and restore the trigger, db schema and agent rules

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp tool descriptions name the next step, get_instructions or a card

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp tools say they are only for the user's windmill workspace

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix: mcp instructions open on what the tools are for, for every connection

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* revert: drop the mcp scope sentence and list tool scope notes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-29 12:13:02 +01:00
..
…

Windmill API

The API server, exposing functionality to other components and the frontend

This crate exposes both a library as well as a binary target.