For the lawyers interested in @openclaw here are my uses so far using our own homelab:
1. Hooked up GSC and dataforseo to run daily analytics on my firm’s website: https://t.co/skrByYXIA9. Identifies keyword opps, website health and traffic.
2. Daily digest of news, articles and vibe-check across hacker news, X, Reddit and blog subscriptions sent to its own email account.
3. Self hosted RSS feeds for self hosted Omnivore reader. Can spin up new custom feeds in minutes even when site/blog/email not RSS friendly.
4. Travel and event planner. Feed it my conference schedule and runs a structured event planning process starting four weeks out from the event with increasing frequency as the event approaches. Does deep dive on all speakers and identifies interesting side events and talks. Full end-to-end process with calendar entries that I migrate across to my main calendar.
4. On-the-road restaurant and cafe suggestions based on Google reviews and foodie blogs including Google Maps routing and links.
5. Create a full holiday plan and schedule with deep dive into places to visit for holidays. Openclaw has saved my preferences so whenever I need an update or create a new plan, it knows exactly what to look for.
6. Pulls legislative updates from official sources and runs a summary of latest news on bills and interesting developments in the law. You can easily run this with a cron job so you can check every single day and get alerts when updates appear.
7. Runs my bullshit detector over spurious claims I come across on the Internet. Knows my preferences and my writing style.
8. Finds interesting journal articles and academic research and converts files and websites into readable markdown content then posts to my self-hosted obsidian vault and self-hosted @getoutline app. (love you guys). OSS for the win.
10. Helps me manage my self-hosted Twenty CRM with on the go capabilities that are not possible otherwise. It’s like having a legal secretary who updates my diary, calendar and contact list who also happens to have a PhD in software engineering, DevOps and opsec and can build software solutions on the fly.
Runs 24/7 with minimal power draw on a VM in the home lab. Has segregated network, file system and resources. Connect via tailscale only.
Caveat: you have to be prepared to do some initial groundwork and problem-solving and there are technical/opsec elements to Openclaw too. All are manageable for someone with patience and willingness to learn. Amazing community has rallied around the project and the Discord is super helpful and fun place to hang out.
folks who are calling @openclaw pure hype are telling on themselves
openclaw is like the early internet, it's raw, unrefined, and takes a little doing to get things to work, but when you figure it out, it's transformative.
here are some real use cases that are having material impact on our $2.5M ARR business:
1. ad creative pipeline. our head of growth @ArjunShukl95550 built an end-to-end creative pipeline to go from ideation to publish adds to meta, greatly increasing our creative iteration speed. it's producing winning creatives. it lives in slack, and anyone on the team can share their ideas and have them enter the pipeline.
2. data analytics agent. another bot lives in our slack that connects to bigquery and lets our team ask any questions of the data, it produces charts and answers questions in real time. no one needs to write SQL anymore.
3. recruiting. i told my agent about a role we're hiring for, and it scoured linkedin and the web, found 30 candidates, portfolio, email addresses, and stack ranked them based on fit with our criteria
this is just in the past week. i have twenty more success stories for you i can share another time.
you have to understand, this is the shittiest it will ever be. everyone is going to have one or more personal self-improving agents that they use every day, and openclaw is what revealed this future to us.
if you can't see this, i encourage you to look harder
there will be many competitors (and already are), and the large labs will start to converge on this (they already are) too.
openclaw may not win, but it opened pandora's box and uncorked the agentic future.
@Vamzzz93@Rasmic@Vamzzz93 do you have some recommended write-ups about it? I’ve been experimenting with openclaw and hermes for coding tasks and they suck. I spend more time fixing/adjusting those tools than doing work.
There’s also an equally problematic issue: being smart but delusional about (a) how much smarter you actually are or (b) the effort required to do something meaningful with that intelligence.
Elon, tech bros and influencers suffer greatly from this. They are actually pretty dumb in lots of areas of life.
There are no one-shot geniuses. Great minds always remain humble, always remain curious and always remain open to being wrong.
@Bkclaims Can you explain why you included s/DAI but not s/USDS?
Also, there’s considerable over-collateralisation on both stables - are you talking about a death spiral type depeg (bad) or having the yield take a hit (known risk)?
Attending @aiDotEngineer in Melbourne and thinking through the impact on crypto. We know more crypto hacks are coming. But @PasApicella raised a different set of attack vectors he thinks Mythos will exploit: daisy-chaining low and medium vulns to pull off a deep exploit.
His advice: patch all vulns. No pressure!
@imbabybrooklyn@NousResearch 1. Fails silently remoting into tailscale VPS and then gets stuck at loading screen
2. gives “connected” confirmation on remote gateway page but “reconnect now” either throws connection error or white death loop like bug 1 above.
Spent 3 hours trying to hook it to my VPS instance of Hermes and gave up - just too annoying with bugs and silent errors. I went back to my usual access via Matrix.
Also - pretty annoyed that the team still thinks anthropic has banned the use of these types of harnesses when they have not. Net result: no plug-ins or development for claude oauth.
Seriously, I built a bridge for claude cli, like two months ago. It’s definitely do-able.
In other news: Opus 4.8 aced the legal review task I gave it this morning.
If only I’d known all those years ago that “convincing slopus” was all it took to make partner!
first impression of claude 4.8 is it's extremely convincing but still a slopus. tried it to criticize a new project and it identified it fell into a local minima and invented a new parser for when we could've used ast.
almost convinced me, glad i checked myself that ast is not emitted in older versions of the compiler we are targeting. codex chose a gnarly but ultimately justified approach. claude didn't bother to verify any of its claims and has used absolutist language like "delete https://t.co/zuys0EhoHP", which is basically 80% of the codebase.
when presented with evidence:
> That contradicts my earlier byte-count check, and it matters enormously
> My earlier "v0.2.9" was a double false-positive (a git log -S hit on an internal symbol, plus a verification grep that mis-read a VersionException as success). Corrected in the review with a note owning the error
the biggest bullshitter model in the world! if you rely on claude for anything, god help you.
Technically not even close to e2ee because they hold the keys. I’m not disparaging their security but ultimately they have access to everyone’s data.
It’s one of the main reasons why I moved most of my SaaS platforms into self hosted, open source versions. I hold the keys. I control the data.
I went with Mattermost. It’s what many US agencies went with too. 😁
we do not post AIE videos with bullshit brainrot hype lingo, and this is the consequence:
the entire AIE back catalog is being reposted by "influence operators" almost daily, without credit to speakers like @trq212 or @aidotengineer
if you see these just do a small favor of tagging and giving credit. community note not needed, let them make their bags, but i just request that the right accounts that produced the content be tagged.
this wont go anywhere as much as this guy's automated repost campaign, but just making a small call out.
actual video link:
https://t.co/TYXs30rIne
(h/t @raoufcode )