360 Secure SkillHub
360 安全技能中心

Gmail Gog Setup

该 Skill 提供为 Agent 邮箱接入 Gmail 的操作步骤：在 Google Cloud 创建桌面应用 OAuth 客户端并启用 Gmail API，安装 Gog CLI，存储 OAuth 凭据，手动完成账号授权，验证邮件检索与垃圾邮件检查，并列出常见认证故障与处理方式。

stefanferreira
stefanferreira
热度 46.57
最近更新 2026-05-11 17:42:59
分类：协作依赖：代码执行 / 联网浏览搜索 / 读写文件 / 第三方 API应用场景：API 集成 / 工作流 / 邮件起草

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add gmail-gog-setup
Metadata
name
gmail-gog-setup
description
Set up Gog CLI for Gmail access and authenticate agent mailboxes.
metadata
{"openclaw":{"emoji":"📧","requires":{"bins":["gog"]},"install":[]}}

Gmail + Gog Setup

Use this skill when you need to give an agent (e.g., Facet, competitions agent) access to a Gmail inbox via Gog CLI.

When to use

  • Creating a new agent mailbox (e.g., facet.ai.oc@gmail.com)
  • Setting up Gmail reading capability for an existing agent
  • Troubleshooting Gog auth failures
  • Adding new OAuth clients or test users

Prerequisites

1. Google Cloud OAuth client

  • Create a Desktop app OAuth client in Google Cloud Console
  • Enable Gmail API
  • Add target Gmail address as a test user in OAuth consent screen
  • Download the client JSON file

2. Gog installed

# Install Gog from latest release
cd /tmp
curl -L -o gogcli_0.12.0_linux_amd64.tar.gz https://github.com/steipete/gogcli/releases/download/v0.12.0/gogcli_0.12.0_linux_amd64.tar.gz
tar -xzf gogcli_0.12.0_linux_amd64.tar.gz
install -m 0755 gog /usr/local/bin/gog

Steps

1. Store OAuth credentials

gog auth credentials /path/to/client_secret_....json

2. Authenticate the Gmail account

export GOG_KEYRING_PASSWORD='your-keyring-password'
gog auth add agent@gmail.com --services gmail --manual
  • Open the provided auth URL in browser
  • Log in as the target Gmail account
  • Approve requested permissions
  • Copy the redirect URL (localhost) after Google redirects
  • Paste it into the waiting Gog prompt

3. Verify access

gog auth list
gog gmail messages search 'newer_than:7d' --account agent@gmail.com --json

4. Check spam

New senders often land in spam:

gog gmail messages search 'in:spam newer_than:7d' --account agent@gmail.com --json

Common issues

"No auth for gmail"

  • Verify test user is added in Google Cloud OAuth consent screen
  • Re-run auth with --force-consent if needed

"state mismatch"

The auth session restarted. Use the latest auth URL and callback.

"no TTY available for keyring file backend"

Set GOG_KEYRING_PASSWORD environment variable before running gog auth add.

Emails going to spam

  • Move from spam to inbox: gog gmail messages modify <msg_id> --remove SPAM --add INBOX
  • Consider training Gmail by marking as "Not spam"

Notes

  • Store OAuth client JSON in ~/.openclaw/credentials/google/
  • Keep GOG_KEYRING_PASSWORD in a secure environment variable or secret manager
  • For production, consider service account with domain-wide delegation instead of OAuth
  • Always check spam folder for important verification/API emails

References