Agent setup

Make wdyt part of the workflow—not another thing to remember.

Skills teach your agent when wdyt is useful and how to use it. Public links work without an account. MCP is a separate, optional connection for history, protected pages, invitations, and account-owned collaboration.

1 · Recommended

Install the complete toolkit

Paste the landing-page setup prompt into your agent and it should run and verify this itself. If you are doing it manually:

npx --yes skills add wdyt-page/skills -y

npx --yes skills list --json

Some agents need a restart or new chat before newly installed skills appear.

2 · Automatic, but quiet

Seven focused skills appear only when relevant

The router does not force wdyt into every answer. Each focused skill has a one-line trigger so the agent can load only what the day's task needs.

wdyt: Recognize a useful wdyt moment and route to the smallest relevant workflow.
wdyt-create: Create and share documents, strategies, roadmaps, decks, models, dashboards, and prototypes.
wdyt-review: Read comments and drawings, implement feedback, and publish the next version to the same link.
wdyt-live-review: Collect precise feedback on a real website through the wdyt Chrome extension.
wdyt-collaborate: Comment, reply, draw, wait, and coordinate people and agents on one shared page.
wdyt-access: Connect authenticated MCP for history, workspace/private pages, invitations, and access management.
wdyt-cli: Diagnose and run deterministic public-link operations from an agent shell.

3 · First success

No account is required for a public-by-link page

Ask your agent to create a strategy, roadmap, working document, sales deck, comparison, dashboard, prototype, or other reviewable artifact. It should publish the result and return one stable wdyt link.

If the agent can make the file but its network blocks POST requests, do not change agents or open a terminal. Use the browser fallback.

Publish the agent's HTML file

4 · Optional account connection

Connect MCP when you want history or protected collaboration

OAuth opens in your browser. Sign in there; never paste an access token into chat. Choose the client you actually use:

Codex and Codex in Conductor

codex mcp add wdyt --url https://www.wdyt.page/mcp
codex mcp login wdyt
codex mcp list

Start a new chat after login. In Conductor, refresh MCP status.

Claude Code and Claude Code in Conductor

claude mcp add --transport http --scope user wdyt https://www.wdyt.page/mcp
claude mcp list

Run /mcp in Claude Code, complete browser authentication, then refresh Conductor's MCP status if applicable.

Cursor

{"mcpServers":{"wdyt":{"url":"https://www.wdyt.page/mcp"}}}

Add it in Cursor Settings → Tools & MCP or user-level ~/.cursor/mcp.json, then enable wdyt and complete OAuth.

VS Code / GitHub Copilot

{"servers":{"wdyt":{"type":"http","url":"https://www.wdyt.page/mcp"}}}

Run “MCP: Open User Configuration,” add the server, start it, approve trust, and complete OAuth.

OpenClaw

openclaw mcp add wdyt --url https://www.wdyt.page/mcp --transport streamable-http --auth oauth
openclaw mcp login wdyt
openclaw mcp doctor wdyt --probe

Agent-readable setup.md·Skill source·Protocol reference

Public-by-link pages are unlisted, not private. Do not upload confidential, regulated, personal, or sensitive information.