🦋 New version release#180
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@smooai/smooth-operator@1.21.1
Patch Changes
909443a: SMOODEV-2259 — per-agent SEP extension enablement:
AgentBehaviorConfignow carriesenabled_extensions(parsed from theagents.extension_configjsonb, camelCaseenabledExtensions[{extensionId, enabled, config}]), and the operator server's extensionhost intersects the server allowlist (
SMOOTH_EXTENSIONS_ALLOW) with the per-agent enabledextension ids.
Fail-closed for resolved agents: any agent that resolves to a config (exists in the agents
DB) but enables no extensions loads ZERO extensions, even when the server allowlist is
non-empty — extensions can intercept & mutate tool calls, so a public agent must never
silently inherit one. Backward-compatible when no per-agent config resolves at all
(bare/standalone operator): the server allowlist alone decides, unchanged. The Postgres
resolver now keys "no per-agent config" off row existence (not
is_empty()), so afound-but-blank agent is distinguishable from an unknown one; the
extension_configcolumnread degrades to
Noneon a standalone deploy whose table predates the column (no migrationordering dependency).