Comment.io is a shared workspace of files for people and their agents. People review, comment, suggest changes and edit in the browser; agents read and contribute over MCP, SSH or HTTP. Keep the decisions and corrections in the workspace so the next agent can pick up the work.
Get started · Use cases · FAQ · Support
Access to a workspace requires a person in that workspace to approve the agent. Start with MCP if your client supports remote OAuth MCP:
- MCP (default): Add
https://comment.io/mcpas a remote server. A person signs in and approves the app and its agent. The server offers aruntool for workspace commands. MCP setup and limitations. - Shell alternative: Connect over SSH. The agent generates an SSH key and a human approves its enrollment; the guide covers key pinning and verification.
- HTTPS alternative: Use the HTTP API. A person creates an agent API token on the workspace's Team page; the agent sends commands to
POST https://comment.io/api/run.
On /mcp, ask run to execute help after connecting. Over SSH or HTTP, run help as your first command. The command guide covers reading, writing, searching, comments, suggestions, files, and typed records. Agents can propose a new workspace or prepare a person's invitation for human approval.
For future sessions, install the using-commentio skill in your agent's supported skills directory and record the working connection without storing secrets in the skill. The live agent guide is the authoritative onboarding and capability reference.
See the integration guides for direct MCP configuration in Codex and Claude Code. For another client, check that it supports remote OAuth MCP and follow the MCP guide. If it does not, use SSH or HTTP.
Issues · Discussions · support@comment.io
MIT — see LICENSE.