Live data from Hacker News

Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

rajveerbachkaniwala.com

51–60 of 95 posts

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#51
post #24

Earlier quoted context omitted.

I really don't get it. Started using computers when that was the only affordable way to use computers. For some reason, some people really love to live in 1970's with their expensive HiDPI monitors.

I wasn't alive in the 70s, but I still prefer a terminal. I can string together a complex series of text-related tasks far more effectively as a shell pipeline than I can by pointing and clicking in a UI. I can scale that sequence of tasks out to operate on every file on the filesystem if I want, or down to a single character in a single file. Claude Code being a full-featured TUI is also helpful because I can quickl…

I can do the same in a language REPL, with the advantage it doesn't need to emulate a teletype.

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#52

Why are we emotionally tied to command line interfaces Desktop apps are a second class citizen that do not get feature parity Lot of actions on Claude Code seem much more suited for a thoughtfully designed GUI Even the chat responses and links therein can benefit from judicious use of rich text and formatting and real hyperlinks to other parts of the UI or elsewhere Favourite Skills can be toolbar buttons or menus if…

>Why are we emotionally tied to command line interfaces Being a power user, having used computers for more than 30 years, I usually prefer GUI because that's an evolution over CLI. Going from the basic interpreter on ZX Spectrum to the command line in MS DOS had me mesmerized. Going from the DOS CLI to Windows 95 GUI, had me me mesmerized, too. I think people in general consider themselves more pro and "hackers" if t…

Which is a pity, a real hacker uses a graphical environment inspired from Lisp Machines, Interlisp-D, Smalltalk, selecting code in the REPL with "do it", fixing it on the fly in the debugger and "redo it", changing the work environment in the flow.

Unfortunely they hear that and only understand Emacs.

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#53
post #3

The last "When this stops being needed" needs one amendment: "Or stop using Windows."

Valve could actually create a need for native Windows games.

As it stands the only reason I have to pain myself back into using Linux on bare metal laptops, instead of VMs, is independence from US technologies in European soil, which also implies not having to care about Claude.

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#54
post #50
post #24

Earlier quoted context omitted.

I really don't get it. Started using computers when that was the only affordable way to use computers. For some reason, some people really love to live in 1970's with their expensive HiDPI monitors.

It might be overcompensation. I think UI, UX and GUIs got better up until the 90s, and early 2000s, but then somewhere GUIs suddenly got a lot worse. So a modern CLI is better and more standardized than a modern GUI.

A modern CLI would be a REPL.

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#55

Earlier quoted context omitted.

But can you paste an image into it? I have a similar setup, but I access it directly via iTerm2 instead of VS Code's terminal. I've figured out the right terminal settings to get copying/pasting text to work (including with neovim's + register), but not images. Would be nice to paste images, though. Currently I have to SCP them over.

I've actually never tried it before. I just ran some tests now on a mac: If I copy a file in Finder and paste it into a claude session, it shows in the TUI as [Image #1]. If I do the same, but paste into a claude session running over SSH, it pastes the path to the file, not the data. If I open the image in Preview, copy the pixels (CMD-A, CMD-C), pasting that into a terminal does nothing. So it looks like CC just put…

I suspect the first case worked as intended, and VS Code is greasing the wheels. I'm sure there's a way to get it working in iTerm 2, though I wouldn't be surprised if the solution was some Goldbergian chain of forwarded unix sockets and a helper daemon living inside the sandbox.

Thanks for mentioning yoloAI, though. I started off sandboxing via devcontainers using kata & cloud hypervisor set up as a custom docker runtime. It worked well enough, but nested docker was super slow due to virtio-fs limitations. I recently moved to sysbox and it's a bit quicker. It's probably not as airtight as kata/chv, but good enough to keep Claude from writing a security test that deletes my whole filesystem [1].

1: https://github.com/anthropics/claude-code/issues/28521

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#56
post #24

Earlier quoted context omitted.

I really don't get it. Started using computers when that was the only affordable way to use computers. For some reason, some people really love to live in 1970's with their expensive HiDPI monitors.

I wasn't alive in the 70s, but I still prefer a terminal. I can string together a complex series of text-related tasks far more effectively as a shell pipeline than I can by pointing and clicking in a UI. I can scale that sequence of tasks out to operate on every file on the filesystem if I want, or down to a single character in a single file. Claude Code being a full-featured TUI is also helpful because I can quickl…

can't agree more, I now run my agents in parallel with "agentbox claude", "agentbox opencode" and it teleport my project and settings to an hetzner VPS

For those interested: https://github.com/madarco/agentbox

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#57
My main issue was the ability to paste images when using ClaudeCode via ssh on a remote machine, so I solved it by having Claude write a quick bridge that fetches the image in your clipboard, rsync it to the server and paste the correct image path in your clipboard: https://github.com/mdrzn/claude-screenshot-uploader

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#59

Why are we emotionally tied to command line interfaces Desktop apps are a second class citizen that do not get feature parity Lot of actions on Claude Code seem much more suited for a thoughtfully designed GUI Even the chat responses and links therein can benefit from judicious use of rich text and formatting and real hyperlinks to other parts of the UI or elsewhere Favourite Skills can be toolbar buttons or menus if…

i would gladly use claude code via the desktop app, but it lags behind the cli in terms of supported features, so i just don't bother. last i tried, it didn't support executing CC within WSL while desktop is running in windows.

Re: Why Ctrl+V won't paste images in Claude Code on WSL, with a fix

#60

Why are we emotionally tied to command line interfaces Desktop apps are a second class citizen that do not get feature parity Lot of actions on Claude Code seem much more suited for a thoughtfully designed GUI Even the chat responses and links therein can benefit from judicious use of rich text and formatting and real hyperlinks to other parts of the UI or elsewhere Favourite Skills can be toolbar buttons or menus if…

Claude Code can't slopcode working GUIs

That's the real reason.

If you don't believe me, take a look at the leaked codebase from a couple weeks ago. It's the stuff of nightmares, because too many junior devs slopcoded in all places without any plan or understanding of software architecture patterns. They never actually take the time to refactor, there's dozens of outdated redundancies and orphaned modules all over the place.

Without good architecture patterns, there can be no good GUI nor good UX.

Post reply on HN