openai/codex · error · io::Error

permissions profile `{profile_name}` uses a reserved built-i

Error message

permissions profile `{profile_name}` uses a reserved built-in profile prefix

What it means

Error "permissions profile `{profile_name}` uses a reserved built-in profile prefix" thrown in openai/codex.

Source

Thrown at codex-rs/core/src/config/permissions.rs:108

                *exclude_slash_tmp,
            ),
            None => PermissionProfile::workspace_write(),
        }),
        BUILT_IN_DANGER_FULL_ACCESS_PROFILE => Some(PermissionProfile::Disabled),
        _ => None,
    }
}

pub(crate) fn validate_user_permission_profile_names(
    permissions: Option<&PermissionsToml>,
) -> io::Result<()> {
    let Some(permissions) = permissions else {
        return Ok(());
    };

    for profile_name in permissions.entries.keys() {
        if profile_name.starts_with(':') {
            return Err(io::Error::new(
                io::ErrorKind::InvalidInput,
                format!(
                    "permissions profile `{profile_name}` uses a reserved built-in profile prefix"
                ),
            ));
        }
    }

    Ok(())
}

pub(crate) fn network_proxy_config_from_profile_network(
    network: Option<&NetworkToml>,
) -> NetworkProxyConfig {
    let mut config = network.map_or_else(
        NetworkProxyConfig::default,
        NetworkToml::to_network_proxy_config,
    );

View on GitHub (pinned to 339751715c)

Solutions

1. Rename permissions profile `{profile_name}` to avoid the reserved built-in prefix.

When it happens

Trigger: Thrown at codex-rs/core/src/config/permissions.rs:108 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of openai/codex@339751715c (2026-08-25). Data as JSON: /api/errors/d559fa81e016b883. Report an issue: GitHub.