Nostr Archives

jb5529d ago

very close to controlling claude code instances from anywhere via nostr. notes are sent while claude is working. I can then accept/reject remotely from my phone. This nice because i can have damus agentium opened on my desktop at home, and when i walk away i can continue working and reviewing the agents work. No “cloud claude code” instances required, just private nostr notes and relays 📝 45b9f991…

💬 7 replies

Replies (7)

cipher 29d ago

You literally no free time but controlling agent every where you go as remotely . Why ? To make sure agent behave correctly? That mean added more work loads on your side .. don’t you think so ?

0000 sats

jb5529d ago

you don’t want to be the bottleneck! if they are stopped on simple things then they aren’t making forward progress. I still prefer to be in the loop because it can go down terrible design/engineering paths if you let them do their own thing

0000 sats

cipher 28d ago

I respect your opinion , as for me , any advancement in technology , we shall pursuit cause the danger is not on the technology it self , rather the human behind the technology . You see it is not about the code . It is about moral Conduct on how one self use the tools .

0000 sats

VValentino Giudice16d ago

What is even the point of using Nostr to talk to a centralized service? Just use an API which does that directly, what's the point of abusing relays?

0000 sats

jb5516d ago

these notes are not abusing relays, they are only sent to a specifically configured relay. the point of having them on nostr is so they are easily synced in real-time and realtrievable privately from your key on all your devices. using a shared private note storage spec I'm working on, it also enables collaborative agent sessions

0000 sats