From 43e5734833a40399e6f791e8027e3f517b3b0fbb Mon Sep 17 00:00:00 2001
From: luccast <2213102+luccast@users.noreply.github.com>
Date: Mon, 2 Feb 2026 13:49:22 -0500
Subject: [PATCH] docs: update README to clarify gateway token retrieval
 process

- Simplified instructions for obtaining the gateway token, emphasizing automatic detection from the configuration file.
- Added manual retrieval options and explicit token setting commands for user convenience.
---
 README.md | 15 ++++++---------
 1 file changed, 6 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index b1249e7..cf74ea0 100644
--- a/README.md
+++ b/README.md
@@ -144,23 +144,20 @@ Requires OpenClaw gateway running on the same machine.
 
 ### Gateway Token
 
-Find your token in the openclaw config file:
+The CLI auto-detects your token from `~/.openclaw/openclaw.json` (at `gateway.auth.token`). No manual config needed for local setups.
 
-```bash
-# Look for gateway.auth.token
-cat ~/.openclaw/openclaw.json | rg "gateway\.auth\.token"
-```
-
-Or with jq:
+To find your token manually:
 
 ```bash
 jq '.gateway.auth.token' ~/.openclaw/openclaw.json
 ```
 
-Or copy it directly:
+Or set it explicitly:
 
 ```bash
-export CLAWDBOT_API_TOKEN=$(python3 -c "import json,os; print(json.load(open(os.path.expanduser('~/.openclaw/openclaw.json')))['gateway']['auth']['token'])")
+crabwalk -t your-token
+# or
+export CLAWDBOT_API_TOKEN=your-token
 ```
 
 ## Stack