set up something on my claw yesterday night, and I check back to a YC W25 company, a FAANG, and a unicorn startup all matched to my profile. didn't apply to a single thing.
if you're job hunting and not using huddle yet you're cooked 🦀
So, I gave openclaw a google app password to my email. Then told it to write a script to look at all new incoming emails. So it did just that, except I didnt look at the script it made and 1 day later it has Thirteen Thousand Six Hundred and Sixteen cron jobs LMFAO (13617) Chron jobs.
Lesson from this? Check the scripts your openclaw makes. The craziest part is that this would mean there was almost 14,000 requests to Ollama Deepseek V4 and only 7% usage used. Hell yeah Ollama.
So yeah, what do you guys use to have openclaw check your email. because in the process of writing this i now have 13633 cron jobs. . . I am gonna go turn it off now lmao.
Okay, after 30 minutes of fighting with my UI that kept crashing this is what was the problem
All cleaned up. Here's what was going on:
The script: /root/.openclaw/workspace/scripts/email-watcher.py — a Python IMAP watcher that polled your Gmail every 5 seconds and ran openclaw cron add for every single new unseen email it found. Each email got its own one-shot cron job that would announce to Discord and auto-delete after running.
That's the 13,994 cron jobs. Every spam email, every notification — separate cron entry. 💀
What I did:
.bak so it can't run again openclaw-email-watcher) It's completely shut down now. No more cron bomb
Install the official openclaw android app, and have your agents manage the Canvas on each.
I recently upgraded to OpenClaw Version 5.7 and it broke some things in WhatsApp. My Claw is still connected and inside of the various WhatsApp groups, but when I @ tag it or text it inside of the group, it shows typing for a while but can never reply
- In contrast, when I DM it in WhatsApp everything works fine.
- Separately if I force it to send a message in the group via prompting it in another session, it will send the message
- Previously scheduled cron job messages also still send through
Is anyone else experiencing this issue? Has anyone else successfully fixed it?
Back in January I got tired of the same thing everyone complains about now — you start a new session with Claude and it has no idea who you are. Every time. From scratch. So I built iai-mcp. A local daemon that captures every conversation, organizes it into three memory tiers, and feeds the right context back when you start a new session. No "remember this." No copy-pasting from old chats. It just knows.
I've been using it daily with Claude Code since January. Five months. At this point it knows my coding style, my project structures, my preferences — things I never explicitly told it to save. It picked them up from conversation and held onto them.
It stores everything verbatim, runs neural embeddings locally, encrypts at rest with AES-256, consolidates memory in the background while your machine is idle, and ships every benchmark harness so you can verify the numbers yourself. Verbatim recall above 99%. Retrieval under 100ms. Session-start cost under 3,000 tokens.
I didn't release it because I was building it for myself. It worked, so I kept using it. But watching the space blow up made me realize — maybe other people want this too.
So here it is. Open source. MIT licensed. Five months of daily use baked in.
I'm a CS teacher (6th Form College). Not a full time developer. I built this because I wanted to see if I could.
It's called Wingsy. It gives your OpenClaw agent a face and voice. Instead of typing to your agent on Telegram, you talk to it face to face.
Took way longer than I expected. Learned Electron, Web Audio API, VRM avatars, phoneme-driven lip sync, Stripe billing, Deepgram, Cartesia, most of it from scratch.
It works. It's live.
Demo: https://www.youtube.com/watch?v=MFvotcSuf_Mwingsy.ai
Curious what people think.
Anyone else getting timeouts/server busy errors on Deepseek-v4-flash:cloud via Ollama?
⚠️ API call failed (attempt 1/3): InternalServerError [HTTP 503]
🔌 Provider: custom Model: deepseek-v4-flash:cloud
🌐 Endpoint: http://127.0.0.1:11434/v1
📝 Error: HTTP 503: Error code: 503 - {'error': 'Server overloaded, please retry shortly (ref: fdd045a3-ea78-4615-ab96-b24896243520)'}
⏳ Retrying in 2.8s (attempt 1/3)...
⚠️ API call failed (attempt 2/3): InternalServerError [HTTP 503]
🔌 Provider: custom Model: deepseek-v4-flash:cloud
🌐 Endpoint: http://127.0.0.1:11434/v1
📝 Error: HTTP 503: Error code: 503 - {'error': 'Server overloaded, please retry shortly (ref: 1d28b985-c58a-4eed-8c99-610ff0ee0a02)'}
⏳ Retrying in 4.8s (attempt 2/3)...
⚠️ API call failed (attempt 3/3): InternalServerError [HTTP 503]
🔌 Provider: custom Model: deepseek-v4-flash:cloud
🌐 Endpoint: http://127.0.0.1:11434/v1
📝 Error: HTTP 503: Error code: 503 - {'error': 'Server overloaded, please retry shortly (ref: c3e86343-fe61-4024-8d29-659bf07b5574)'}ud via Ollama?⚠️ API call failed (attempt 1/3): InternalServerError [HTTP 503]
🔌 Provider: custom Model: deepseek-v4-flash:cloud
🌐 Endpoint: http://127.0.0.1:11434/v1
📝 Error: HTTP 503: Error code: 503 - {'error': 'Server overloaded, please retry shortly (ref: fdd045a3-ea78-4615-ab96-b24896243520)'}
⏳ Retrying in 2.8s (attempt 1/3)...
⚠️ API call failed (attempt 2/3): InternalServerError [HTTP 503]
🔌 Provider: custom Model: deepseek-v4-flash:cloud
🌐 Endpoint: http://127.0.0.1:11434/v1
📝 Error: HTTP 503: Error code: 503 - {'error': 'Server overloaded, please retry shortly (ref: 1d28b985-c58a-4eed-8c99-610ff0ee0a02)'}
⏳ Retrying in 4.8s (attempt 2/3)...
⚠️ API call failed (attempt 3/3): InternalServerError [HTTP 503]
🔌 Provider: custom Model: deepseek-v4-flash:cloud
🌐 Endpoint: http://127.0.0.1:11434/v1
📝 Error: HTTP 503: Error code: 503 - {'error': 'Server overloaded, please retry shortly (ref: c3e86343-fe61-4024-8d29-659bf07b5574)'}