#windows
1 messages · Page 1 of 1 (latest)
Do you mean âguide for Windowsâ for OpenClaw?
Start here: https://docs.openclaw.ai/start/faq
If youâre troubleshooting an install, please paste:
openclaw --version- how you installed it
- the exact command/error youâre seeing
Small claws note: use pnpm for source installs, not Bun.
If you mean GOG Galaxy on Windows:
- Go to https://www.gog.com/galaxy
- Click Download GOG Galaxy
- Run the downloaded
.exe - Sign in with your GOG account
- Use Owned games / Store to install games
If you meant an OpenClaw Windows install guide instead, say that and paste your openclaw --version if you already have it installed.
Do you mean an OpenClaw skill for GOG/Windows?
If so, skills are installed through ClawHub / OpenClaw, not through GOG Galaxy. For a âread docs / answer questionsâ style skill, start here: https://docs.openclaw.ai/
Tell me what you want the skill to do, and I can point you at the right setup path.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Yep, thatâs the gog Google Workspace CLI skill.
On Windows you need two pieces:
- Install the
gogbinary:
- Download
gogcli_<version>_windows_amd64.zipfrom https://github.com/openclaw/gogcli/releases - Extract
gog.exe - Put that folder on your Windows
PATH - Check it works with
gog --version
- Install the OpenClaw skill:
openclaw skills install jx76-gog
Then set up Google OAuth:
gog auth credentials C:\path\to\client_secret.json
gog auth add you@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
gog auth list
Skill page: https://clawhub.ai/jx-76/jx76-gog
OpenClaw skills docs: https://docs.openclaw.ai/tools/skills
If anything fails, paste openclaw --version, gog --version, and the exact error.
which windows path?
Use any normal folder you control, then add that folder to Windows Path.
Simple option:
C:\Tools\gog\
Put gog.exe there, so the full file is:
C:\Tools\gog\gog.exe
Then add the folder, not the exe, to Path:
C:\Tools\gog
Windows steps: Start menu â search Environment Variables â Edit environment variables for your account â select Path â Edit â New â paste C:\Tools\gog â OK. Open a new PowerShell and run:
gog --version
C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64
That path is fine if it contains gog.exe:
C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64\gog.exe
For a quick test, open PowerShell and run:
& "C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64\gog.exe" --version
For permanent use, Iâd move that folder out of Downloads, for example:
C:\Tools\gog
Then add C:\Tools\gog to your Windows Path. Downloads works, but itâs easy to delete or move by accident.
"C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64\gog.exe"
Good, thatâs the executable path.
In PowerShell, run it like this:
& "C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64\gog.exe" --version
The & matters in PowerShell when the path is quoted.
If that prints a version, add this folder to Windows Path:
C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64
After reopening PowerShell, this should work from anywhere:
gog --version
what is windoiws path
Windows Path is a list of folders Windows searches when you type a command.
Example: if gog.exe is in:
C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64\gog.exe
Then add this folder to Path:
C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64
After that, you can type:
gog --version
instead of typing the full long path every time.
How to add it: Start menu â type environment variables â Edit environment variables for your account â select Path â Edit â New â paste the folder path â OK â reopen PowerShell.
gog : Die Benennung "gog" wurde nicht als Name eines Cmdlet, einer Funktion, einer Skriptdatei oder eines ausfĂŒhrbaren Programms erkannt. ĂberprĂŒfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt
ist (sofern enthalten), und wiederholen Sie den Vorgang.
In Zeile:1 Zeichen:1
- gog --version
-
+ CategoryInfo : ObjectNotFound: (gog:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\racki>
That means Windows canât find gog.exe from Path yet. First test the exact file directly:
& "C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64\gog.exe" --version
If that works, add the folder to Path for this PowerShell window:
$env:Path += ";C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64"
gog --version
If that works too, add it permanently with the Environment Variables UI and then close/reopen PowerShell.
Also check the file really exists:
Test-Path "C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64\gog.exe"
It should print True.
it says true and version if i do gog --version there is error
Good, the exe works. The only problem is Path.
Run this in the same PowerShell window:
$env:Path += ";C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64"
gog --version
If that works, make it permanent:
[Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path", "User") + ";C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64", "User")
Then close all PowerShell windows, open a new one, and run:
gog --version
If it still errors after reopening, paste this output:
$env:Path -split ";" | Select-String "gogcli"
Nice. Next steps:
openclaw skills install jx76-gog
Then Google auth:
gog auth credentials C:\path\to\client_secret.json
gog auth add you@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
gog auth list
If this fixed the install part, please right-click the solution message â Apps â â Mark Solution so Answer Overflow indexes it for the next Windows user.
Next is Google OAuth setup.
- Install the OpenClaw skill:
openclaw skills install jx76-gog
-
Create/download a Google OAuth Desktop app client JSON from Google Cloud.
-
Point
gogat that file:
gog auth credentials C:\path\to\client_secret.json
- Add your Google account:
gog auth add your-email@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
- Check it:
gog auth list
gog gmail search "newer_than:7d" --max 5
If you donât have the client_secret.json yet, thatâs the next thing to create in Google Cloud.
gog auth credentials C:\path\to\client_secret.json
â[38;2;239;68;68mopen C:\path\to\client_secret.json: Das System kann den angegebenen Pfad nicht finden.â[0m
C:\path\to\client_secret.json was just a placeholder. You need to use the real file path of the OAuth JSON you downloaded from Google Cloud.
If itâs in Downloads, it may look like:
gog auth credentials "C:\Users\racki\Downloads\client_secret_123456.apps.googleusercontent.com.json"
To find it, run:
Get-ChildItem "$env:USERPROFILE\Downloads" -Filter "client_secret*.json"
If that shows a file, copy its full path and use it with gog auth credentials "...".
If it shows nothing, you still need to create/download the OAuth Desktop app client JSON in Google Cloud first.
nothing happens Get-ChildItem "$env:USERPROFILE\Downloads" -Filter "client_secret*.json" with this
That means there is no client_secret*.json file in Downloads yet.
You need to create/download it first:
- Open Google Cloud Console: https://console.cloud.google.com/apis/credentials
- Create/select a project
- Configure OAuth consent screen if Google asks
- Click Create credentials â OAuth client ID
- Application type: Desktop app
- Download the JSON file
- Put it in Downloads
Then run again:
Get-ChildItem "$env:USERPROFILE\Downloads" -Filter "client_secret*.json"
When it shows a file, use its real path:
gog auth credentials "C:\Users\racki\Downloads\client_secret_....json"
Donât paste the JSON contents here; just the filename/path if you need help.
have it there
Good. Now get the exact filename:
Get-ChildItem "$env:USERPROFILE\Downloads" -Filter "*.json" | Select-Object FullName
Then run gog auth credentials with the exact FullName, for example:
gog auth credentials "C:\Users\racki\Downloads\client_secret_123456.apps.googleusercontent.com.json"
After that:
gog auth add your-email@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
Use your real Gmail address in that last command.
Fehler 403: access_denied
403: access_denied usually means Google blocked the OAuth app, not that gog is broken.
Check this in Google Cloud:
- Go to https://console.cloud.google.com/auth/audience
- If the app is in Testing, add your Gmail address as a Test user
- Go to OAuth clients and make sure the client type is Desktop app
- Make sure you downloaded the JSON from that exact Desktop app client
- Try again:
gog auth add your-email@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
If it still fails, paste the full 403 text from the browser page, but donât paste your client secret JSON.
connected what next
Nice. Now verify the account and test one read-only command:
gog auth list
gog gmail search "newer_than:7d" --max 5
If Gmail works, test the other services you enabled:
gog calendar events --today
gog drive search "" --max 5
gog contacts list --max 5
Then install/confirm the OpenClaw skill if you havenât already:
openclaw skills install jx76-gog
After that, restart/new OpenClaw session so the skill is picked up.
â[38;2;239;68;68mGmail API is not enabled for this OAuth project.
Enable it at: https://console.developers.google.com/apis/api/gmail.googleapis.com/overview
Then retry the command. If you enabled it on a different OAuth client, re-authenticate with: gog auth add <account> --services gmailâ[0m
That one is direct: enable the Gmail API in the same Google Cloud project that owns your OAuth client.
Open this link and click Enable:
https://console.developers.google.com/apis/api/gmail.googleapis.com/overview
Then wait ~1 minute and re-run:
gog auth add your-email@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
Then test:
gog gmail search "newer_than:7d" --max 5
Youâll likely need to enable the other APIs too if you use them:
- Calendar API
- Google Drive API
- Google Sheets API
- Google Docs API
- People API / Contacts API
Enable them in the same project.
now it shows me mails
Great, Gmail is working.
Next, install/confirm the OpenClaw skill and start a fresh OpenClaw session:
openclaw skills install jx76-gog
Then test from OpenClaw by asking something like:
Search my Gmail for messages from the last 7 days using gog.
If you want Calendar/Drive/Sheets/Docs too, enable those APIs in the same Google Cloud project and re-run auth with the services you want:
gog auth add your-email@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
Also, please right-click the solution message â Apps â â Mark Solution so this Windows setup gets indexed for the next person.
PS C:\WINDOWS\system32> openclaw skills install jx76-gog
|
o
OpenClaw 2026.5.18 (50a2481) â If it works, it's automation; if it breaks, it's a "learning opportunity."
Skill already exists at C:\Users\racki.openclaw\workspace\skills\jx76-gog. Re-run with force/update.
Assertion failed: !(handle->flags & UV_HANDLE_CLOSING), file src\win\async.c, line 76
The important line is:
Skill already exists at C:\Users\racki\.openclaw\workspace\skills\jx76-gog
So the skill is already installed. The Assertion failed ... UV_HANDLE_CLOSING looks like a Windows CLI crash after it printed the result.
Next:
- Close that PowerShell window
- Open a normal PowerShell, not admin/System32 if possible
- Start a new OpenClaw session so it reloads skills
- Ask OpenClaw something like:
Use gog to search my Gmail for messages from the last 7 days.
If you actually need to update the skill later, use:
openclaw skills update jx76-gog
If that assertion keeps happening, file it as a bug with your version/output here: https://github.com/openclaw/openclaw/issues
with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe" -Command 'Get-Command gog -ErrorAction SilentlyContinu⊠(agent)
Tool input
{
"command": ""C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe" -Command 'Get-Command gog -ErrorAction SilentlyContinue | Format-List *'",
"cwd": "C:\Users\racki\.openclaw\workspace"
}
Tool output
{
"status": "failed",
"exitCode": 1,
"durationMs": 658
}
That means the OpenClaw agent process still canât see gog on its Path, even though your interactive PowerShell can.
Most likely fix: restart OpenClaw after changing Path.
Do this:
- Fully stop/restart OpenClaw / the gateway / the app
- Open a fresh OpenClaw session
- Ask it to run/check:
Get-Command gog
If it still fails, add the gog folder to the System Path, not just your user Path:
C:\Users\racki\Downloads\gogcli_0.17.0_windows_amd64
Then restart OpenClaw again. A full Windows reboot also works if the service is holding old environment variables.
Your gog install/auth is fine; this is just OpenClaw not inheriting the updated Windows Path yet.
where do i put Get-Command gog in powershell? or telegram?
Use PowerShell to test your own Windows setup:
Get-Command gog
But the failing output you pasted came from the OpenClaw agent, so after restarting OpenClaw you can also ask your agent in Telegram something like:
Run Get-Command gog and tell me the result.
So:
- PowerShell = checks if Windows can find
gog - Telegram/OpenClaw = checks if the agent/gateway can find
gog
Since PowerShell already worked for you, the important one now is: restart OpenClaw, then ask the Telegram agent to check Get-Command gog.
Get-Command gog
CommandType Name Version Source
Application gog.exe 0.0.0.0 C:\Users\racki\Downloads\gogcli_0.17.0...
Perfect. PowerShell can find gog.
Now restart OpenClaw/the gateway so the agent gets the updated Path. Then in Telegram ask:
Run Get-Command gog and tell me the result.
If Telegram still says it canât find gog, move gog.exe to a stable folder like:
C:\Tools\gog\gog.exe
Add this folder to Path:
C:\Tools\gog
and reboot Windows once. Services sometimes keep the old environment until a full restart.
what should i type telegram
In Telegram, type this exactly:
Run Get-Command gog and tell me the result.
If that works, then type:
Use gog to search my Gmail for messages from the last 7 days.
If the first one fails, restart OpenClaw/the gateway and try it again.
its not replying
If Telegram is not replying at all, check the Telegram connection first, not gog.
In PowerShell, run:
openclaw logs --follow
Then send a message to your Telegram bot. If you see pairing required or a pairing code, approve it:
openclaw pairing list telegram
openclaw pairing approve telegram <CODE>
Also try sending /start to the bot in Telegram.
If logs show nothing when you message Telegram, restart the gateway/app:
openclaw gateway restart
it works thank you