What you need
An official account or WeCom service agent the platform can manage; a computer with Codex / WorkBuddy installed, or the web console; an MCP developer key generated in the personal centre.
Guide · Agent Twin
Configure your agent with Codex / WorkBuddy
Turn scattered company decks, product material, courses, FAQs and service flows into one maintainable service role you can test inside WeChat. The web console suits item-by-item checking; an AI host suits bulk clean-up and cross-module iteration.
Prepare material and a developer key
Complete the modular configuration
Test for real inside WeChat
Before You Start
Start with a manageable entry point and real material
The goal is not a very long prompt. It is splitting service positioning, factual knowledge, FAQ, risk boundaries and assets into maintainable modules. Decide which official account or WeCom service agent you are configuring, then create a folder for its material.
What material to include
Company or personal introduction, products and services, pricing policy, service flow, FAQ, cases, sample phrasing and prohibited topics. Never put passwords, personal data or internal secrets into public assets or the knowledge base.
Create a folder for this account first
Create one folder for this account, ideally named after it. Keep everything for it here so material from different accounts never mixes.
XXX-account-twin/ 00-role-and-goals.md 01-introduction/ 02-products-and-services/ 03-pricing-and-policy/ 04-service-flow/ 05-faq/ 06-cases-and-samples/ 07-prohibited-and-risk/ 08-media/
Install & Enter
Pick one way of working
All three share the same platform configuration of record: an AI host (Codex or WorkBuddy, good for organising material, generating plans and iterating) calls the platform through authorised capabilities; the web console opens the real configuration pages directly.
Install the Agent Designer
- Go to Expert · Skills · Connectors on the left and choose Skills.
- Search for wanxiangdashi in the top right and confirm.
- Under SkillHub find Agent Designer (xcharagent design) and click the plus to install.
- That is all — no separate connector configuration is needed.
Hand the public install note to Codex
Once Codex finishes installing it should hold xagent 与 xagent-files two local stdio MCP services. The first connects platform tools and dynamic Skills; the second performs authorised operations on workspace, asset and resource files.
Read and strictly follow https://x.wanxiangdashi.com/mcp/install/codex. Install the XAgent plugin and the xagent and xagent-files MCP services for this Codex. If a developer key is needed, remind me to generate one in the wanxiangdashi personal centre under Settings → Developer keys. After installing, run doctor to confirm both MCP services are available, and remind me to restart Codex or start a new task.
- Requires Node.js 18+, the Codex CLI and tar.
- Codex Desktop on macOS needs the GUI process to receive an MCP token.
- Never paste the token into public chats, screenshots or material files.
Or configure it without installing a plugin
Go to the Operations Centre, find the target under My WeChat Official Accounts or My WeCom → Digital staff, open the account console or WeCom service desk, then open Agent configuration.
- Assistant templates, the wizard, basic info, persona, service rules, memory, knowledge base, FAQ, edge cases, failure fallbacks, skill apps, hot words and the operation log are all available.
- Best for item-by-item edits and visual checks; bulk material clean-up and cross-module plans are better handed to Codex / WorkBuddy.
Platform key setup (once)
- Open x.wanxiangdashi.comand go to the personal centre; under Profile → Developer keys, generate and copy a key.
- In a new WorkBuddy conversation, click the plus, add Agent Designer, type "please configure my key", then paste the key and send.
- Then type "list the official accounts I created". If WorkBuddy lists the account you bound earlier, the connection is complete.
First Success
Seven steps to a first testable configuration
Choose the workspace
In Select workspace at the bottom of the WorkBuddy composer, choose the folder you just created. It becomes the single place you keep material.
Load the agent design Skill
Click the plus in the composer, or type a slash, to add /Agent Designer.
Read the currently available rules and version first; do not configure the platform from memory.
It lists the agents you can configure
Confirm which accounts or WeCom service agents you are entitled to manage. Do not create orphan agents for convenience, and do not assume a private key alone grants authority.
List the official accounts and WeCom service agents I may configure, grouped by account type, name and management relationship. Do not change any configuration yet.
Organise the material and find the gaps
Drop existing documents into the folder, or let the host interview you and list what is missing. Keep facts separate from design decisions.
Generate a modular plan first
On the first pass, only read material and produce a plan — write nothing to the platform.
Read ./XXX-account-twin. Do not write to the platform yet. Produce a modular configuration plan for the agent I select: basic info, persona, service rules, role memory, knowledge base, FAQ, edge cases, assets and hot words. Say which document each item comes from, which parts are facts, which are design decisions, which still need my confirmation, and leave unrelated configuration untouched.
After confirming, write module by module and re-read
Leave untouched fields alone. Deletions, template overwrites, major risk policy changes and bulk asset moves need separate confirmation.
I confirm this plan. Configure it module by module, keeping existing fields that are not involved each time. Deletions, template overwrites, major risk policy changes and bulk asset moves must be confirmed separately first. When done, re-read the affected modules and run a consistency check.
Test for real at the WeChat entry point
The entry point only counts as accepted when a real message sent there gets a reply. Saving a page is not the same as a verified conversation.
Extend Carefully
Add these operating capabilities when needed
Configure skill apps
Under Agent configuration → Skill apps, attach real apps or link assets. At runtime the agent may only recommend cards that exist; it must never invent URLs or product fields.
Create VIP / XApp products
Products, VIP, resource objects, publishing and licensing are operations and commerce configuration, not the job of xcharagent_design the code. A product draft is not a live product either.
First-follow and re-follow greetings
In the account console under Message automation → Event messages, create templates and rules for subscribe and resubscribe separately; confirm the template before enabling automation.
Custom voice
Basic voices are chosen under Agent configuration → Basic info. Cloned voices are configured by platform super-administrators today; ordinary tenants cannot train one in a normal form.
Test & Improve
Let real questions drive small iterations
Each round, submit only the real question and the correction you expect, and let the host locate the module to change. Never overwrite the whole configuration with one huge prompt.
Test dimensionCheck at leastIf it fails, look here first
Identity and knowledgeWhether "who are you", the core business, pricing and process are accurate.Basic info, knowledge base, FAQ.
Service boundariesWhether uncertainty, refunds, complaints and high-risk questions acknowledge the boundary or hand over.Service rules, edge cases, failure fallback.
Service actionsWhether recommendations are real, restrained and in context.Skill apps, products, message strategy.
MultimodalityWhether voice, image and other message types match the role and quota policy.Basic info, assets, message flow.
Next: turn the service into a deliverable XApp
When you need forms, assessments, records, courses or paid delivery, build an XApp that can call the agent.
