Skip to content

feat: agent catalog foundations and migration #14316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
erichare merged 7 commits into from
Jul 31, 2026
Merged

feat: agent catalog foundations and migration #14316

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
6b73635
feat(catalog): add policy data model
erichare Jul 29, 2026
5e757c1
fix(catalog): harden foundation migration
erichare Jul 30, 2026
dc68bea
feat(catalog): add policy service and admin API (#14318)
erichare Jul 31, 2026
9949470
feat(catalog): close remaining enforcement paths (#14364)
erichare Jul 31, 2026
5eeb48c
fix(catalog): sequence migration after provider policy
erichare Jul 31, 2026
abd50b8
Merge branch 'release-1.12.0' into feat/agent-catalog
erichare Jul 31, 2026
a425e92
fix(catalog): remove stale authorization test mock
erichare Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion docs/docs/Deployment/deployment-block-custom-components.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,23 @@ LANGFLOW_CUSTOM_COMPONENT_ADMIN_ONLY=true

When set to `true`, non-superusers can still view and use custom components in flows, but they cannot create new custom components or edit custom component code.

## Interaction with catalog governance

Catalog governance takes precedence over the custom-code settings on the custom-component create, update, and code-validation endpoints. A catalog block has no superuser bypass.

| Submitted source | Catalog policy | Custom components | Admin-only mode | Result |
|---|---|---|---|---|
| Known server template | Blocked | Either | Either | Denied for every user |
| Known server template | Allowed | Disabled | Either | Allowed using the trusted server source |
| Known server template | Allowed | Enabled | Non-superuser | Allowed using the trusted server source |
| Unknown custom source | Not blocked | Disabled | Either | Denied |
| Unknown custom source | Not blocked | Enabled | Non-superuser | Denied |
| Unknown custom source | Not blocked | Enabled | Superuser or admin-only disabled | Allowed |

For `POST /api/v1/validate/code`, this policy runs before the source is parsed or imports are inspected. In a restricted custom-code mode, known templates are validated from the trusted server copy, while unknown source follows the same disabled or admin-only rule as the component editor. On custom-component create and update, known blocked template source is rejected before the component is built, and the resolved component type is checked again before request-supplied frontend updates are applied.

An active catalog policy fails closed with a temporary `503` response while server template identities are still initializing. An empty catalog policy preserves the default behavior and does not require template identity lookups.

## Configure a custom component allow-list

`LANGFLOW_ALLOW_CUSTOM_COMPONENTS` works together with optional paths that define which component templates the server loads, and which code hashes are trusted.
Expand Down Expand Up @@ -62,4 +79,4 @@ Default is `true`, which preserves existing behavior. The setting has no effect
For more information, see:

* [Environment variables](/environment-variables#visual-editor-and-playground-behavior)
* [Security](/security)
* [Security](/security)
Loading
Loading