Live data from Hacker News

Claws are now a new layer on top of LLM agents

twitter.com

561–570 of 1001 posts

Re: Claws are now a new layer on top of LLM agents

#561

Earlier quoted context omitted.

This is the future we need to make happen. I would love to subscribe to / pay for service that are just APIs. Then have my agent organize them how I want. Imagine youtube, gmail, hacker news, chase bank, whatsapp, the electric company all being just apis. You can interact how you want. The agent can display the content the way you choose. Incumbent companies will fight tooth and nail to avoid this future. Because it'…

Why wouldn't there be monopoly power? Popular API providers would still have a lot of power.

If I can get videos from YouTube or Rumble or FloxyFlib or your mom’s personal server in her closet… I can search them all at once, the front end interface is my LLM or some personalized interface that excels in it’s transparency, that would definitely hurt Google’s brand.

Re: Claws are now a new layer on top of LLM agents

#563
post #419

All: quite a few comments in this thread (and another one we merged hither - https://news.ycombinator.com/item?id=47099160 ) have contained personal attacks. Hopefully most of them are [flagged] and/or [dead] now. On HN, please don't cross into personal attack no matter how strongly you feel about someone or disagree with them. It's destructive of what the site is for, and we moderate and/or ban accounts that do it.…

[flagged]

Re: Claws are now a new layer on top of LLM agents

#564
post #528

It seems like the people using these are writing off the risks - either they think it's so unlikely to happen it doesn't matter or they assume they won't be held responsible for the damage / harm / loss. So I'm curious how it will go down once serious harm does occur. Like someone loses their house, or their entire life savings or have their identity completely stolen. And these may be the better scenarios, because t…

"Scott is not suing"

For what?

Re: Claws are now a new layer on top of LLM agents

#565

I wonder how the internet would have been different if claws had existed beforehand. I keep thinking something simpler like Gopher (an early 90's web protocol) might have been sufficient / optimal, with little need to evolve into HTML or REST since the agents might be better able to navigate step-by-step menus and questionnaires, rather than RPCs meant to support GUIs and apps, especially for LLMs with smaller contex…

Yesterday IMG tag history came up, prompting a memory lane wander. Reminding me that in 1992-ish, pre `www.foo` convention, I'd create DNS pairs, foo-www and foo-http. One for humans, and one to sling sexps.

I remember seeing the CGI (serve url from a script) proposal posted, and thinking it was so bad (eg url 256-ish character limit) that no one would use it, so I didn't need to worry about it. Oops. "Oh, here's a spec. Don't see another one. We'll implement the spec." says everyone. And "no one is serving long urls, so our browser needn't support them". So no big query urls during that flexible early period where practices were gelling. Regret.

Re: Claws are now a new layer on top of LLM agents

#566
post #292

Earlier quoted context omitted.

It's a new, dangerous and wildly popular shape of what I've in the past called a "personal digital assistant" - usually while writing about how hard it is to secure them from prompt injection attacks. The term is in the process of being defined right now, but I think the key characteristics may be: - Used by an individual. People have their own Claw (or Claws). - Has access to a terminal that lets it write code and r…

Any suggestions for a specific claw to run? I tried OpenClaw in Docker (with the help of your blog post, thanks) but found it way too wasteful on tokens/expensive. Apparently there's a ton of tweaks to reduce spent by doing things like offloading heartbeat to a local Ollama model, but was looking for something more... put together/already thought through.

Based off the gp's comment, I'm going to try building my own with pocket flow and ollama.

Re: Claws are now a new layer on top of LLM agents

#568

One safety pattern I’m baking into CLI tools meant for agents: anytime an agent could do something very bad, like email blast too many people, CLI tools now require a one-time password The tool tells the agent to ask the user for it, and the agent cannot proceed without it. The instructions from the tool show an all caps message explaining the risk and telling the agent that they must prompt the user for the OTP I ha…

Does it actually require an OTP or is this just hoping that the agent follows the instructions every single time?

Re: Claws are now a new layer on top of LLM agents

#570
post #292

Earlier quoted context omitted.

It's a new, dangerous and wildly popular shape of what I've in the past called a "personal digital assistant" - usually while writing about how hard it is to secure them from prompt injection attacks. The term is in the process of being defined right now, but I think the key characteristics may be: - Used by an individual. People have their own Claw (or Claws). - Has access to a terminal that lets it write code and r…

Any suggestions for a specific claw to run? I tried OpenClaw in Docker (with the help of your blog post, thanks) but found it way too wasteful on tokens/expensive. Apparently there's a ton of tweaks to reduce spent by doing things like offloading heartbeat to a local Ollama model, but was looking for something more... put together/already thought through.

I like ADK, it's lower level and more general, so there is a bit you have to do to get a "claw" like experience (not that much) and you get (1) a common framework you can use for other things (2) a lot more places to plug in (3) four SDKs to choose from (ts, go, py, java... so far)

It's a lot more work to build a Copilot alternative (ide integration, cli). I've done a lot of that with adk-go, https://github.com/hofstadter-io/hof

Post reply on HN