Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nvidia NemoClaw

github.com

Post reply on HN
Print view View original

91–100 of 291 posts

Re: Nvidia NemoClaw

#91

Post by danielbln »

g947o wrote: post #10
Iolaum wrote: post #6

Earlier quoted context omitted.

While I don't have OpenClaw installed and not sure how I 'd use it I doubt all the hype around it is because it doesn't solve a real problem. The project grew to huge popularity organically!!! How can that happen if it doesn't serve a need people have?

Maybe let me ask this question: How is this any different from NFT?

I'll ignore the bait and answer: NFTs were gambling in disguise, these claws are personal/household assistants, that proactively perform various tasks and can be genuinely useful. The security problem is very much unsolved, but comparing them to NFTs is just willfully ignorant at best

Re: Nvidia NemoClaw

#92

Post by hypfer »

jesse_dot_id wrote: post #88

The fully autonomous agentic ecosystem makes me feel a little crazy — like all common sense has escaped. It feels like there is a lot of engineering effort being exhausted to harden the engine room on the Titanic against flooding. It's going to look really secure... buried in debris at the bottom of the ocean. When a state sponsored threat actor discovers a zero day prompt injection attack, it will not matter how iso…

Well, at least we share the same world as these people, meaning that we too will experience the consequences of their actions.

Isn't that a nice perspective

Re: Nvidia NemoClaw

#93

Post by otabdeveloper4 »

here2learnstuff wrote: post #9

It’s impressive someone early in their career shipped this. There seems to be a stark increase in high-quality AI/data projects from early-career engineers lately and I'm super curious what’s driving that (and honestly speaking: a little jealous).

OpenClaw is many things, but decidedly not "high-quality".

Re: Nvidia NemoClaw

#94

Post by hypfer »

mjr00 wrote: post #86
chill_ai_guy wrote: post #74

Earlier quoted context omitted.

Lol you think these github repos just materialize as is? They probably did all the iteration and development internally and then ported it over to a github repo and made it public afterwards

No they didn't. You can see all the commits as this was built iteratively[0]. This project started development on Saturday morning and now it's here. This is pretty common now, people love to rapidly throw together stuff and show it off a few days later. The only thing different about this from your average Show HN sloppa is that it's living under the NVIDIA Github org, though that also has 700+ repositories[1] in it…

Cash in on the claw brand recognition by having "claw, but Nvidia".

And, to be fair to them, it works. It sticks. It gets the desired reactions.

Re: Nvidia NemoClaw

#95

Post by elif »

I kind of hope nemoclaw uptake and spark usage pushes ARM into the spotlight for LLM development, making it the primary release target rather than x86.

This could be the opening we need to wrangle a truly opensource-first ecosystem away from Microsoft and apple.

Re: Nvidia NemoClaw

#96

Post by sayYayToLife »

Netcob wrote: post #65

Am I missing something? Why is everyone talking about sandboxes when it comes to OpenClaw? To me it's like giving your dog a stack of important documents, then being worried he might eat them, so you put the dog in a crate, together with the documents. I thought the whole problem with that idea was that in order for the agent to be useful, you have to connect it to your calendar, your e-mail provider and other servic…

[dead]

Re: Nvidia NemoClaw

#97

Post by elif »

mjr00 wrote: post #86
chill_ai_guy wrote: post #74

Earlier quoted context omitted.

Lol you think these github repos just materialize as is? They probably did all the iteration and development internally and then ported it over to a github repo and made it public afterwards

No they didn't. You can see all the commits as this was built iteratively[0]. This project started development on Saturday morning and now it's here. This is pretty common now, people love to rapidly throw together stuff and show it off a few days later. The only thing different about this from your average Show HN sloppa is that it's living under the NVIDIA Github org, though that also has 700+ repositories[1] in it…

Sorry to be the one to inform you that we edit history in git.

There has been reporting on nemoclaw for the last couple weeks. Are you supposing that journalists were writing about software that hadn't even been designed?

Re: Nvidia NemoClaw

#98

Post by sayYayToLife »

jesse_dot_id wrote: post #88

The fully autonomous agentic ecosystem makes me feel a little crazy — like all common sense has escaped. It feels like there is a lot of engineering effort being exhausted to harden the engine room on the Titanic against flooding. It's going to look really secure... buried in debris at the bottom of the ocean. When a state sponsored threat actor discovers a zero day prompt injection attack, it will not matter how iso…

[dead]

Re: Nvidia NemoClaw

#100

Post by hardsnow »

hmokiguess wrote: post #84
Netcob wrote: post #65

Am I missing something? Why is everyone talking about sandboxes when it comes to OpenClaw? To me it's like giving your dog a stack of important documents, then being worried he might eat them, so you put the dog in a crate, together with the documents. I thought the whole problem with that idea was that in order for the agent to be useful, you have to connect it to your calendar, your e-mail provider and other servic…

Yes, although what I think is different in this setup here is the OpenShell gateway override, as they mention: > NemoClaw installs the NVIDIA OpenShell runtime and Nemotron models, then uses a versioned blueprint to create a sandboxed environment where every network request, file access, and inference call is governed by declarative policy. The nemoclaw CLI orchestrates the full stack: OpenShell gateway, sandbox, inf…

OpenShell is the gem here indeed. A lot of good ideas like network sandbox that does TLS decryption and use of policy engine to set the rules. However:

> Credentials never leak into the sandbox filesystem; they are injected as environment variables at runtime.

If anyone from the team is reading - you should copy surrogate credentials approach from here to secure the credentials further: https://github.com/airutorg/airut/blob/main/doc/network-sand...

Post reply on HN