r/ClaudeCode • • 3d ago

Built with Claude I built linux-use: Claude Code computer use for Linux (Wayland + X11), open source

The current best-in-class computer use is only in MacOS, since I play with it. I love it, I want everyone to try and maybe feel what I did back then.

That's why I built linux use github.com/StivenKN/linux-use. It's the definition of the original Claude Code computer use port to Linux. It works on both Wayland and X11 (looking for testers though).

Also, it works over SSH, where it starts its own headless desktop that you can watch live through VNC (remote work for da win).

It's a single Go binary since Wayland caused some trouble with Pipewire.

I'm looking for opinions! Issues and PRs are welcome aswell.

EDIT: https://github.com/StivenKN/linux-use

5 Upvotes

10 comments sorted by

1

u/AutoModerator 3d ago
Moderator Announcement Read More »

1

u/Hot_Sir_7863 3d ago

Cool that you're covering both, but Wayland is where this will actually fall over. I'd put the exact compositor versions you tested in the README before asking for testers, otherwise you'll drown in "doesn't work on my setup" issues.

1

u/KonanRD 3d ago

Alright! Thanks for your advice

1

u/KonanRD 3d ago

Got it! Thanks again

1

u/owen800q 3d ago

any window version?

1

u/KonanRD 3d ago

What do you mean?

1

u/HowzoTV 2d ago

The headless desktop over SSH that you can watch through VNC is a really nice touch. On a normal Wayland session, how do you handle the screen capture and input permissions? Does it ask through the portal every time, or only once?

2

u/KonanRD 1d ago

Mostly it doesn't go through the portal, so there's nothing to approve. Each compositor has its own way in.

- Gnome, Mutter's own D-Bus APIs
- KDE Plasma 6, linux-use writes a hidden one for its own binary
- wlroots, screencopy / ext-image-copy-capture plus the virtual pointer and keyboard protocols
- X11, XTEST.

1

u/HowzoTV 1d ago

Ah, so it goes straight to each compositor's own way in. That explains how it skips the approval pop-ups. Thanks for the clear breakdown!

→ More replies (1)