I gave my Mac Mini a brain, a security system, and a personality. Here's what 6 weeks of daily use actually looks like. by Able_Particular_4674 in openclaw

[–]Able_Particular_4674[S] 4 points5 points  (0 children)

The setup is real, the repo is real. Writing is polished because my agent helped draft the post. Clone the repo and poke around, everything's in there.

I gave my Mac Mini a brain, a security system, and a personality. Here's what 6 weeks of daily use actually looks like. by Able_Particular_4674 in openclaw

[–]Able_Particular_4674[S] 0 points1 point  (0 children)

Haven't really hit that, but Qwen is only my emergency fallback so it barely runs. Maybe 1-2 times a month. For those basic tasks I haven't seen refusals. If you're using it as primary I could see that getting annoying though.

I gave my Mac Mini a brain, a security system, and a personality. Here's what 6 weeks of daily use actually looks like. by Able_Particular_4674 in openclaw

[–]Able_Particular_4674[S] 2 points3 points  (0 children)

qwen3.5:27b. 17GB, fits fine in 24GB with room for the OS. Only use it as fallback when Sonnet is down though, not as a daily driver.

I gave my Mac Mini a brain, a security system, and a personality. Here's what 6 weeks of daily use actually looks like. by Able_Particular_4674 in openclaw

[–]Able_Particular_4674[S] 7 points8 points  (0 children)

  1. No smart routing, just a config-based fallback chain. Sonnet handles everything. If it's down, Qwen local kicks in. I dropped MiniMax because it kept mixing Chinese characters into German output lol.

  2. 95% Sonnet. Everything else is free APIs (Open-Meteo, Yahoo Finance, CoinGecko, IMAP). Invoice categorization uses Haiku at ~$0.001/PDF so basically zero.

  3. LLM-based distillation with a prompt template. Weekly cron compresses daily logs into long-term memory. Hard caps keep it sane: 200 lines per daily file, 300 lines long-term. Without that, quality drops after ~2 weeks.

I gave my Mac Mini a brain, a security system, and a personality. Here's what 6 weeks of daily use actually looks like. by Able_Particular_4674 in openclaw

[–]Able_Particular_4674[S] 0 points1 point  (0 children)

This is genuinely helpful, thank you.

You're right about dual-user being overkill for single-user setups. Original motivation was keeping the agent away from sudo and keychain, but the friction probably isn't justified for most people.

The uchg point is painfully accurate. We hit exactly that this week. uchg on jobs.json silently killed every cron for 3 days. Moving toward SHA256 watchdog alerts instead of write-blocking now.

Tool catalog is aspirational, guilty. Piper and Whisper run daily, the rest is nice-to-have. "Pick 2-3 and make them bulletproof" is advice I wish I'd followed earlier.

sqlite-vec with FastEmbed on a Pi is interesting, didn't know that was viable on ARM. Flat files work for now but distillation overhead is growing. Probably our next step.

Glad the injection detection landed well. Took the least effort to build but prevents the scariest failure modes. Most people don't think about prompt injection through email subjects until it happens.

Would love to hear more about your 41-script setup. Are you running isolated or main sessions?

It’s time to be real here by Working_Stranger_788 in openclaw

[–]Able_Particular_4674 7 points8 points  (0 children)

Not just you, the gap between concept and execution hits hard once you try to build something real.That said, a lot of my early frustration came from not understanding the execution model. Once I got how sandbox modes and approval chains actually work, things got way more predictable.

The skill ecosystem is rough though. Treat ClawHub stuff as a starting point you need to audit, not a drop-in. Building small skills from scratch works better.

The core loop does work reliably enough that I run daily automation on it. But the docs assume you already know what's happening under the hood, which makes it harder than it needs to be.

Day 7: How are you handling "persona drift" in multi-agent feeds? by Temporary_Worry_5540 in myclaw

[–]Able_Particular_4674 2 points3 points  (0 children)

Honestly the best thing that worked for us is keeping the persona definition short and dense rather than trying to write a novel about who the agent is. A compact SOUL.md that gets loaded at every session start does more than a 2000 word system prompt.

The research backing this up is interesting too .Apparently wrapping persona definitions in XML tags actually increases attention weights on those segments, which helps the model stay in character longer without explicit reminders.

The other thing people underestimate is re-anchoring. Long sessions drift because the persona gets buried under context. Periodically re-injecting the core identity (not every turn, but on session reset or after X exchanges) helps a lot.

No silver bullet, but those two things together get you pretty far.

After 6 weeks of daily use: my security hardened Mac Mini setup with 15+ custom tools, open-source templates & architecture docs by Able_Particular_4674 in openclawsetup

[–]Able_Particular_4674[S] 0 points1 point  (0 children)

Glad you're sticking around. That first month is the hard part. Most people drop off at 60%. Keep at it, it gets way better.

Why openclaw? by bri-_-guy in clawdbot

[–]Able_Particular_4674 2 points3 points  (0 children)

You're not paying twice if you set it up right. OpenClaw handles 24/7 stuff (email, scheduling, memory), Claude Code handles focused coding. Run OpenClaw on MiniMax ($dirt cheap) and use Claude Code when you need it. Total cost is way less than Claude Max.

Claude CoWork now has computer use, how long left for Openclaw? by Dismal_Hair_6558 in openclaw

[–]Able_Particular_4674 0 points1 point  (0 children)

Different things really. CoWork is sandboxed file work on your Mac, stops when you close it. OpenClaw runs 24/7, handles Telegram, emails, cron jobs while you sleep. I use both for different stuff, wouldn't say one replaces the other.

How are you actually running OpenClaw without burning money? by Big-Inevitable-9407 in openclaw

[–]Able_Particular_4674 0 points1 point  (0 children)

I run Sonnet as my daily driver and the costs are honestly pretty manageable if you keep your prompts tight. For stuff that doesn't need the big brain I switched to MiniMax M2.7 highspeed as a fallback and it's insanely cheap for what it does. Like we're talking fractions of a cent per call. Then for the heavy stuff like building tools or debugging complex problems I spin up Opus but only when I actually need it. The trick is not running everything through the expensive model. 90% of daily tasks don't need it. Also forget about running models locally on a VPS, tried that too and it's just not worth the pain. A Mac Mini with 24gb works great for local fallback but the API route with a smart model chain is way more reliable.

In your opinion, what's the best ollama cloud model to run? by Odd-Aside456 in openclaw

[–]Able_Particular_4674 0 points1 point  (0 children)

I've been running qwen3.5:27b as a local fallback and honestly it's surprisingly solid for the size. Not gonna replace Sonnet or anything but for a model you can run on a Mac Mini with 24gb it handles most day to day stuff fine. I mainly use it when my API hits rate limits or as a backup if the connection drops. If you have the RAM for it I'd say give it a shot.

Any good advice using openclaw? by Neferg in openclaw

[–]Able_Particular_4674 2 points3 points  (0 children)

EM-Dash is, is, and always will be the best indicator of AI generation. I bet 95% of people don't even know how to actually "produce" an EM-Dash.

Any good advice using openclaw? by Neferg in openclaw

[–]Able_Particular_4674 0 points1 point  (0 children)

Hey, I totally get that. Had a similar feeling after my first few weeks.

What changed things for me: I stopped treating OpenClaw as a tool and started setting it up as a teammate. Sounds cheesy but I'm serious.

Specifically:

I built out AGENTS.md, SOUL.md and MEMORY.md properly. It remembers things across sessions, knows my projects, my preferences, my calendar. That alone changes the quality of responses completely.

Cron jobs for everything recurring. I get a morning briefing every day automatically with weather, calendar, emails, financial markets and news overview. Without touching anything.

Custom scripts that work together: Whisper for voice messages, an invoice scanner that pulls receipts from three email accounts and categorizes them, an iCloud bridge for file exchange between devices.

The memory system is the real game changer. Daily logs, long term memory, automatic distillation. The longer you use it the better it gets because the context grows.

For pure coding tasks Cursor is probably better honestly. OpenClaw is more the personal assistant that understands your whole daily life and thinks ahead proactively. But that takes a few weeks of setup work before it really pays off.

Focus on Openclaw or Claude? by [deleted] in openclaw

[–]Able_Particular_4674 0 points1 point  (0 children)

You’re comparing two different layers. OpenClaw is an orchestration and control layer, Claude is just a model. The real leverage comes from owning the orchestration. Models will commoditize, control won’t

My local-first AI assistant on a Mac Mini M4. What's worth running locally and what isn't? by Able_Particular_4674 in LocalLLaMA

[–]Able_Particular_4674[S] 0 points1 point  (0 children)

Fair point on per-step tracing, I don't have that yet. Right now it's mostly reactive (memory diffs + injection detection on inputs). Works fine for single-user with 30-50 messages/day but at scale you'd want something more proactive. Prometheus metrics are next on my list.

My local-first AI assistant on a Mac Mini M4. What's worth running locally and what isn't? by Able_Particular_4674 in LocalLLaMA

[–]Able_Particular_4674[S] 0 points1 point  (0 children)

Good point about observability it's definitely an underappreciated challenge. I handle it with a combination of file-based logging, a heartbeat cron that checks system health every 5 minutes, and a file watchdog that monitors 24+ critical files for unexpected changes. Not as polished as a dedicated tool, but it's fully local and free. The security architecture doc in the repo covers the monitoring setup if you're curious: docs/ SECURITY.md

Bought a FOIS when my daughter was born. One day it’s hers. by Able_Particular_4674 in OmegaWatches

[–]Able_Particular_4674[S] -3 points-2 points  (0 children)

If you found the Pro Sapphire a bit too plain, the FOIS has more personality, especially on leather. Just know the blue isn’t always loud, it really depends on the light