You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Analytics still collapsed a managed permission profile with unrestricted filesystem access and restricted network access into the external_sandbox telemetry bucket. That loses the same distinction this stack is trying to preserve elsewhere: external sandbox means enforcement is delegated outside Codex, while managed custom permissions are still represented by Codex's PermissionProfile model.
What Changed
Updated the analytics sandbox_policy classifier to report custom_permissions for managed unrestricted-filesystem/restricted-network profiles.
Updated the reducer test to capture that distinction explicitly.
Replaced a read-only analytics test fixture that still built a PermissionProfile through SandboxPolicy with PermissionProfile::read_only().
Verification
cargo test -p codex-analytics managed_full_disk_with_restricted_network_reports_custom_permissions
summarize_managed_profile now labels any managed profile with at least one writable root as workspace-write, but custom managed policies can have writable paths (for example /tmp or another absolute root) without granting write access to the working directory. In that case this branch produces a misleading mode string instead of custom permissions, which regresses the previous to_legacy_sandbox_policy-based behavior and can misstate the effective sandbox in user-facing status/config summaries.
Closing this pull request because it has had no updates for more than 14 days. If you plan to continue working on it, feel free to reopen or open a new PR.
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
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.
Why
Analytics still collapsed a managed permission profile with unrestricted filesystem access and restricted network access into the
external_sandboxtelemetry bucket. That loses the same distinction this stack is trying to preserve elsewhere: external sandbox means enforcement is delegated outside Codex, while managed custom permissions are still represented by Codex'sPermissionProfilemodel.What Changed
sandbox_policyclassifier to reportcustom_permissionsfor managed unrestricted-filesystem/restricted-network profiles.PermissionProfilethroughSandboxPolicywithPermissionProfile::read_only().Verification
cargo test -p codex-analytics managed_full_disk_with_restricted_network_reports_custom_permissionsStack created with Sapling. Best reviewed with ReviewStack.