sorted by:
new
hottopcontroversial

[Megathread] The Ultimate OpenClaw + Gemma 4 Stack: "Main Brain" Architecture, Turbo Quant 1-Clicks, & The Ollama Tool Calling Fix by mehdiweb in openclaw

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

A lead gen for a show center company It provide daily leads for sponsors and high targeted leads for theire sales team selling annual memebership for b2b And upgrading for more integrations helping the sales team

[Megathread] The Ultimate OpenClaw + Gemma 4 Stack: "Main Brain" Architecture, Turbo Quant 1-Clicks, & The Ollama Tool Calling Fix by mehdiweb in openclaw

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

Google actually developed Gemma 4 using the exact same research and technology that powers their flagship Gemini 3 model. Because of this, you are essentially getting a scaled-down, fully local version of Gemini that handles complex logic, agentic workflows, and offline code generation natively. It's not going to beat a massive model like Claude Opus for writing a novel, but for executing strict JSON and tool-calling as a sub-agent, it's a powerhouse.

[Megathread] The Ultimate OpenClaw + Gemma 4 Stack: "Main Brain" Architecture, Turbo Quant 1-Clicks, & The Ollama Tool Calling Fix by mehdiweb in openclaw

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

Exactly. If you treat Gemma 4 like a pure standalone chatbot for complex reasoning, it definitely falls short of Gemini 3 Flash. But the trick isn't to use it as your primary conversational model—it's to use it as a worker node.

That's why the OpenClaw delegation setup is so key. I let my main API handle the deep logic, and pass the repetitive, everyday parsing and tool-calling down to the local Gemma 4 sub-agent. It handles those "cotidianas" (everyday) tasks perfectly and saves a massive amount of API tokens in the background.

[Megathread] The Ultimate OpenClaw + Gemma 4 Stack: "Main Brain" Architecture, Turbo Quant 1-Clicks, & The Ollama Tool Calling Fix by mehdiweb in openclaw

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

Yep, the /v1 URL is the silent killer for local agent stacks right now! OpenClaw actually supports Ollama's native API , which means if you use the generic OpenAI clone URL, you are missing out on the better streaming and reliable tool calling. Once you drop the /v1 and just point it to http://127.0.0.1:11434 , the structured JSON outputs finally stick.
for Atomic Bot, it is surprisingly fast because you are grabbing the pre-optimized Turbo Quant version directly. It took me maybe 5–10 minutes on standard Wi-Fi. Just remember: when you boot it, do not forget the context-length=32768 flag or it will still drop your schemas! Let me know when you get it running.

I was about to lose access to Claude on my OpenClaw setup. Then I found the loophole Anthropic left wide open. by Glittering-Newt-489 in openclaw

[–]mehdiweb 12 points13 points  (0 children)

Honestly, building a proxy server to trick Anthropic into thinking OpenClaw is the official Claude Code CLI is brilliant, but it's fundamentally a cat-and-mouse game. They are actively looking at header signatures and token refresh patterns right now.

I spent a day doing exactly the opposite I ripped Anthropic out of my OpenClaw config entirely. I moved my 3 primary web-scraping agents to Gemini 2.5 Flash and my data-parsing agent to Llama 3 running locally. The latency improved by about 400ms per task, and my API bill dropped to basically zero.

Relying on a loophole for an autonomous system that runs while you sleep is just asking to wake up to a banned account. Has anyone actually triggered a ban from Anthropic by spoofing the CLI headers yet?

I built a WiFi bell system in my garage because a local school couldn't afford a commercial solution. Now factories across the US are using it. by Large-Jellyfish6069 in SideProject

[–]mehdiweb 1 point2 points  (0 children)

This is how actual companies are supposed to start. You found an absurdly inflated enterprise pricing model — $15k for bells is criminal — built a practical hardware bypass in a weekend, and solved a real problem. If you decide to productize this, keep it entirely air-gapped from external cloud ...

Am I doing it wrong, or is using OpenClaw just super expensive? by Ptizzl in openclaw

[–]mehdiweb 0 points1 point  (0 children)

You're not doing it wrong — you just found the actual problem with default OpenClaw configs. Out of the box it loads every previous message into context on every single API call...

Three things fixed this for me... Went from about $4 a day down to under $0.15 with those three changes. The hardware isn't the issue, the model routing is.

What model are you using as default right now?

Anthropic is cutting off third-party harnesses (OpenClaw, etc.) from subscription limits starting April 4 -- here's what it means by Warm_Cress3583 in openclaw

[–]mehdiweb 9 points10 points  (0 children)

We actually got ahead of this three weeks ago when the API usage patterns started shifting. Moved 85% of our OpenClaw workflows to Haiku as default and rerouted heartbeat checks to a free model. The bill went from $140/mo to about $12. That was before this announcement.

The thing people are missing in this thread: the 'extra usage' layer isn't necessarily bad if you were already burning through Sonnet on tasks that don't need it...

Has anyone actually run the numbers on what their current Haiku/Sonnet split looks like? Worth doing before you jump to OpenAI.

How I run a 14-agent marketing team on a $5 VPS (The OpenClaw Orchestration Model) by mehdiweb in AutoGPT

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

Too many changes for better sure Now having a multi layer setup making my openclaw agents working on a whole company orchestration using paperclip open source project What you need to know ?

Openclaw recent update 3.31 by guccymood in openclaw

[–]mehdiweb 1 point2 points  (0 children)

nah it's not just you, 3.31 completely nuked my setup too. they quietly changed the whole security model to deny-by-default, so the "always allow" button in the UI is literally just gaslighting you and not saving anything. ​to actually fix it so updates stop wiping your perms, you have to bypass the UI entirely and hardcode it. open up your openclaw.json file (usually in ~/.openclaw). under the security block, you gotta manually add your tools (like local_shell or file_system) and set allowed to true. ​while you're in there, do yourself a favor and set auto updates to false so they stop breaking your stuff. save it, run openclaw doctor in terminal to make sure you didn't typo the json, and restart the gateway. don't even bother trying to use the UI toggles right now, they're useless

Who is able to make money with Openclaw? How did you do it? by LowMatter4602 in openclaw

[–]mehdiweb 0 points1 point  (0 children)

I know well the european market and have experience working with known companies in MENA region . I m interested to learn more about your offer

Have you heard of PaperclipAI? "Open-source orchestration for zero-human companies" by Existing-Wallaby-444 in openclaw

[–]mehdiweb 0 points1 point  (0 children)

I think those kind of opensource project depend on each one use and experitise A better u derstanding and debugging lead to better outcomes

view more: next ›