[docs] AgentBase OpenClaw — pair only after Active, enter Bot Token at deploy — VI + EN - #41
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
/startwith no mention of instance state. If the OpenClaw instance is stillCreating, 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
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)
VI —
ai-stack/agent-base/agent-runtime/openclaw/: lay-bot-token-va-pairing, trien-khai-openclaw-1-click, openclaw-1-click, gioi-han-va-luu-yEN —
ai-stack/agent-base/agent-runtime/openclaw/: get-bot-token-and-pairing, deploy-and-manage-openclaw, openclaw-1-click, limitations-and-notesVerified
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