XDG_CONFIG_HOME/pub/config.json when XDG_CONFIG_HOME is set
~/.config/pub/config.json by default
PUB_HOME must be an absolute path. It also roots Pub data, state, runtime sockets, and workspaces.
For OpenClaw bridge mode, set an explicit workspace before pub config --auto, for example OPENCLAW_WORKSPACE=/absolute/path/to/workspace.
Pub is built for adaptive interfaces — agents generate real-time UIs tailored to the user's task.
Pubs are private by default.
Reuse existing pubs for regular or repeated tasks. Use pub list to check if a relevant pub already exists, then pub update <slug> instead of creating a new one. Each user is limited to 10 pubs.
Title and description come from OG meta tags in the HTML. Always include og:title and og:description in your <head>. The server extracts them automatically — there are no CLI flags for title/description.
html
<head>
<meta property="og:title" content="My Pub Title">
<meta property="og:description" content="A short description of what this pub does">
</head>
When updating a pub's content, always keep the OG tags accurate.
Live is browser-initiated: the user opens the pub page; owner live mode connects automatically once the daemon is online.
Start the agent daemon:
bash
pub start --agent-name "<agent-name>"
Notes:
Bridge mode comes from saved config (pub config --auto or pub config --set bridge.mode=...).
Supported bridge modes: openclaw, claude-code, claude-sdk, claude-channel, and openclaw-like.
Enable verbose live daemon logging with pub config --set bridge.verbose=true when startup or bridge delivery is hard to diagnose.
Standalone binary installs fall back to claude-code when the Claude Agent SDK package is not locally importable.
bridge.mode=claude-sdk requires @anthropic-ai/claude-agent-sdk to be available in the local JS environment.
bridge.mode=claude-channel expects a running relay socket. Start it with pub channel-server and override the socket path with claude-channel.socketPath or PUB_CHANNEL_SOCKET_PATH when needed.
bridge.mode=openclaw-like uses named command profiles from openclawLike.profiles and openclawLike.defaultProfile; profile args are passed before the final prompt.
Canvas command-manifest agent executors require a local agent runtime:
provider: "claude-code" needs claude-code.path or CLAUDE_CODE_PATH;
provider: "openclaw" needs openclaw.path and openclaw.sessionId or matching env vars.
On success, pub start prints the daemon log path and current runtime status.
On failure, inspect the reported log path first; if logs are sparse, enable bridge.verbose=true and retry.
Check runtime status:
bash
pub status
Reply in chat:
Bridge-owned chat is the live-session contract. Reply with normal assistant text; the bridge forwards that text to the chat channel.
For longer live-session work, regularly send concise, specific progress updates through chat while continuing:
bash
pub write "Working on it"
Use channel-specific pub write for canvas and other non-chat outputs:
