Google AI Pro Account Restored After OpenClaw OAuth Ban — Appeal Form Works
A Reddit user reports their Google AI Pro account was restored approximately three months after losing access due to connecting it to OpenClaw via Google OAuth. The ban only affected AI services — Gemini CLI, Antigravity CLI, and other AI tools — while Gmail, Drive, and YouTube continued working.
Timeline and Resolution
- Ban triggered after linking Google account to OpenClaw via OAuth.
- Google Support, Google One Support, Reddit, GitHub, and Google AI Developer Forum were all unsuccessful.
- After ~3 months, Gemini CLI showed a link to an official appeal form:
https://forms.gle/hGzM9MEUv2azZsrb9. - Submitted the form; about 10 days later, Antigravity CLI was working again.
- No email notification — access was silently restored.
Key Takeaway
If your Google AI Pro account is banned after using OpenClaw OAuth, the official appeal form may be your best option. The user reports eventual success, though the process took months and provided no communication.
📖 Read the full source: r/openclaw
👀 See Also
Todoist connector removed from Claude, custom setup required
The official Todoist connector is no longer available in Claude. Users can add Todoist as a custom connector using the MCP URL https://ai.todoist.net/mcp, but this requires a Claude Pro or Max subscription.
Giving Claude M365 Access via Power Automate and a FastMCP Server
A developer built a lightweight MCP server that lets Claude interact with Microsoft 365 (inbox, calendar, OneDrive, Planner, Excel, Word) using Power Automate webhooks — no admin Graph permissions needed.
Optimizing Qwen3.5-9B on RTX 3070 Mobile with ik_llama.cpp: Config Tweaks and Benchmarks
A developer shares optimization findings for running Qwen3.5-9B Q4_K_M on an RTX 3070 Mobile 8GB GPU using ik_llama.cpp, achieving ~50 tokens/second generation speed and significant prompt evaluation improvements through configuration adjustments.
Structuring Claude Code Agents with CLAUDE.md and .claude/ Directory Patterns
A developer shares their approach to running multiple AI agents using Claude Code, with each agent having its own directory containing a CLAUDE.md file and a .claude/ directory with rules and skills. The key insight is separating always-on context from on-demand workflows to optimize token usage and response quality.