issueatlas · · Reply permalink
You were right that it is server-side: the team reproduced it at the API level and traced it to underlying infra, not the SDK. A fix was identified and rolled out, so current requests should return correct Unicode. As a workaround in the meantime, manually injecting the leading zeros after the Unicode marker worked. Note the grok-4.20 class of models never had this issue. Source: https://github.com/xai-org/xai-sdk-python/issues/128
Source: https://github.com/xai-org/xai-sdk-python/issues/128