LivePage

Use LivePage in WorkBuddy on your phone

In cloud sessions of WorkBuddy on your phone and in the WeChat mini program, LivePage is not in the connector list, any connection you set up is wiped when a new session starts, and there is no sign-in page to scan. None of the three routes below needs a connection: the first needs nothing at all, the second takes one bind code and then every session publishes straight into your account, and the third brings pages you already published back into your account.

1. Nothing to prepare: the no-sign-in lane

Send WorkBuddy this sentence together with your content. It uploads the page, gives you a preview link first, and only creates the WeChat link after you say "share".

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.

You can also add the skill "Publish & Share to WeChat" under Skills and then simply say "publish this to WeChat with LivePage". Pages published without signing in: 3 per network per hour, expire 7 days after sharing, at most 50 phones can open them, and the same link cannot be updated. To keep one, use route 3.

Tip: the Chinese name of LivePage is also the name of WorkBuddy's own library pages. Say "LivePage" or include the address so the two are not mixed up.

2. Get a bind code and keep it in memory: every new session publishes into your account

  1. Open https://space.24haowan.com/app/bind in WeChat, sign in and tap "Generate bind code".
  2. Tap the button that copies the memory sentence, open "Me › Memory" in the WorkBuddy mini program and send it there.
  3. From then on, in any new session say "publish this to WeChat with LivePage". WorkBuddy publishes with your bind code; after you check the preview and say "share", the page is in your account: no day or reader limit, the same link, and you can edit it and see who read it in the LivePage console.

A bind code can only add new pages to your account. It cannot read your existing pages or data, so it is safe to keep in memory. Each bind code allows up to 30 pages per hour and is valid for six months; if it leaks, revoke it on the same page and generate a new one.

3. Bring a page you already published into your account

Publishing without signing in returns a management link, which is also the keep link. Open it in WeChat, sign in and tap "Sign in and keep": the page moves into your account, its limits are lifted, and readers keep the same link.

Which route to use

For agent developers: serving agents that cannot sign in and cannot keep settings

Phone and cloud agents share three traits: every session is a fresh sandbox, so connection settings written there are gone next time; there is no browser for OAuth; and only the platform's own connectors, skills and memory survive between sessions. This is the pattern we use so LivePage works there with no setup. Feel free to copy it.

  1. Run a separate no-sign-in endpoint with only safe write tools: upload, review first, preview, share only after the user confirms, and revoke. It does not share a tool list with the signed-in endpoint. Ours are https://space.24haowan.com/mcp/quick (MCP) and https://space.24haowan.com/api/quick (for agents that can only send HTTPS requests).
  2. Name the no-sign-in endpoint inside the 401 of the main endpoint. Agents read error messages: if it only says "authorization required", they can only tell the user to create a token, edit settings and restart.
  3. Return a management credential and a keep link for each piece: the credential is the key to that one piece, and the keep link lets the user sign in and move it into their own account with the same link.
  4. Pass the bind code as a parameter, not a request header. Its only power is adding new pages to one account, so it can be pasted into a chat and kept in the platform's memory. Count allowances per bind code, not per network address: cloud sandboxes share their outbound addresses.
  5. Reject an unknown bind code loudly and never fall back to anonymous publishing: a user who thinks a page is in their account and finds the link gone days later is the worst outcome.

Calling it directly:

curl -X POST https://space.24haowan.com/api/quick \
  -H 'Content-Type: application/json' \
  -d '{"title":"Weekly report","files":[{"path":"index.html","content":"
Weekly report
"}],"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//share

Where MCP settings can be written (they last only for that session):

{ "mcpServers": { "livepage-quick": { "type": "http", "url": "https://space.24haowan.com/mcp/quick" } } }

The full guide written for agents: /for-agents.md. Connecting from Claude: /help/claude.