Files
windmill/frontend/src/lib/components
AlexRV12andClaude Opus 5 0b3dc3e5c9 fix: build the global chat's prompt identity from the operating workspace (#10793)
* fix: do not read an unloaded workspace list as a non-membership

`roleForWorkspace` settled `not_a_member` from `userWorkspaces` alone. That store and
`superadmin` both start undefined and load asynchronously, so an unloaded list read as an
empty one: a chat operating on any workspace other than the one being browsed advertised no
pages and reported an access denial. The root layout gives up after its retries, so a load
that fails leaves the denial permanent, with `whoami` never attempted.

Settle a non-membership only once both stores have resolved; treat unresolved as unknown
and fall through to the `whoami` lookup.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix: build the global chat's prompt identity from the operating workspace

The prompt's path conventions and folder guidance came from the ambient `userStore`, which
describes the workspace being browsed rather than the one the chat operates on. Three of
those fields are per-workspace and wrong whenever the two differ: the username (that
workspace's `usr` row), the writable/readable folder sets (its ACLs), and `is_admin`, which
decides whether the folder list reads as exhaustive. The backend still enforces the ACLs, so
the cost is prompt quality — paths the model cannot write to, and a 403 to recover from.

Resolve the identity for the operating workspace and feed that to the prompt, refreshed
alongside skills and MCP servers and settled in `beforeSend` so the cached system-prompt
prefix stays stable for the turn. An unresolved role now leaves the folder sets undefined
rather than empty, so the guidance is dropped instead of claiming there is nothing to write
to, and `create_folder` credits the workspace it wrote to.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix: read the AI provider resource types lazily

`Object.keys(AI_PROVIDERS)` at module scope made `AI_PROVIDERS` a load-time requirement for
every importer of this module, the global chat included. `AIChatManager.test.ts` mocks
`../lib` without it and has been unable to load since the catalog was introduced; no CI
workflow runs vitest, so nothing reported it.

The constant is read in two places, both inside functions, so deferring it removes the
load-time dependency without changing behaviour.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-21 12:23:25 +02:00
..
2025-10-30 06:47:26 +00:00
2025-10-28 17:52:04 +00:00
2026-03-05 18:11:40 +01:00
2026-03-05 18:11:40 +01:00
2025-11-04 19:13:09 +00:00
2026-02-11 06:27:21 +00:00
2025-11-29 01:23:47 +00:00
2026-03-05 18:11:40 +01:00
2026-03-05 18:11:40 +01:00