Live data from Hacker News

NanoClaw Adopts OneCLI Agent Vault

nanoclaw.dev

11–20 of 36 posts

Re: NanoClaw Adopts OneCLI Agent Vault

#11
post #3

From a security standpoint, I'm glad that people are starting to pay attention to basic security practices. That said, while I'm hardly a fan of MCP (judge for yourself by reviewing my previous comments on the matter), at least its security model was standardised around OAuth, which in my opinion is a good thing, albeit with a few small issues. I personally prefer CLIs, but their security is in fact worse. A lot wors…

Yeah, I think that’s broadly right.

MCP has plenty of problems, but standardising on OAuth was one of the better calls. Expiry, scopes, rotation, delegated access, all much better than the usual CLI pattern of long-lived API keys. The CLI story there is still pretty rough.

And once the policy model is host/path matching, GraphQL and JSON-RPC become awkward immediately unless the proxy starts understanding payload semantics.

Re: NanoClaw Adopts OneCLI Agent Vault

#13
post #9

I really don't understand the fascination with openclaw. Can only assume it's mostly just guerrilla marketing spam.

can someone explain openclaw/nanoclaw use cases to me? I also do not understand the uses right now. Are we just grasping at usefulness ?

It's a mess in terms of code/filesystem organization, but it's nice to be able to text somebody "hey, create and deploy a branch of codebase X with feature Y" while I'm on the go. Not exactly magic, and probably not sustainable, but there's definitely something to it.

Also, attaching an LLM with my raindrop.io and Todoist credentials to cron is fun. Haven't got the kinks worked out, yet, but it's pretty incredible how much data-shifting I can do now. Saved me a lot of clicks.

Re: NanoClaw Adopts OneCLI Agent Vault

#15
post #3

From a security standpoint, I'm glad that people are starting to pay attention to basic security practices. That said, while I'm hardly a fan of MCP (judge for yourself by reviewing my previous comments on the matter), at least its security model was standardised around OAuth, which in my opinion is a good thing, albeit with a few small issues. I personally prefer CLIs, but their security is in fact worse. A lot wors…

> I bet we will move from CLIs to something else in about 3-6 months.

My bet would be OpenAPI specs. The model will think its calling a cli but we intercept the tool call and proxy it with the oauth credentials.

There are some implementations already out there in open web ui and bionic gpt.

Re: NanoClaw Adopts OneCLI Agent Vault

#16
post #9

I really don't understand the fascination with openclaw. Can only assume it's mostly just guerrilla marketing spam.

can someone explain openclaw/nanoclaw use cases to me? I also do not understand the uses right now. Are we just grasping at usefulness ?

Most things I use it for could be done without it, it's just more convenient and entertaining.

I had it make a daily aviation weather brief for a private airpark. It uses METAR, outdoor IP cameras I have including one that looks at a windsock and another that looks at the runway surface, and a local weatherstation. It sends me a text message with all of that information aggregated into "It's going to be really windy this afternoon, visibility is high, but there is ice on the runway surface", that sort of thing.

The thing is, all I had to do is point it to a few endpoints and it wrote the entire script and set up a cron for me. I just gave it a few paragraphs of instructions and it wrote, then deployed the rest.

The other day, there was a post here about a new TTS model. I wanted to try it out, so I gave my claw the github URL, and it pulled everything down and had it running without any effort on my part. Then it sent me a few audio messages on discord to try.

When I'm away from home, I can text it to say "what's going on at home" and it will turn on the lights around the house, grab a frame from each camera turn lights back off, and give me a quick report. I didn't have to do any work other than tell it I wanted that skill.

I also have a group chat with some friends on signal that's hilarious. It roasts us, gives us reminders, lets us know about books we might be interested in, that sort of thing. It's really fun.

Re: NanoClaw Adopts OneCLI Agent Vault

#17
post #9

I really don't understand the fascination with openclaw. Can only assume it's mostly just guerrilla marketing spam.

can someone explain openclaw/nanoclaw use cases to me? I also do not understand the uses right now. Are we just grasping at usefulness ?

Honestly, I installed Hermes Agent last weekend, and while there isn't any "killer use case", the combination of "your little assistant agent on it's own machine" and good messaging integration is really quite cool.

I've set it up with it's own mailbox, and a git token to make PRs etc. So far I've set up a few automations (check thing X and message me if Y) but the combination of enough "intelligence" to be able to triage/suggest solutions, messaging via a standard messaging app, and a sandboxed environment for code execution, all packaged as "this is your helpful assistant" is fun.

In theory it's nothing I couldn't do with Claude Code + some integrations, but having all of that out of the box + setting the expectation that this is legitimately a helpful assistant you can message and email with any mad request you have does shift the way I see it.

Though yes, the more fun you have with it, the more of a security threat the whole thing becomes, and it's slightly terrifying. I briefly considered giving it view only access to my emails and decided that was just too high risk. But treat it as a vaguely clueless but not incompetent intern and works?

Re: NanoClaw Adopts OneCLI Agent Vault

#18
post #8
post #5

Interesting! I still wouldn't give to any claw access to my mail accounts, but it is a step in the good direction. I love how NanoClaw is aggregating the effort of making personal assistants more secure. Good job!

I don't get the idea of giving a claw access to your own mail account, but am now playing with the idea of it having its own email account that I selectively forward to - that offers almost the full benefit, with significantly less risk.

yeah, that's the approach I've taken. I quite liked the idea of giving it full delegated perms on my email account and calendar (eg, dig out that email and reply back to them for me) but the risk profile is just too high, and forwarding emails where needed mostly works.

Re: NanoClaw Adopts OneCLI Agent Vault

#19
post #9

I really don't understand the fascination with openclaw. Can only assume it's mostly just guerrilla marketing spam.

can someone explain openclaw/nanoclaw use cases to me? I also do not understand the uses right now. Are we just grasping at usefulness ?

Here are some things I use it for:

1. monitoring anything online and giving me a summary when something changes

2. contribute or make edits to any online forum (where TOS allows it)

3. Giving it access to any API / cli gives you a natural language interface to that service.

4. Memory / notes retrieval. It can search through its discussion / thought history and answer detailed questions about what happened in the past.

5. Any standard GPT cases but it has a much more specific memory of who you are and what you might be interested in.

6. If you ever want to add capabilities you just tell it to add a new skill to do xyz and it just does it.

Re: NanoClaw Adopts OneCLI Agent Vault

#20
> You can set rate limits so an agent can only send or delete a few emails per hour

Nice idea, but it will not work. Agents are so resourceful and determined, they will find that weird call which can delete all emails with one request (/delete?filter=*)

Post reply on HN