Kill ENABLE_MANAGED_AGENT_CONFIG; gate managed config on the server SAFE flag - #504
Draft
david-siqi-liu wants to merge 1 commit into
Draft
Kill ENABLE_MANAGED_AGENT_CONFIG; gate managed config on the server SAFE flag#504david-siqi-liu wants to merge 1 commit into
david-siqi-liu wants to merge 1 commit into
Conversation
…AFE flag Remove the client-side ENABLE_MANAGED_AGENT_CONFIG env var and managed_agent_config_enabled(). Managed coding-agent config is now gated purely by the server-side SAFE flag, which surfaces as FEATURE_DISABLED from refresh_managed_config (authoritative: returns None and clears the cache). - Drop the `ug configure` admin auto-routing. It was a passthrough when the flag was off, so configure now behaves as it always did for non-flag users: non-interactive, no managed-config prompts. Keeps omnigent's `ucode configure --profiles --agents ... --use-pat` non-interactive. - Bare `ug` prints help when the feature is disabled server-side, instead of a silent no-op. - Launch always consults the managed config (removed the cached-launch fast path) so an admin's config can't be bypassed by stale local state. - Remove --skip-managed-config; it worked by unsetting the now-gone env var. - status and the launch "no managed config" note key off the server signal. Co-authored-by: Isaac <no-reply@databricks.com>
david-siqi-liu
force-pushed
the
david/kill-managed-config-flag
branch
from
September 5, 2026 02:30
a6580cc to
a7ebe98
Compare
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
1 participant
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.
Stacked on #500.
What
Removes the client-side
ENABLE_MANAGED_AGENT_CONFIGenv var andmanaged_agent_config_enabled(). Workspace-managed coding-agent config is now gated purely by the server-side SAFE flag, which surfaces as aFEATURE_DISABLEDreason fromrefresh_managed_config(authoritative: returns no config and clears the persisted cache).Why
The client flag was a bug-bash opt-in. Per team decision, the feature should be gated by the server SAFE flag alone. Two constraints had to hold, and do:
ucode configure --profiles DEFAULT --agents claude,codex,pi --use-pat --skip-validate --skip-upgradestays non-interactive.Changes
ENABLE_MANAGED_AGENT_CONFIG/managed_agent_config_enabled()and every gate that read them.ug configureadmin auto-routing. When the flag was unset it was already a passthrough, soug configurenow behaves exactly as it did for non-flag users: non-interactive, no managed prompts.ugon a feature-disabled workspace prints a short, managed-free guidance line (runug configure, thenug <agent>) instead of a silent no-op.--skip-managed-configfrom all commands (it worked by unsetting the now-gone env var).statusand the launch "no managed config" note key off the server signal rather than the env var.Testing
This pull request and its description were written by Isaac.