Hello together,
(Posting in English — I'm German, no Dutch, but you all seem to handle English effortlessly and I'm leaning on the browser translator for the Dutch replies in this thread, so hope that's fine.)
I stumbled upon this thread crawling through the internet and want to share what I am actually doing: I started building something in this space before OpenClaw publicly existed. First public write-up was around New Year's on r/LocalLLaMA, a few weeks before OpenClaw's launch: reddit.com/r/LocalLLaMA/comments/1q0rrxr — completely independent, just happened to converge on the same idea at the same time. It's moved on a lot since then, so figured this thread is a good place to share where it stands now.
It's called AIfred-Intelligence, self-hosted, no cloud dependency required:
github.com/Peuqui/AIfred-Intelligence
My hardware setup grew over the past year from my 24/7 Mini-PC server with one Tesla P 40 in an eGPU-Adapter to this:
https://peuqui.github.io/AIfred-Intelligence/examples/Hardware_Setup_Frankenstein_MiniPC.html
Re: the security concerns @CyBeRSPiN and @DeNachtwacht raised — that's actually one of the things I spent the most time on, because I didn't want a "give it your credentials and hope" model either. It's a 5-tier permission system (READONLY → COMMUNICATE → WRITE_DATA → WRITE_SYSTEM → ADMIN), configurable per channel — so Telegram can be allowed to read your calendar but not delete files, independent of what the browser session is allowed to do. Plus inbound sanitization and a "rule of two" that blocks write-tier tools from ever being triggered by an external message (no drive-by file deletion via a crafted email).
On the local-model side (@DeNachtwacht, saw your Qwen 3.5 35B post) — it runs llama.cpp/Ollama/vLLM with automatic VRAM-aware context calibration, so it's not GPU-list-hardcoded, it measures your hardware and fits itself to it.
It also does the Telegram/Discord/email routing thing @MennoE built by hand on his VPS, just built in as a plugin system.
Some other bits in there, in case anyone's curious what else it's grown into:
- Complex autonomous workflows chaining multiple tools in one go — e.g. photograph a business card, and it reads the data via vision, creates the Google Contact, checks your calendar for a free slot, books the appointment, and sends you the photo + contact back over Telegram — all from one prompt, no clicking through steps.
- Built on top of:
- Websearch and -crawling
- Google Contacts, Calendar, Drive, Essential PIM
- Files, Documents, RAG
- Persistent Memory per agent
- unlimited Agents with own persona, e.g. AIfred is my personal butler with distinct noble english speech
- Camera surveillance mode (motion + face recognition, GDPR blackout zones you paint directly over the live feed, nightly auto-description of events) — runs as a background watcher, survives browser disconnects
- Sandboxed code execution — writes and runs Python itself, renders plots/interactive HTML straight into the chat
- Sub-agents: any agent can delegate a self-contained task to a fresh instance with its own tool loop, so the main context doesn't get flooded on long research/coding jobs
- Multi-agent debate modes — a critic agent and a judge agent, with a "Tribunal" mode where they argue it out and a verdict gets rendered, plus a few other modes (consensus voting, free-form multi-agent discussion)
- Local TTS/STT voice interface with voice cloning, plus custom firmware for an old Echo Dot as a dedicated voice terminal
- ...
Anyway — not trying to pitch it, genuinely curious what this crowd thinks given how deep you've all gone into the OpenClaw rabbit hole already.
And no, it isn't a commercial product, just open source, a journey through agentic coding from the curious start how two agents would perform, when they are able to discuss with each other to a project, that got totally out of hand , even hardware wise...
Happy to answer questions.
/u/164119/crop5a5a2a556d2af_cropped.png?f=community)
:strip_icc():strip_exif()/u/1677928/crop66000a25a1ab3_cropped.jpg?f=community)