Live data from Hacker News

NanoClaw Adopts OneCLI Agent Vault

nanoclaw.dev

21–30 of 36 posts

Re: NanoClaw Adopts OneCLI Agent Vault

#21
post #9

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

To be clear this is not OpenClaw. Maybe the difference doesn't matter to you.

NanoClaw is pretty interesting to me. It's a really small piece of software and a different category of software than we've seen before, one that you are expected to customize by editing it yourself (via Claude Code).

For that reason alone I find it interesting to play around with. I don't find it actually useful at the moment.

Re: NanoClaw Adopts OneCLI Agent Vault

#23
post #9

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

People don't want to have to manage or derive context from searching across multiple different apps, emails, spreadsheets, CRMs, etc. It's like having your own personal assistant or oracle.

I find it interesting how European and American devs (especially on HN) are so luddite about AI and OpenClaw, but Chinese, Indian, and Israeli developers both domestically and in the diaspora have been adopting this kind of tooling fairly rapidly.

And then people wonder why the center of gravity for a number of engineering subfields is slowly shifting.

Re: NanoClaw Adopts OneCLI Agent Vault

#26
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.

Same here. Coupled with configuring the agent's email account at the provider to only be able to send and receive to my email address.

Re: NanoClaw Adopts OneCLI Agent Vault

#27
I'm a little shocked that someone like 1Password hasn't released a vault access + approvals model. There are a lot of little menial tasks that I'd love for an agent to take care of ("book me a hair appointment next week when my calendar says I'm free"). Agent has access to a locally synced calendar and can see the existence of a password for the booking portal in my vault, asks to use it, I get a push notification and can approve.

These kinds of things aren't common enough for me to want to set up a programmatic policy, and are also low sensitivity enough that I don't mind giving access to complete the task. If it later asks to log into my bank, I decline.

I know the devil's in the details for how to actually do this well, but I would love if someone figured it out.

Re: NanoClaw Adopts OneCLI Agent Vault

#28
post #4

Nice upgrade. userpsace HTTP proxies are a good start and should make unlikely that a secret gets into the context window due to a high permission read. There are a few missing pieces in the agent security world in general 1. Full secret-memory isolation whereby an agent with root privileges can't exfilrate. Let's assume my agent is prompt injected to write a full-permissions script to spin up OneCli, modify the dock…

At a basic levels, access layers should be aware of operations that are Read-only and operations that are Write/Delete. It should be easy to give agents access to read anything, then require permission/prompt to execute any state changing operations.

Re: NanoClaw Adopts OneCLI Agent Vault

#29
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 ?

Twitter grasps at usefulness, mostly for engagement farming (those TUI dashboards with a thousand agents mucking around).

Me and others I know use it for things similar to the following:

- I get a lot of emails from various organisations about talks and events (today there was one by andrew barto). I ask it to read emails from announce@*, filter to those adjacent to my field, or from notable people, fill the RSVP form using generic details(which it knows!) and then add it to calendar (I don't want to add all)

- giving me the latest updates of my wandb run

- gives me morning abstract+summary(intro + conclusion) of arxiv papers matching keyword / author i specify.

- a specific product I buy (grocery) is very popular and runs out of stock quick every week. I have it watch my quick commerce provider's website and tell me when it becomes available.

- do simple things like summarise new papers add to group zotero

- send discord msg to collaborator, wait for an OK, and then do merge on this repo from this branch provided checks pass

If I had to "pitch" it, I would say this:

Remember those "taking 4 hours to write an automation for something that takes 2m of your day" activities that you never ended up automating? Well it no longer takes 4 hours to write the automation. Most of the above is just a python script no new ability really, but now it takes 1m to write. Making it worth it.

For longer tasks you do very often, I would say you're better off writing a python script. Similarly for important scripts that you want good error handling for.

And really long complex scripts means you'll have to debug it. At which point you might as well write it yourself in the first place.

The telegram gateway makes it super convenient. Many mobile UIs are garbage as you know, so you can ask it to wrangle info into any format and put it there.

However, it absolutely drinks tokens IME. Hard to get it to limit tokens without destroying usefulness. I get some credits so I don't pay. If you pay and are not rich then it's probably not worth it at today's prices.

Re: NanoClaw Adopts OneCLI Agent Vault

#30
post #25

The main problem still isn’t solved. It’s not that agents have access to something the shouldn’t have but that the creates havoc exactly with the access they are allowed to have.

OneCLI doesn't solve the problem of the agent wrecking havoc, you're right, but it does help protect against the agent leaking private credentials from prompt injections / malicious skills.
Post reply on HN