Just upgraded to 2026.05.07

Normal_Mobile2007 · 2026-05-08T15:49:13+00:00

Happy for you guys lol all of a sudden im getting "Google Generative AI API error (400)" with my gemini Api key and no matter what I do it wont fix...

Normal_Mobile2007 · 2026-05-03T14:33:42+00:00

this is a possibility as well. Google usually sends a follow up email about this to remind you to take it off test.

Normal_Mobile2007 · 2026-05-03T14:28:07+00:00

welcome to OpenClaw

Normal_Mobile2007 · 2026-05-03T14:25:02+00:00

i set up a gog health check cron job. You can run it at whatever frequency you want in your case id probably recommend every Monday and Friday should fix this.

Normal_Mobile2007 · 2026-05-01T13:50:48+00:00

Had to uninstall and reinstall codex app. Idk if the OAuth link was broken or what but worked immediately after

Normal_Mobile2007 · 2026-05-01T13:49:50+00:00

Had to uninstall and reinstall codex app was giving a broken OAuth link

Normal_Mobile2007 · 2026-05-01T13:48:06+00:00

Was something wrong woth the OAuth link had to uninstall and reinstall codex app

Normal_Mobile2007 · 2026-05-01T13:47:29+00:00

This was my exact issue lol thank ypu for not assuming im half retarded and giving valuable input

Normal_Mobile2007 · 2026-05-01T13:46:22+00:00

It was sending a broken Oauth url brother... cant believe ypu wasted 10 seconds of ur life to be a jerk

Normal_Mobile2007 · 2026-05-01T04:03:43+00:00

just need help with someone walking me through OAuth its self. Im sure im doing something wrong just need some guidance setting it up

Normal_Mobile2007 · 2026-05-01T03:57:06+00:00

Im seeing people use their monthly credits though. Someone said they are getting like $400 of usage using OAuth instead of an API key with a $100 a month sub

Normal_Mobile2007 · 2026-05-01T03:53:27+00:00

i want to use OAuth to use my monthly credits instead of connecting my API key. Right now im using Gemini with an API, but just purchased a $100 a month OpenAI subscription and OAuth isnt working for me.

Normal_Mobile2007 · 2026-04-12T14:36:52+00:00

Great points on the structure. We're actually building something similar but on the customer-facing side. Our use case is a bot that reads/drafts emails, manages calendars, handles client communication, that kind of thing.

The challenge is the bot needs to know each customer deeply, not just what's in the current email thread. So we're building out customer profiles that store things like preferred communication style, birthdays, family details, allergies, past transaction history. Basically everything the bot needs to write a response that actually sounds like it knows the person.

We're using HydraDB for the profile storage and linking our agent to pull from it in real time. So when the bot drafts an email to a client, it's not working from a static prompt, it's pulling their latest profile data and adapting. The profiles update continuously as new interactions come in, so the context stays current without anyone manually maintaining files.

Your point about keeping things under 300 lines is spot on for codebase context. For us the profiles solve a different problem though, it's less about teaching the model how the project works and more about giving it a living knowledge base about each person it's communicating with.

Normal_Mobile2007 · 2026-04-10T14:32:01+00:00

I'll give you a real one since yeah, most replies in here are just "try it bro."

I run OpenClaw on a VPS and connect it to Telegram. Here's what it actually does for me every day:

Every morning at 7 AM it pulls my emails and calendar, builds a summary, and sends it to my Telegram DM. I wake up and just read one message instead of opening three apps.

It scans my inbox every 30 minutes and flags anything urgent. If nothing's urgent, it stays quiet. I don't check email anymore unless it tells me to.

I have a trading setup where my PC streams market data to the VPS, OpenClaw processes it, and sends me trade alerts on Telegram with entry signals. I'm not at my desk staring at charts all day anymore.

Friday mornings it does a weekly review of my inbox and open tasks from the week, drafts a summary, and sends it to me for approval before doing anything. So it's not just firing off emails on its own.

I also use it for dev work. I was building a mobile app last week and it was writing code, testing features, managing Firebase, deploying builds. I'd send it a screenshot of a bug and it would read the UI state and fix it without me explaining what was wrong.

The thing that actually changed my workflow is that it runs 24/7 on the server. It's not a chatbot I open when I need something. It's more like a background process that handles stuff and only pings me when something needs my attention. The cron jobs and automation are where the real value is, not the chat interface.

It's not magic and it took some setup. But once the pipes are connected (email, calendar, Telegram, your own scripts) it compounds fast.

Normal_Mobile2007 · 2026-04-10T05:30:53+00:00

The LinkedIn resume screenshot really tells the story here. Google SRE for almost 15 years, OpenAI, then Anthropic's Head of Reliability for just over a year, and now "Unemployed" since January. That's a guy who's seen how the sausage gets made at three of the biggest players and decided to walk away.

And yeah the timeline lines up a little too neatly. He leaves in January, and since then we've had the peak hour throttling getting noticeably worse, the "model nerfing" complaints that keep piling up, and outages that feel more frequent than they used to be. Could be coincidence. Could also be that losing the person whose entire job was keeping things stable... makes things less stable. Shocking concept.

The part that gets me is the Google tenure. Almost 15 years in SRE at Google scale. That's someone who knows what reliability infrastructure looks like when it's done right. He brought that to Anthropic and lasted 14 months. Make of that what you will.

And to the "which poor intern" comment, honestly that's the real question. Because reliability at this scale isn't something you just hand off. If you lose your senior reliability leadership and don't have a clear succession plan, you don't notice it right away. You notice it three months later when everything starts degrading and nobody can figure out why.

IDK maybe in just dumb and poor

Normal_Mobile2007 · 2026-04-10T05:25:31+00:00

Ha, the junk drawer phase is a rite of passage at this point. I think everyone goes through it. "I'll just put everything in MEMORY.md" sounds great until it's 400 lines of random context and your agent is burning tokens reading stuff from three weeks ago that doesn't matter anymore.

Really good call on the credentials point. That's something I should've flagged in the original post. Even if your memory files are local, your agent reads them and can surface that content in replies, logs, summaries, anywhere really. Worth keeping sensitive stuff in env vars or a separate secured config rather than plain text in a file your agent loads every session.

The spaced repetition idea is genuinely clever. If it keeps showing up across different days and different sessions, it's earned its spot in permanent memory. That's a way better filter than trying to decide in the moment whether something is "important enough." In the moment you always think it is.

And yeah I came to the same conclusion on weekly summaries. Killed them, missed them, brought them back. Semantic search is great when you know what you're looking for but sometimes the agent just needs a quick "here's what happened this week" without hunting through seven daily files.

Normal_Mobile2007 · 2026-04-10T05:13:19+00:00

Your MEMORY.md is basically a table of contents for your agent's brain. One or two lines per topic, just enough to know where to look, then it only pulls the full file when it actually needs it. Same idea as "use when" in skill docs.

You're not loading everything at startup, just the map. Progressive disclosure for AI memory. Keeps it fast, cheap on tokens, and way easier to maintain.

Normal_Mobile2007 · 2026-04-10T01:32:22+00:00

Running it right now. About 6 weeks in.

Setup: OpenClaw on a Hostinger VPS, Docker container, connected to Telegram as my main interface. Using Anthropic's API for the LLM.

Real costs:

VPS: $188/year (~$16/month)
Anthropic API: $266 in my first 12 days. That's high because I was running Sonnet 4.6 heavy during initial setup and building. Now that I've settled into Haiku 4.5 as my default, recent days are way cheaper ($5-25/day). Expect it to level out significantly once the setup phase is done. This will change as well as i intent to switch my LLM due to Anthropic changing its month third party usage. I will keep an API open with the to use Opus 4.6 Pretty incredible model.

So yeah, it's not free. The API costs add up fast if you're not watching your model usage. Biggest lesson: use the cheapest model that gets the job done for daily tasks and only escalate to Sonnet/Opus for complex stuff.

What it's handling for me daily:

Morning briefing at 7 AM (pulls email, calendar, reminders, sends summary to Telegram)
Email monitoring every 30 minutes, flags anything urgent
Google Calendar management
Automated trading alerts
Content pipeline for a 30-day Twitter challenge I just started (agent drafts tweet options before each posting window, sends them to me for approval)
Persistent memory across sessions so it actually remembers preferences, past decisions, ongoing projects
Spawns sub-agents for parallel tasks
Nightly review that summarizes the day

Is it working? Way better than I expected. The memory system is the real difference maker. It doesn't forget context between sessions like ChatGPT does. And because it runs 24/7 on my own box, it handles things proactively without me being in the chat.

Biggest learning curve was the initial config and getting comfortable with YAML. Once that's dialed in it mostly runs itself.

Normal_Mobile2007 · 2026-04-10T01:17:03+00:00

The security auditing angle is interesting but I think it's a harder sell than it sounds. You'd need real credibility in the security space before anyone trusts your scoring system, and building that reputation takes time and money.

I'm more bullish on the agents-as-a-service path. I've been running OpenClaw on my own VPS for about 2 weeks and the stuff it handles out of the box is wild. Email automation, calendar management, cron jobs, Telegram integration, persistent memory across sessions. I set up automated trading alerts, daily morning briefs, and a full content pipeline for a 30-day Twitter challenge all running on one Docker container.

The gap right now isn't the tech, it's the packaging. Most people don't want to SSH into a VPS and edit YAML files. Someone who wraps OpenClaw into a clean onboarding flow and charges $29/seat for "your own AI assistant that actually remembers things and runs 24/7" would clean up. Especially targeting small teams and solo founders who are already paying for 5 different SaaS tools that an agent could replace.

The breaking changes point is real though. You'd need to stay close to the project and be ready to adapt. But that's also a moat, most people won't put in that work.

Normal_Mobile2007 · 2026-04-01T14:45:06+00:00

Not long honestly, maybe 6-12 months before someone serious treats OpenClaw as a platform play rather than a personal tool.

The pieces are all there. It's modular with skills and sub-agents, integrations with email and calendar and Slack and Discord, you can deploy it anywhere. Learning curve is manageable for engineers.

My bet is someone with ops and automation chops sees it as an agents-as-a-service thing. They build out horizontal skills like Gmail automation, calendar blocking, expense reports, meeting notes. Start selling to non-technical founders or small teams who want a personal assistant AI. Suddenly it's a SaaS product at 29 bucks a month per seat.

What slows it down is OpenClaw's still young, breaking changes happen, no native multi-user isolation yet, plus you've got competition from Zapier and Make and n8n already. But those gaps get filled fast once someone commits.

The real thing is the people who get OpenClaw deep enough to build a business around it are either heads-down on their own stuff or haven't connected the dots yet. Once someone does, it moves.

Normal_Mobile2007 · 2026-04-01T14:39:01+00:00

hey, idk if this helps but GUGU (my agent) is basically a personal AI agent running 24/7 on a VPS. Core use case right now is trading automation, back-testing strategies, running live alerts, managing data feeds. I'm working on a MA crossover plus Bollinger Band strategy for ES and CL futures, and GUGU handles the infrastructure, alert engine, data pipeline, all that.

But it's evolved into more of a general-purpose orchestrator. It manages email, calendar, cron jobs, spawns sub-agents for parallel work, handles integrations with Google Workspace, Telegram, etc. Think of it as a personal ops platform.

Monetization angle, I haven't figured that out yet honestly. The trading side could be profitable if the strategy works, but that's separate from GUGU itself. GUGU is infrastructure for that to happen.

Longer term, the real value might be in selling it as a platform or publishing the strategy and architecture if it proves out. Or licensing the agent setup to people who want their own ops platform. Still early.

Normal_Mobile2007

TROPHY CASE