Use LivePage in WorkBuddy on your phone
The cloud mode of the WorkBuddy phone app can now connect LivePage; for a daily push to WeChat see the cloud scheduled task guide. The WorkBuddy mini program still has no LivePage connector, and any connection you set up there is gone in the next session. None of the three routes below needs setup.
1. Nothing to set up: publish with one sentence
Send WorkBuddy this sentence together with your content:
Publish this as a WeChat link through the LivePage no-sign-in lane (space.24haowan.com, not the WorkBuddy library): call quick_publish at https://space.24haowan.com/mcp/quick, or POST https://space.24haowan.com/api/quick. Show me the preview first and share only after I confirm.


Pages published without signing in expire 7 days after sharing, open on at most 50 phones, and are limited to 3 per network per hour. To keep one, use route 2 or 3. Include the address so WorkBuddy does not confuse LivePage with its own library.
2. Bind code: set up once, then every page goes into your account


3 From then on, in any new session say "publish this to WeChat with LivePage", confirm the preview and say "share": the page is in your account with the same link and no day or reader limit.
A bind code can only add new pages to your account; it cannot see or change existing ones. Up to 30 pages per hour, valid for six months; if it leaks, revoke it on the same page.
3. Keep a page you already published

With the LivePage connector you can update the same link, collect forms and push on a schedule: on your computer see the illustrated desktop guide; for a cloud scheduled task built in the phone app (runs with your computer off) see the cloud guide.
For agent developers: serving agents that cannot sign in or keep settings
- Run a separate no-sign-in endpoint with only safe write tools (upload, review first, preview, share only after confirmation, revoke), with its own tool list. Ours are https://space.24haowan.com/mcp/quick (MCP) and https://space.24haowan.com/api/quick (HTTPS).
- Name that endpoint inside the 401 of the main endpoint: agents read error messages.
- Return a management credential and a keep link for each piece; signing in moves it into the account with the same link.
- Pass the bind code as a parameter, not a header. It can only add pages to one account, so it can live in the platform's memory. Count allowances per bind code, not per network address.
- Reject an unknown bind code loudly; never fall back to anonymous publishing.
curl -X POST https://space.24haowan.com/api/quick \
-H 'Content-Type: application/json' \
-d '{"title":"Weekly report","files":[{"path":"index.html","content":"<h1>Weekly report</h1>"}],"bind_code":"lpb-…"}'
# returns preview_url (show it to the user) and manage_url; after the user confirms:
curl -X POST https://space.24haowan.com/api/quick/<last segment of manage_url>/share
{ "mcpServers": { "livepage-quick": { "type": "http", "url": "https://space.24haowan.com/mcp/quick" } } }
The full guide for agents: /for-agents.md.