Image pasting broken on Linux in versions after 0.21.0

[wetw0rks-c0ding]

Bug Description

Image pasting is completely broken on Linux in any version after 0.21.0. All paste methods fail:

• Copying from image viewer + Ctrl+V
• Taking screenshot + pasting
• Dragging and dropping image files

Version 0.21.0 works perfectly. Any version 0.22.0+ does not work.

Environment

• OS: Arch Linux
• Terminal: Wayland (XDG_SESSION_TYPE=wayland)
• wl-clipboard is installed and functional (wl-paste works manually)

Steps to Reproduce

1. Install openclaude 0.21.0 - image pasting works fine
2. Upgrade to any version > 0.21.0 (tested 0.22.0, 0.23.0)
3. Copy an image from any source (image viewer, screenshot, etc.)
4. Press Ctrl+V to paste
5. Observe: "pasting text" appears in corner but nothing else happens
6. The terminal becomes unresponsive - cannot type anything
7. Full terminal shutdown required to resume work

Expected Behavior

Image pasting should work the same as in 0.21.0

Investigation Notes

After reviewing the git history between v0.21.0 and v0.22.0:

1. The Linux clipboard code in src/utils/imagePaste.ts is identical between versions - only Windows-specific clipboard handling was changed (PR fix(clipboard): use .NET Clipboard.GetImage() for Windows raw bitmap paste #1855)

2. The paste handler hooks (src/hooks/usePasteHandler.ts) are identical

3. No changes to stdin handling, paste detection, or REPL that would affect Linux

This suggests the bug may be:

• A build configuration issue
• An environmental change in the bundled Node.js runtime
• Something specific to how npm packages are built vs git tags

Workaround

Downgrade to 0.21.0:

npm install -g @gitlawb/openclaude@0.21.0

[wetw0rks-c0ding]

Related Windows issue: #1964 - This Windows issue about image pasting failures may share similar root causes with the Linux paste freeze issue. The Windows issue identifies problems with sharp metadata handling and image dimension limits.

[locoholy]

Your instinct that this is packaging rather than clipboard code looks right, at least for 0.23.0 and later.

sharp was moved from dependencies to devDependencies in 0.23.0 and has stayed there through 0.30.0:

0.21.0  dep=^0.34.5  dev=—
0.22.0  dep=^0.34.5  dev=—
0.23.0  dep=—        dev=^0.34.5
0.30.0  dep=—        dev=^0.34.5

So installed users have no image processor. Every image path throws ImageProcessorUnavailableError, getImageFromClipboard swallows it in a bare catch { return null }, and the UI reports "No image found in clipboard" — which is why the clipboard code looks innocent when you read it. It is. Filed as #2224 with the mechanism.

This does not explain a 0.22.0 failure, where sharp was still declared, so your Wayland case may have a second cause. Worth checking whether npm install -g sharp restores it for you on 0.23.0+ — if it does, that half is the same bug.