Python SDK is not compatible with latest Copilot-CLI

[0xba1a]

I'm getting following exception while connecting the SDK to a remotely running CLI.

ValueError: invalid literal for int() with base 10: '2026-05-27T13:08:01.308Z'

Analysis from Copilot -

The SDK's [PingResponse.from_dict()] calls [int(timestamp)] on the [timestamp] field from the server's ping response. The copilot-cli server running inside your container is returning the timestamp as an ISO 8601 string ("2026-05-27T12:56:21.217Z") instead of a Unix epoch integer.

[github-actions]

Investigation Findings

Thanks for the detailed report! I investigated the relevant code paths in the Python SDK.

What I looked at:

• python/copilot/client.py — PingResponse.from_dict() (lines 322–337)
• python/copilot/generated/rpc.py — PingResult.from_dict() (lines 3516–3521) and from_datetime() (line 75–76)

What I found:

The current code in client.py already handles both integer (Unix epoch ms) and ISO 8601 string timestamps:

timestamp_value = (
    datetime.fromtimestamp(timestamp / 1000, tz=UTC)
    if isinstance(timestamp, (int, float))
    else from_datetime(timestamp)  # uses dateutil.parser.parse for ISO strings
)

This means the bug you're describing does not reproduce with the current version of the SDK. The ValueError: invalid literal for int() with base 10 error would only occur if int(timestamp) was called directly on the string — which is not what the current code does.

Likely cause: You may be running an older version of the Python SDK that had this bug before the timestamp handling was made flexible.

Recommended action: Please update to the latest version of copilot-sdk and verify if the error persists. If it does, please share:

1. The exact version of the SDK you're using (pip show copilot-sdk or similar)
2. The full traceback showing which line raises the error

I've labelled this as question for now. If you can reproduce it on the latest version, we can reopen/relabel as a bug.

Generated by Bug Handler for issue #1454 · ● 6.8M · ◷

[0xba1a]

The latest release in pypi.org is 0.3.0. Please check the reference screenshot.

It looks like the code in above comment is added after the last release.

Though the correct code is available in the source repo, it didn't get published to pypi. Can you please check when the pypi publishing will be aligned with GitHub release?

[stephentoub]

The compatibility bug is fixed in the repository. PingResponse.from_dict() in python/copilot/client.py now accepts both Unix epoch timestamps and ISO 8601 strings:

timestamp_value = (
    datetime.fromtimestamp(timestamp / 1000, tz=UTC)
    if isinstance(timestamp, (int, float))
    else from_datetime(timestamp)  # parses ISO 8601 strings
)

So connecting to a CLI that returns an ISO-8601 timestamp no longer raises ValueError: invalid literal for int().

As you correctly pointed out, this landed after the 0.3.0 PyPI release, so it isn't on PyPI yet — it will be included in the next published Python SDK release. I'm closing this since the compatibility bug itself is resolved in source; the remaining item is purely the PyPI publish cadence (tracked separately, see #1374). If the incompatibility persists once the next release is out, please reopen.

Generated by Copilot