cli not pulling latest picard image

[kevin-kortum-trustedshops]

Meta:

CircleCI CLI Version:

0.1.31632+d2e8a96 (homebrew)

Operating System:

Darwin 24.4.0 Darwin Kernel Version 24.4.0: Fri Apr 11 18:33:47 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T6030 arm64
aka
macOS Sequoia 15.4.1 (on Apple M3 Pro)

CircleCI CLI Diagnostic:

---
CircleCI CLI Diagnostics
---
Debugger mode: false
Config found: /Users/<redact>/.circleci/cli.yml
API host: https://circleci.com
API endpoint: graphql-unstable
OK, got a token.
Hello, <redact>.

---

Current behavior:

Just running a local job for orb development as described at https://circleci.com/docs/testing-orbs/

Note: This is explicitly programmed into https://github.com/CircleCI-Public/circleci-cli/blob/main/local/local.go#L199 but my checksum is sha256:47f9460bf9d6227a845f7859960218794c55c2ea886b3c0273ea713a1868ff90

Expected behavior:

I noticed that the tool prints Fetching latest build environment... but all images that were fetched are 2 to 3 years old and are not the latest revision.
After removing the images and explicitly pulling the latest circle-cli and picard images, the picard image was still ignored and the older one was pulled during the test (e.g. circleci local execute ***).

When did this begin / Was this previously working?:

I started observing it three days ago. Maybe it did work previously, but i don't know.

Additional Information:

[kevin-kortum-trustedshops]

Update: I figured out its potentially possible to override this with --build-agent-version but i was not able to find a recent version which would work. The error messages are not helpful at all for me e.g.
time="2026-01-15T07:17:46Z" level=error msg="Exit with status 1 due to generic error" error="unknown command \"build\" for \"circleci\""

The hardcode one (and even a few never ones) fail with a go panic.

Update: I see now based on the code that this feature is effectively deprecated/disabled. The new agent images in docker do not ship with a cli that can execute the required command e.g.
docker run --rm --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock --mount type=bind,src=/var/folders/d4/5cxvx7kj6gzfgb20fj9tvn2m0000gp/T/744127541_circleci_config.yml,dst=/var/folders/d4/5cxvx7kj6gzfgb20fj9tvn2m0000gp/T//local_build_config.yml --mount type=bind,src=/path/to/my/test/orb/.debug,dst=/path/to/my/test/orb/.debug --mount type=bind,src=/home/user/.circleci,dst=/root/.circleci --workdir /path/to/my/test/orb/.debug circleci/picard@sha256:6f72343e2ae79be6f5f04997aa3e26299d2cedef27da1aa0f491508e4a704e4d circleci build --config /var/folders/d4/5cxvx7kj6gzfgb20fj9tvn2m0000gp/T//local_build_config.yml --job local-orb local-orb

The image fails because it cannot run circleci build in the container. So the result of circleci local execute is the same error as for circleci build because circleci build delegates its call to the same docker container as the circleci local execute does.

Basically, both feature are not working for me. But, they are also not promoted by circleci --help.