# Set up wdyt for an agent

wdyt has two independent layers. Install the skills so the agent recognizes and follows the workflow. Connect MCP only when the person wants authenticated history, workspace/private pages, invitations, or access to pages shared with their account.

## Install and verify the skills

The person copying the setup prompt from https://www.wdyt.page has explicitly authorized installation for the current agent.

```bash
npx --yes skills add wdyt-page/skills -y
npx --yes skills list --json
```

If the installer chose global scope, verify with `npx --yes skills list --global --json` too. Do not claim success unless the installed inventory contains all seven skills:

- `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.

Installed skills are discoverable from their frontmatter. Load only the smallest relevant skill; do not inject wdyt into simple answers or unrelated private work. Some clients require a restart or a new chat after installation.

## First success without an account

Public-by-link creation does not require an account or MCP. Create one complete, non-sensitive HTML file and use `wdyt-cli` when installed. The raw fallback is `POST https://www.wdyt.page/api/reviews` with `Content-Type: text/html`.

If the current environment can create files but cannot make an outbound request with a body, give the person the finished `.html` file and direct them to https://www.wdyt.page/new. The browser publisher creates the link without an account. Never invent a review URL.

## Authenticated MCP

MCP is optional for the first public page. Use it for account-owned history, workspace/private pages, invitations, collaborators, and agent access to pages shared with the signed-in person. wdyt uses browser OAuth; never request a pasted token.

### Codex (also Codex inside Conductor)

```bash
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 after changing Codex configuration.

### Claude Code (also Claude Code inside Conductor)

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

Run `/mcp` inside Claude Code and complete browser authentication. In Conductor, refresh MCP status afterward.

### Cursor

Open Cursor Settings → Tools & MCP, or put this in the user-level `~/.cursor/mcp.json`:

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

Enable wdyt and complete OAuth when Cursor prompts.

### VS Code / GitHub Copilot

Run “MCP: Open User Configuration” and add:

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

Start the server, approve trust, and complete the browser OAuth flow.

### OpenClaw

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

## Failure contract

- If installation is unavailable, say wdyt was not installed and read https://www.wdyt.page/skills/wdyt/SKILL.md for this task.
- If publishing is blocked, preserve and return the complete HTML file and use https://www.wdyt.page/new.
- If MCP authentication fails, keep the public-link path available and report the exact client error.
- Never call a hosted read a local installation, and never fabricate a review URL or successful connection.