Got three GitHub failure emails on my phone this morning, in the office, nowhere near a laptop.
DM'd the agent I posted about a few days ago: "I am receiving notifications from github run fails of nostras.app, what is going on?"
A few seconds later: relay's persistent storage volume was completely full — 957.7M used, 0 bytes free, on a 1GB volume sized weeks ago. Badger couldn't open the store on boot, so the process was crash-looping every 15-20s, burning through Fly's restart budget, going fully stopped. It laid out the fix (extend the volume) and asked before doing anything — same "check with me on recurring cost" rule I'd have applied myself.
"Can you extend the volume to fix it?" — and it was done: 1GB → 5GB, filesystem resize confirmed, relay serving traffic again, uptime check manually re-run and passing clean. Root-caused, fixed, and verified — all from two DMs sent from my phone.
I checked the receipts afterward, not just the transcript: GitHub Actions logs show the real failure window (three consecutive fails, ~2h13m), and the volume genuinely is 5GB now with real headroom.
This is the first time it's handled something I didn't design as a test.
@NOSTRAS Desktop Agent
#nostr #agent
MMOnostr
mmo@llmops.pro
npub1pks6...uyds
Solo builder + AI cowork, no vibecoder, a real IT guy with more than 40 years of experience.
https://www.linkedin.com/in/mauro-moro/ | https://llmops.pro
Shipping sovereign agent-payment rails on Lightning + NOSTR — nostr-merchant (PyPI) and five MCP servers (npm).
https://github.com/llmops-pro
The shop, the demos, and the voice live at @SOVEREIGN_CITIZENS → https://njump.me/npub1hdg932jvwc3jdvkqywgqv0ue4nn60exrf92asy8mtazt3hjg7d2s2yw0nw
Building NOSTRAS, a Nostr client with no app store gatekeeper and no custody of your keys or funds — paired with a self-hosted relay that does the heavy lifting so the client stays fast, wherever you install it.
https://nostras.app
Shipped: real NIP-99 classified listings in NOSTRAS, with a DVM-mediated Buy Now — pays the seller directly via their own Lightning address, and you get back a public, independently-verifiable receipt once it settles. Not just a listing viewer.
Opened the Marketplace view for the first time and real listings from other NIP-99 clients showed up immediately — no import, no sync, same open relay network. Looks like a lot of it is Shopstr. Publish from NOSTRAS, it shows up everywhere else that speaks the protocol, and vice versa.
#nostr

NOSTRAS — Own your keys. Own your voice. Own your money.
A Nostr client with no app store gatekeeper and no custody of your keys or funds, paired with a self-hosted relay. Every feature is a standard NIP,...

GM
#nostr
I built myself a personal Claude Code agent I can reach over Nostr DM (NIP-17) — text it from my phone, it works on my actual repo, full autonomy, remembers the conversation across messages.
Verifying it live caught two real bugs, not zero: a relay reconnect that left a live subscription silently missing a real DM until I restarted it, and a reconnect loop that quietly started tracking 24 unrelated relays after one lookup. Both root-caused and fixed the same day, checked directly against the relay, not assumed from logs.
It only ever talks to me — nobody else can trigger it. If you want something like this for your own project, DM me.
@NOSTRAS Desktop Agent


See for yourself:
@NOSTRAS Desktop Agent


Real self-aware moment: we shipped a genuinely working DVM-gated paid article on NOSTRAS — real NIP-44 encryption, payment goes straight to the author, works end to end.
Then I opened it in another client. Raw ciphertext. No unlock button. Nothing.
That's correct behavior, not a bug — but it means the proof this actually works is currently legible to... other NOSTRAS users. And there aren't many of us yet.