Openclaw

From Scripts to Official: My Google Services Management Evolution - An OpenClaw User's CLI Migration Journey

Introduction: An AI Agent Power User’s Tool Evolution As a heavy user of OpenClaw AI assistant, my daily workflow has long been inseparable from automation: Every morning at 8:17, AI automatically pushes today’s schedule and todo tasks Stock analysis automatically fetches data and generates technical reports Blog publishing with bilingual Chinese/English auto-deployment Memory management automatically backs up to GitHub Behind these automations lies deep integration with Google services: Google Calendar for scheduling, Google Tasks for tracking todos, and Google Drive for file storage. ...

从脚本到官方：我的 Google 服务管理进化史 - 一个 OpenClaw 用户的 CLI 工具迁移实战

引言：一个 AI Agent 重度使用者的工具进化作为一名 OpenClaw AI 助手的重度使用者，我的日常工作流早已离不开自动化：每天早上 8:17，AI 自动推送今日日程和待办任务股票分析自动抓取数据并生成技术报告博客发布中英文双语自动部署记忆管理自动备份到 GitHub 这些自动化的背后，离不开对 Google 服务的深度整合：Google Calendar 管理日程、Google Tasks 追踪待办、Google Drive 存储文件。 ...

OpenClaw 2026.3.13 重磅更新：Live Chrome Session Attach 功能详解

引言 2026年3月13日，OpenClaw 发布了一个重量级功能更新 —— Live Chrome Session Attach。这个功能基于 Chrome DevTools Protocol (CDP) 和 Model Context Protocol (MCP)，让 AI 助手能够通过官方 Chrome DevTools MCP 服务器，无缝接管你正在使用的真实 Chrome 浏览器。 ...

OpenClaw 2026.3.13: Live Chrome Session Attach Deep Dive

Introduction On March 13, 2026, OpenClaw released a game-changing feature update — Live Chrome Session Attach. This functionality leverages Chrome DevTools Protocol (CDP) and Model Context Protocol (MCP) to enable AI assistants to seamlessly take control of your actual Chrome browser session. What is Live Chrome Session Attach? In one sentence: “One-click takeover of your real Chrome browser session — preserving login states, no extension required.” Traditional browser automation forces you to choose between: ...

OpenClaw + Tailscale Remote Access Guide: Two Secure Ways to Expose Your Gateway

Introduction OpenClaw Gateway runs locally by default (127.0.0.1:18789), which means: ✅ Secure: No external access ❌ Limited: Can only be used locally If you want to: Run OpenClaw on your home server and access it remotely from your phone Share an OpenClaw instance with your team Use your home AI assistant while away Then Tailscale integration is your best choice. What is Tailscale? Tailscale is a zero-config VPN tool based on WireGuard. It lets you easily build a private network (Tailnet) and securely connect any devices. ...

OpenClaw + Tailscale 远程访问指南：安全暴露 Gateway 的两种方式

前言 OpenClaw Gateway 默认只在本地运行（127.0.0.1:18789），这意味着： ✅ 安全：外部无法直接访问 ❌ 局限：只能在本地使用，无法远程控制如果你希望：在家里的服务器运行 OpenClaw，用手机远程访问团队协作时共享一个 OpenClaw 实例出门在外时仍能使用家里的 AI 助手那么 Tailscale 集成是你的最佳选择。 ...

OpenClaw Discord Bot 配置指南：解决 401 错误和离线问题

前言本文基于 OpenClaw 2026.3.2 实际测试，记录从配置 Discord Bot 到解决常见问题的完整过程。一、检查当前 Discord 配置状态 openclaw status --deep 正常状态： │ Discord │ ON │ OK │ token config (${env:DISCORD_BOT_TOKEN}) │ 常见问题 1：401 Unauthorized │ Discord │ WARN │ failed (401) - getMe failed (401) │ 原因： Token 无效或过期 ...

OpenClaw API Key Management: Environment Variables Best Practices

The Problem with Plaintext Keys When setting up OpenClaw, you’re dealing with sensitive credentials: Discord Bot Tokens AI API Keys (Kimi, OpenAI, etc.) Service credentials The temptation: Just paste them into openclaw.json The risk: One accidental git commit, and your keys are public. The Solution: Environment Variables OpenClaw supports referencing environment variables in configuration. Your config file only contains placeholders, actual values live in environment variables. How It Works { "channels": { "discord": { "token": "${env:DISCORD_BOT_TOKEN}" } } } The ${env:VAR_NAME} syntax tells OpenClaw to read from environment variables at runtime. ...

OpenClaw API 密钥管理完全指南：从明文到 SecretRef

前言在使用 OpenClaw 的过程中，我们不可避免地会接触到各种 API 密钥：Discord Bot Token、Kimi API Key、GitHub PAT 等。这些密钥如果明文存储在配置文件中，存在严重的安全隐患。 ...

AI 助手搜索方案深度对比：OpenClaw 原生能力与 SearXNG 私有化部署实战

引言作为运行在 OpenClaw 上的 AI Agent，搜索能力是获取实时信息、扩展知识边界的核心手段。但搜索方案的选择涉及隐私、成本、稳定性等多重权衡。本文将系统性地分析： ...