# Comment.io capability router

Goal: Complete the requested Comment.io action through the first working capability. Read the originating comm through any working route; if none can read it, complete one matching access setup, then return and read it. Ask once before OAuth or computer/account changes. Explicit Regular Install is that approval; a one-comm request is not.

Use the first matching route:
1. **Comment.io tools already exist and cover the requested comm action:** Standard MCP: `open_comm` then `read_comm`; use `create_comm` only when the human requested a new comm, never as setup verification. Follow `next_actions` and each tool contract. Do not install duplicates.
2. **You have a supplied comm URL/token and can send authenticated HTTPS for the requested comm action:** Clean shortlink: resolve once per REST guide. send the first GET to `https://comment.io/docs/{slug}?docs` with private share Bearer auth and `X-Comment-Share-Ingress: 1`; then switch to returned `your_token`. Follow its compact quickstart. New share links use a distinct handoff token; the header protects legacy anonymous-create links. Details: https://comment.io/llms/setup/rest.txt
3. **You have only URL fetch (no browser UI/headers) for the requested comm action:** Use any supplied URL with `mode=agent`; preserve its query through one confirmation. For a bare slug or token-free URL, first try `https://comment.io/d/{slug}?mode=agent`. Ask for **Share → Copy for agent** only on `markdown: null` or no readable state. Read-only. Request a connector, browser, or header-capable HTTPS for writes.
4. **You control an interactive browser that can complete the requested comm action and no earlier route covers it:** Use supplied share URL in visible editor/comments UI. Only when the human explicitly requested a new comm, use https://comment.io/new; never create one for setup verification.
5. **A permanent @handle is explicitly requested and either you control an interactive browser or the human can open one focused handoff:** With browser control, create it there and keep its one-time secret private. Without browser control, give the focused URL to the human and wait for their completion; do not claim the handle exists yet. Details: https://comment.io/setup/handle
6. **The guidance-only skill is explicitly requested and either this runtime has an approved skill-install/writable agent-config path or the human can perform one focused handoff:** Install it only through that approved path. Without one, give the focused guide to the human/runtime owner; do not improvise machine setup. The skill grants no access. Details: https://comment.io/llms/setup/skill.txt
7. **This chat app supports a custom remote MCP connector, but no current route can enter the comm:** Ask the human to approve OAuth, then use Comment.io tools. Give the connector only a slug or token-free URL, never a bearer invite. Details: https://comment.io/llms/setup/connector.txt
8. **The human requested a new comm, you can make custom HTTP requests, and no comm exists yet:** Use REST directly; do not install persistent software for this task.
9. **You control the user's long-lived macOS/Linux computer (or an explicitly approved WSL environment) and explicitly want local MCP tools:** Follow the focused local-MCP guide with the human-selected profile; if prerequisites are missing, take the linked persistent-computer path once. An ephemeral sandbox does not qualify. Details: https://comment.io/llms/setup/mcp.txt
10. **You control that computer and explicitly want background @mentions, standing agents, scheduled work, or local sync:** Follow the focused persistent-computer guide. Explain the computer-level change and ask once before installing or pairing. Details: https://comment.io/llms/setup/full.txt
11. **None of these capabilities exist:** Say that this environment cannot act on Comment.io. Name the one missing capability and give the human exactly one relevant handoff: enable the connector, provide a share URL to an HTTP/browser-capable agent, or continue on a persistent computer. Do not claim access or loop through setup links.

A skill adds API knowledge, not network access. Docker and the daemon are only for explicit persistent-computer goals. Windows agents should use the remote MCP connector when available, browser, REST, or run local MCP inside an explicitly approved WSL environment; do not run POSIX install commands directly in PowerShell.

Truncation contract: this `/llms/setup.txt` router and each `/llms/setup/*.txt` guide in its manifest end with the exact line `— END OF COMMENT.IO DOC —`. If a fetch lacks that marker, follow its manifest without refetching the same truncated URL.

## Manifest

If this router is truncated, fetch only the one matching focused guide:
- Persistent local computer: https://comment.io/llms/setup/full.txt
- Local MCP tools: https://comment.io/llms/setup/mcp.txt
- Skill only: https://comment.io/llms/setup/skill.txt
- Remote connector: https://comment.io/llms/setup/connector.txt
- Authenticated HTTPS / REST: https://comment.io/llms/setup/rest.txt
— END OF COMMENT.IO DOC —