I asked Hermes if everything at home was OK. It told me the gateway was down, and named the two services it took with it.
That is Homelab Watch, a plugin I built for Hermes. One page for the servers, the router, a VPS and the sites I care about.
If you already run Hermes, what do you want it to watch first?
30
I ran one command on my own logs. Thirty days of AI work, at API-equivalent prices: $787. Paid in subscriptions: $84.
npx ax-route audit
It reads local Claude Code, Codex, Kimi, Hermes and OpenClaw logs. Nothing is uploaded.
github.com/lpsmurf/ax-route
1
1
30
I asked Hermes if everything at home was OK. It named the one service that broke — and the two it took down with it.
Homelab Watch: a Hermes plugin that watches every system on your network from one page. Servers, your router and wifi gear, a VPS, your websites, and any device you add.
My entry for the Hermes Agent Plugin Hackathon @NousResearch.
ONE ROOT CAUSE, NOT TEN RED LIGHTS
▸ Every target names a parent
▸ When a gateway dies, its dependents fold into a single incident
▸ So you get "Demo gateway is down, taking 2 more with it" instead of three separate alarms
ALERTS THAT COST NOTHING
▸ /homelab alerts on telegram creates a no_agent cron job through Hermes' own cronjob_manage
▸ It posts only when an incident opens or resolves
IT WATCHES YOUR AGENTS, NOT JUST YOUR MACHINES
▸ A post_api_request hook counts Hermes' own token use per day (counts only, never prompt text)
▸ Priced from a sourced table and split: absorbed by your subscription, saved by cheaper models, saved by free local models, and what you actually spent
▸ A model with no published price shows tokens, never an invented dollar figure
▸ Measured on my own machine over the last 30 days, at API-equivalent prices: $787 of AI work. Paid in subscriptions: $84.
A COST ROUTER:
▸ Ships in shadow mode: it logs what could have moved and changes nothing until you trust it
hermes plugins install homelab-watch
github.com/lpsmurf/hermes-ho…
4 days in @SpoutFi's beta with real signed txs. The 0%-borrow/covered-call design is clever, docs unusually honest, vault UX best-in-class — and I've got stories (a 53h silent outage, an order that never filled). Full report + evidence: github.com/lpsmurf/spout-fin…
4
107
L Plo 🧲 retweeted
More of this, please:
@plubtcm's and @nft_plg's Solana Ecosystem Tuesday, Touch Grass Edition, funded by a Superteam NL grant, builds real friendships, not just Discord threads.
Founder deep-dives, simple Solana education for retail, member spotlights back on X.
The blueprint exists. Just needs more of it so we can grow even more.🌱
L Plo 🧲 retweeted
Bento Beta Bounty is officially complete ✅
Over the last 2 weeks:
→ 81 feedback submissions
→ 15 winners
→ dozens of bugs, edge cases, and UX issues uncovered
→ countless product suggestions for the next version
Huge thanks to everyone who tested Bento, filed reports, submitted PRs, connected real trading bots, and tried to break the product before launch.
Some of the biggest improvements coming from this cohort:
• Jupiter trust classification
• protect() handling for blocked actions
• intent vs transaction verification
• on-chain / off-chain workflow gaps
• wallet onboarding improvements
Special shoutout to our Top 5 contributors:
🏆 @mel_sol1
🏆 @uledjend
🏆 @plubtcm
🏆 @onadeonft
🏆 @Ademola102
And a huge thank you to @superteam @SuperteamJapan @SuperteamEarn for helping accelerate this campaign and connecting us with an incredible group of builders and testers.
This beta validated something important:
People aren't asking whether AI agent security is needed. They're asking when Bento will be production-ready.
Public beta is coming soon.
L Plo 🧲 retweeted
Touch grass with us today 🌱
Superteam NL members are organizing Solana Ecosystem Tuesdays!
Devs, founders, artists, investors, curious minds - all welcome
📅 Today, 10:00-15:00
📍 Gallery MINA, Amsterdam
Come through 👇
Let's be honest: if you still use @Polymarket, it's on you.
You're stupid, that's it.
They're criminals and deserve to fail, but after so many cases, you should just forget about them. We all know this space is toxic.
I can already count dozens of times where they deliberately resolved markets incorrectly, and today just adds to their fraud.
Iran keeps saying that they didn't sign or agree to any peace deal, yet Polymarket is resolving this June 15 market to "Yes."
We don't even know what that "deal" is, because Iran doesn't agree to most of the U.S. requests. So this "deal" could probably just be a ceasefire extension, which wouldn't even qualify to resolve that market to "Yes" (as stated in their rules).
Grifters keep grifting.
If you're building on @Solana, play with solana.new before day one. ⚡
Don't waste your first hackathon hours on absolute basics.
Spin up examples. Break things. Deploy something tiny.
You want day one to be about your idea — not your setup.
(You'll have plenty of other things to break later, trust me.)
2
1
73
Don't treat the hackaton as just a weekend project.
Treat it like a startup audition. 🎭
The best outcome isn't only a prize. It's:
• A real team
• A validated problem
• Investor attention
• Accelerator consideration
• Momentum after submission
Build like you might keep going.
1
46
Your first hackathon will be messy. You'll overscope. You'll break things. You'll rewrite the pitch too late. You'll wonder why nothing works at 2 AM.
That's normal. That's the game. 🏟️
Survival = reduce chaos + ship clearly + use every tool available.
Special Thanks to @wigby @superteamNL @evolu_sol for the guidance and support throughout Colosseum 🙌
61















