Skip to content

[docs] AgentBase OpenClaw — pair only after Active, enter Bot Token at deploy — VI + EN - #41

Merged
greennode-vdb merged 2 commits into
mainfrom
huyenttn3
Aug 18, 2026
Merged

[docs] AgentBase OpenClaw — pair only after Active, enter Bot Token at deploy — VI + EN#41
greennode-vdb merged 2 commits into
mainfrom
huyenttn3

Conversation

@greennode-vdb

Copy link
Copy Markdown
Contributor

What

Two OpenClaw setup traps are now documented in the guides, VI + EN.

Why

1. Pairing before the instance is Active
Part 4 (Zalo pairing) told users to send /start with no mention of instance state. If the OpenClaw instance is still Creating, the bot returns no pairing code at all, and that message is not reprocessed once the instance goes Active — so the user is stuck with no code and no explanation.

2. Bot Token left empty at deploy
The deploy form does not require a Bot Token, and the docs described it as "Optional. Can be configured later at Settings → Config". In practice, adding the token after the instance exists means asking the agent inside OpenClaw to update the channel configuration itself — hard to do and easy to get wrong.

Changes

  • Part 4 opens with a new step "Confirm the OpenClaw instance is Active" (old steps renumbered to 2 and 3), with a warning about the no-code-returned behaviour
  • The Result section gained a bullet for that exact symptom: bot returns nothing → check instance status and channel Bot Token
  • Same Active warning added to the deploy success step and to FAQ [docs] [vMonitor] Export vLB access logs to vDB Kafka/OpenSearch — VI + EN #4
  • A lighter Active check added to the Telegram pairing step — same mechanism, framed as a check rather than restating the Zalo-specific symptom
  • Channel Configuration row changed to "Not enforced by the form, but fill it in here", plus a warning explaining the cost of skipping it
  • Both token-copy steps (Telegram and Zalo) now say where the token goes: the deploy form's Bot Token field
  • The pairing guide opens with "get your bot token before you deploy"
  • Both limitations pages gained a Channel connection notes table holding the two gotchas side by side

Drive-by fix

The EN deploy guide had mojibake from an earlier encoding accident — vCPU × RAM, 2×4, 🟢 Active, Settings → Config, Starting → Active — all repaired to ×, 🟢, .

Files (8, all pre-existing — no SUMMARY.md changes)

VIai-stack/agent-base/agent-runtime/openclaw/: lay-bot-token-va-pairing, trien-khai-openclaw-1-click, openclaw-1-click, gioi-han-va-luu-y
ENai-stack/agent-base/agent-runtime/openclaw/: get-bot-token-and-pairing, deploy-and-manage-openclaw, openclaw-1-click, limitations-and-notes

Verified

Hint tag balance, code-fence parity, all relative links and image paths resolve, CRLF preserved, and VI/EN heading counts + hint sequences match exactly on all 4 page pairs.

🤖 Generated with Claude Code

Hana-Hasa and others added 2 commits August 18, 2026 15:02
…t deploy — VI + EN

Two setup traps users hit:

1. Sending /start on Zalo while the instance is still Creating returns no
   pairing code, and the message is not reprocessed once it goes Active.
   Part 4 now starts with a "confirm instance is Active" step (old steps
   renumbered to 2 and 3), and the result section covers the no-code symptom.
   Same warning added to the deploy success step and FAQ.

2. Bot Token is optional on the deploy form, but adding it after the instance
   exists means asking the agent to update the channel config itself. Channel
   Configuration now recommends entering it there, both token-copy steps point
   at that field, and the pairing guide opens with "get the token first".

Also adds a Channel connection notes table to the limitations pages, and
repairs pre-existing mojibake in the EN deploy guide (vCPU × RAM, 🟢,
Settings → Config).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@greennode-vdb
greennode-vdb merged commit 8eab8a1 into main Aug 18, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants