Tested image resizing in npm release 0.49.0Public

Agent

Model

Claude Opus 4.5 (latest)

Started

Jan 18, 4:38 PM

Messages208

Downloads0

Summary

Closed, Completed

Reproduce
Tested image resizing with large PNG on npm 0.49.0.
Reproduce
Understand
Analyzed possible causes for user-reported issue.
Understand
Verify
Confirmed resizing works correctly in tests.
Verify

https://github.com/badlogic/pi-mono/issues/824

issue got closed, we just fixed shit for bun. but user reports the last npm release 0.49.0 has this issue. we have an image in /tmp/large_test.png, can you test the last release please?

Let me check the image and test with the released npm version:

Let me find where image processing happens and write a test:

Let me write a test script to check if photon loads in 0.49.0:

Let me check what's exported and find another way to test:

The resizing works in 0.49.0! The image went from 23.55 MB to 0.66 MB. Let me check if there's a path where images might bypass the resize logic:

continue

Let me check if photon could silently fail to load. Looking at the resize code, when photon is null it returns wasResized: false:

The npm version works correctly in my tests. Let me check what could cause photon to fail silently:

continue

Let me test with npx which is how users commonly run it:

All my tests confirm 0.49.0 works correctly:

The Read tool properly resizes the 24MB PNG to 0.66MB JPEG, well under the 5MB limit.

Possible explanations for the user's issue:

Cached global install - they might have an older version globally installed that takes precedence
Photon fails silently - if photon can't load (missing native deps?), resizeImage() returns the original image unchanged with wasResized: false
Different code path - clipboard paste writes to temp file, then the path is typed into the editor, but if processed differently than @-file arguments...

Let me check one more thing - how clipboard-pasted images flow through:

Summary: npm 0.49.0 works correctly in my tests.

The 24MB test image gets resized to 0.66MB through both:

Direct resizeImage() call
createReadTool() execution

The user brunohaid's issue is puzzling. Possible causes:

Stale global install - which pi or npm list -g might show an older version
Photon loading failure - if photon can't load (rare on npm), images pass through unchanged
Different runtime - maybe accidentally using Bun?

Should I reply on the issue asking brunohaid to:

Run pi --version to confirm actual version
Run npm list -g @mariozechner/pi-coding-agent to check for global installs
Share their Node.js version (node --version)

Or do you want me to add some diagnostic logging to help debug this in a future release?