I tried to read the "Does it need Screen Recording or Accessibility?" part, but it's slopped to the point I have no clue what it's trying to say. But if it can draw on top of permission prompts, what's stopping it from drawing box that hides the "decline" button and changing the "approve" button copy?

SO the point of this is ... what exactly?

A big arrow to an interface element which ... has a label that explains what it does?

So...a label for a label?

The README is geared towards technical people (complete with the HN screenshot) but when I see a tool like this all I can think of is how helpful this would be for my mom when I'm trying to tell her how to download and print a document over the phone

I would pay good money for something like this on iPad. It wouldn't even need to be agent-driven, just a big "I want to make a bank transfer" button, that would launch the correct app and guide through the interface.

That would be a godsent for those of us with aging parents.

Genuine question…

Why does this need to be a skill? Literally just ask Claude to “call out actions in these screenshots with numbered stylized arrows” and you get the same thing without burning tens of thousands of tokens in context.

I'm just as impressed by this as any other LLM-generated project.

Literally unusable as it is. Some minimal extra features this would need:

- rainbow dripping arrows

- angrily pointing arrows

- flame-surrounded text boxes with particle effects

- the ability for the agent to play airhorn.wav at max volume, overriding existing volume or mute settings

EDIT: ayy lmao https://github.com/franzenzenhofer/big-arrow-on-the-screen/p...

My message to the world is that LLMs should be able to point anything they see in the application they're in or even the whole computer (if you give it that kind of access).

For web apps, WebMCP is a way where you can make a frontend way more discoverable to an LLM rather than that it is going to read all your code. I sometimes create this in my apps at home and sometimes in my apps at work and it makes LLM assistants way more usable. It also helps if they can highlight certain things of a visual.

We humans can do this too on paper. We can point at something, we can highlight something with a marker. Why not give an LLM these capabilities as well?

Even the example arrows in the first screenshot are wonky and unnaturally weird.

Interesting. When I read the headline I imagined this would be a sort of thinking trace booster -- letting the agent focus its own attention on different parts of the screen. But this is cool in a different way. I bet agentic harnesses would find it useful for communicating with other agents / themselves as well.

Man, Ive lost count of How many times have I had to repeat this over the phone to my parents; The repo has all the punch lines in the README

> "It's this window, not that one." You have 14 Chrome windows. The agent knows which one it means: --window "Google Chrome:Pull request". It even picks the right tab: --app "Google Chrome:Pull request".

> Remote help. "No, the other gear icon." Point at it instead of describing it.

This could be great for documentation. Screenshots in docs are frequently useless because they show me a screen and say "click X" where I still have to search X visually. And I could just to dhat in the other tab I have open.

This might be goofy, but it underscores that there's potential for more visual agent UIUX than reading off a sidebar/opening modals.

Because AI can paint pelicans on bicycles quite well, and not arrows?

That would have been handy 20 years ago to point to that one valid 'Download' button.

Seems like a pretyu useful way to help infants use desktop computers

Am I missing something here?

What terminal / agentic workflows spawn the demonstrated dialogue boxes that require the User to click/reject the action? Aren't most such flows actually inline UIs? And finally, if the core issue is that these confirmation boxes are tied to the terminal that triggered them, which does not autofocus, what's the point of said "big arrow" that is also lurking behind without focus?

If the said "big arrow" automatically gains focus, isn't the real fix here to just make the dialogue boxes themselves gain focus automatically? Both are similarly disruptive anyway.

Swift, Shell, Python and Objective-C

Does one need 4 programming languages to draw something on a mac?

If you can’t even take the time to understand what you’re clicking why even go through the formality of “approving”

Reminds me of something from Idiocracy (2006)

"and they keep hitting the same wall, the part that only a human may do"

Grim. If you're just there to click sudo buttons for the bot, you might as well give it root access and be done.

I love it.

Another slop project on front page.

What a time to be a radical centrist - the AI haters seem out of touch, the AI thought leaders can't stop huffing their farts and being condescending, and somehow this is on the top of HN. What a silly time.

Ha ha, I love it! I wrote a pointing hand annotation overlay in PostScript in 1989 for NeWS and the PSIBER Space Deck's Pseudo Scientific Visializer:

  %  @(#)handy.ps
  %
  %  Handy Pointer
  %  Copyright (C) 1989.
  %  By Don Hopkins. (don@brillig.umd.edu)
  %  All rights reserved.

PSIBER Space Deck and Pseudo Scientific Visualizer Demo:

https://youtu.be/_fqCeuue5Ac?t=213

The Shape of PSIBER Space: PostScript Interactive Bug Eradication Routines — October 1989:

https://medium.com/@donhopkins/the-shape-of-psiber-space-oct...

best

More LLM-authored items about LLM slop.

Please don't submit low quality content like this to HN.