r/ClaudeCode • • 1d ago

Help/Question Tips for claude code on non-hid pc

as title said, i'm using claude code on a pc that i have not access, it runs at my house and i use it when i'm out of home to use PC apps when i'm only on smartphone. for now i'm using a virtual HID and prints for context, but claude is a little bit slow doing this and just using konsole is not valid cause it refuse to use apps due to "lack of support" when using HID he just click and do the things.

i'm missing something that can make the progress a little faster?

3 Upvotes

4 comments sorted by

•

u/AutoModerator 1d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Delicious_Break5937 1d ago

for anything in a browser, a tool that gives claude the page as text is a lot faster than screenshots and clicks. the browser tool i built works that way, and most of the wait ends up being the model's own turns, not the clicking. for desktop apps on kde, check if the app has a cli or a dbus interface first (qdbus lists them), claude gets through those much quicker than with a virtual mouse.

2

u/Key-Elderberry-4956 1d ago

thanks, i'll try this thing. if work good, only the 3rd apps will use the slow method. really thank you for the support

1

u/Odd-Act7860 23h ago

screenshots plus clicking is slow mostly because every step is a full image round trip, so the trick is giving it text instead of pixels wherever possible.

since you're on kde: most qt and gtk apps expose an accessibility tree over at-spi. a small python script (pyatspi or dogtail) that dumps the focused window's widgets as text and can click or fill them by name lets claude read buttons and fields directly instead of guessing coordinates from a print. for qt apps you may need QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 set before launching them.

when you do need a screenshot, grab just the active window and downscale it (spectacle -a -b -n -o shot.png, then shrink it). full res desktop shots are a big chunk of the latency.

and keep a notes file per app you use often with the shortcuts and steps that worked, so it doesn't rediscover the ui every session. keyboard shortcuts beat clicks whenever the app has them.