|
1 | 1 | # executor |
2 | 2 |
|
| 3 | +## 1.5.11 |
| 4 | + |
| 5 | +### Patch Changes |
| 6 | + |
| 7 | +- [#1002](https://github.com/RhysSullivan/executor/pull/1002) [`64b3544`](https://github.com/RhysSullivan/executor/commit/64b3544c297f122fb915ab281f2ac84c766ddcfd) Thanks [@RhysSullivan](https://github.com/RhysSullivan)! - Fix the self-hosted "Connect an agent" MCP URL. The card printed an |
| 8 | + organization-scoped path (`<origin>/<organizationId>/mcp`) that the |
| 9 | + single-tenant self-host server didn't serve, so connecting an MCP client |
| 10 | + authorized successfully but then failed to reach the tools with an HTTP 404. |
| 11 | + The self-host server now accepts the organization-scoped path and routes it to |
| 12 | + its MCP endpoint. |
| 13 | + |
| 14 | +- [#1002](https://github.com/RhysSullivan/executor/pull/1002) [`64b3544`](https://github.com/RhysSullivan/executor/commit/64b3544c297f122fb915ab281f2ac84c766ddcfd) Thanks [@RhysSullivan](https://github.com/RhysSullivan)! - Self-hosted MCP connections now require explicit approval. When an MCP client |
| 15 | + connects, the browser stops on an approval screen showing the connecting |
| 16 | + client's name, what it can access, and that the grant is limited to the MCP |
| 17 | + server (not a web-app login, and it can't make other API calls on your behalf); |
| 18 | + a token is granted only after you Approve. Previously a signed-in user's client |
| 19 | + was authorized automatically with no prompt. |
| 20 | + |
| 21 | +- [#1008](https://github.com/RhysSullivan/executor/pull/1008) [`7237bf2`](https://github.com/RhysSullivan/executor/commit/7237bf2a82c2bd435a3a07f7f24338a325d578f0) Thanks [@RhysSullivan](https://github.com/RhysSullivan)! - Self-hosted instances no longer lose data on restart. Better Auth now shares |
| 22 | + the same libSQL connection as the rest of the instance instead of opening its |
| 23 | + own. Previously the two connections each managed their own write-ahead log on |
| 24 | + the shared database file, and the second one to open could orphan the first — |
| 25 | + so integrations, connections, and tools written after startup landed in a |
| 26 | + discarded log and disappeared on the next restart, while sign-in data survived. |
| 27 | + This is the "reconnected my account but it has zero tools" failure; a single |
| 28 | + shared connection removes the split entirely. |
| 29 | +- Updated dependencies []: |
| 30 | + - @executor-js/sdk@1.5.11 |
| 31 | + - @executor-js/runtime-quickjs@1.5.11 |
| 32 | + - @executor-js/local@1.4.4 |
| 33 | + - @executor-js/api@1.4.31 |
| 34 | + |
3 | 35 | ## 1.5.10 |
4 | 36 |
|
5 | 37 | ### Patch Changes |
|
0 commit comments