Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Feature]: Document gws migration guide for Gmail skill users [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#50026•Fetched 2026-04-08 01:00:09
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
AIdenB899AIdenB899
Participants
AIdenB899AIdenB899
Timeline (top)
cross-referenced ×1labeled ×1

Provide official migration documentation for users transitioning from gog (deprecated) to gws for Gmail integration.

Error Message

Users must reverse-engineer migration steps from gws docs and trial-and-error, leading to broken automations and lost productivity.

  • 2-4 hours of trial-and-error per user to figure out migration

Root Cause

Provide official migration documentation for users transitioning from gog (deprecated) to gws for Gmail integration.

Fix Action

Fixed

PR fix notes

PR #50130: docs(gmail): add gog to gws migration guide

Description (problem / solution / changelog)

Summary\n- add an official Gmail migration guide for users moving from gog to gws\n- link the guide from the existing Gmail Pub/Sub docs\n\n## Why\nUsers migrating Gmail integrations currently have to reverse-engineer installation, auth, and command differences between gog and gws. This adds a documented migration path.\n\nCloses #50026\n

Changed files

  • docs/automation/gmail-pubsub.md (modified, +3/-0)
  • docs/guides/gmail-migration-gog-to-gws.md (added, +172/-0)
RAW_BUFFERClick to expand / collapse

Summary

Provide official migration documentation for users transitioning from gog (deprecated) to gws for Gmail integration.

Problem to solve

Users with existing Gmail integrations using gog face challenges migrating to gws due to:

  1. No official migration guide in OpenClaw docs
  2. Breaking CLI syntax changes (positional args vs flags)
  3. Credential path/format differences
  4. Changed authentication flow
  5. Undocumented behavioral changes

Users must reverse-engineer migration steps from gws docs and trial-and-error, leading to broken automations and lost productivity.

Proposed solution

Add an official migration guide to OpenClaw docs covering:

  1. Pre-migration checklist: Document existing gog commands and workflows
  2. Installation: Remove gog, install gws via Homebrew
  3. Authentication: Fresh OAuth setup with gws (credentials not portable)
  4. Command translation: Map common gog patterns to gws equivalents
  5. Testing: Verify all automations work with gws
  6. Rollback: How to revert if needed

The guide should include:

  • Side-by-side command comparisons
  • Common gotchas and solutions
  • Validation steps to confirm successful migration
  • Links to gws documentation for advanced usage

Alternatives considered

  1. Rely on gws upstream docs: Insufficient - doesn't cover OpenClaw-specific integration patterns or migration path from gog
  2. Community wiki: Less discoverable, not versioned with releases, prone to becoming outdated
  3. Keep both tools: Increases maintenance burden and confuses users about which to use

Impact

Affected: All OpenClaw users with Gmail integrations using gog

Severity: Medium-high - Broken email automations impact business workflows

Frequency: One-time migration event, but affects every user who integrates Gmail

Consequence:

  • 2-4 hours of trial-and-error per user to figure out migration
  • Broken automations during transition
  • Support burden on maintainers answering migration questions
  • Users may delay migration or abandon Gmail integration entirely

Evidence/examples

I created a migration guide based on real-world migration experience:

File: /Users/aiden/clawd/docs/gws-migration-guide.md

Key findings during migration:

  • gog credentials at ~/.config/gog/ not compatible with gws ~/.config/gws/
  • OAuth flow requires complete re-authentication
  • Command syntax changes broke existing scripts (e.g., gog gmail list inbox → gws gmail +triage)

This guide could serve as the basis for official documentation.

Additional information

Related links:

Suggested location: docs/guides/gmail-migration-gog-to-gws.md

Timing: Would be helpful to include in next OpenClaw release notes as a migration resource.

extent analysis

Fix Plan

To migrate from gog to gws for Gmail integration, follow these steps:

  1. Pre-migration checklist:
    • Document existing gog commands and workflows.
    • Identify credential paths and formats.
  2. Installation:
    • Remove gog using the package manager.
    • Install gws via Homebrew: brew install gws.
  3. Authentication:
    • Set up fresh OAuth credentials with gws: gws auth --gmail.
    • Note: gog credentials are not portable to gws.
  4. Command translation:
    • Map common gog patterns to gws equivalents:
      • gog gmail list inbox → gws gmail +triage.
    • Update scripts and automations accordingly.
  5. Testing:
    • Verify all automations work with gws.
    • Test OAuth authentication and credential usage.
  6. Rollback:
    • If issues arise, revert to gog by reinstalling it and restoring previous credentials.

Example gws command usage:

# Authenticate with Gmail using OAuth
gws auth --gmail

# List inbox emails using the +triage flag
gws gmail +triage

Update scripts and automations to use the new gws command syntax.

Verification

To verify the fix, test the following:

  • Successful authentication with gws using OAuth credentials.
  • Correct functionality of updated scripts and automations.
  • Compatibility of gws with existing Gmail integration workflows.

Extra Tips

  • Refer to the gws documentation for advanced usage and troubleshooting: https://github.com/gen-mind/gws.
  • Update the OpenClaw Gmail skill documentation to reflect gws usage: skills/gog/.
  • Include the migration guide in the next OpenClaw release notes as a resource for users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#autograd error#tokenizer error#prompt formatting#chain error#conversation history

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING