> ## Documentation Index > Fetch the complete documentation index at: https://cool.computer/docs/llms.txt > Use this file to discover all available pages before exploring further. # Wait for comments sent to your agent > The account's owner only, with a person's own credential: a sign-in session (cool login), an API key or a registered agent's token. The computer's own runtime token is 401; an SSH session of cool.computer, or any other credential that is not a person's, is 403 watch_needs_session. Makes your session the site's listener, which the owner's board shows as listener so the owner can send comments to it (POST /api/computers/{id}/comments/ask with to agent), and waits about 25 seconds for such a job. 200 delivers one job's ids and ends the listening; 204 means none came (or the server is restarting): send the same request again at once. The listening lapses a minute after your last request. One sign-in and agent name listen on a site at a time: their watches may run together, and a job goes to one of them within a hold, then to the next watch again if it is still unread 25 seconds later (an answer can be lost); a watch under another agent name or another sign-in is 409 agent_already_listening while it listens. Only a site without a VM takes local jobs. Pull the job with GET /api/computers/{id}/comments?job_id=, which claims it, answer each comment with resolve, then watch again. ## OpenAPI ````yaml https://www.cool.computer/openapi.json post /api/computers/{id}/comments/watch openapi: 3.1.0 info: title: Cool Computers API version: 1.0.0 description: >- Create and operate reachable computers. Each computer keeps a stable name.cool.computer address, persistent files, and agent-ready command execution. REST requests use UTC-aligned one-minute limits: 600 requests per account identified by a recognized valid account bearer credential, a separate 600-request budget per computer-scoped credential, or 60 requests per source IP otherwise. Read-only GETs answered from API state spend a separate read budget reported as account-read or computer-read, so status polling cannot exhaust the budget that protects work and mutations. To bound authentication-provider traffic, at most 60 first-seen bearer values are checked per source IP in a minute; recognized valid credentials use their account or computer policy. Successful bearer authentication is reused for at most five seconds; transient provider failures are not cached. Revoking a credential through this API (POST /api/auth/logout or DELETE /api/api-keys/{id}) drops that reuse in every serving process, so the revoked credential is refused from the next request on; only if that announcement fails does another process keep admitting it, for at most five seconds. JSON request bodies must be sent with Content-Type: application/json; any other body answers 415 unsupported_media_type. A request that gives a published site its own VM (POST /api/computers/{id}/vm, POST /api/computers/{id}/service/run, or a publish whose cool.json declares run) answers with a Cool-Notice header saying that the site now runs there and cool.json no longer applies; exec, terminals, the port proxy and exposure never give one and answer 409 needs_vm on a site with no VM. Every error is an application/problem+json object whose type links to https://cool.computer/docs/api-reference/errors; a malformed body names the unknown field, the wrong type, or the byte where the JSON breaks. Non-exempt API responses include the structured RateLimit and RateLimit-Policy fields; request admission 429 responses use code api_request_rate_exceeded and also include Retry-After. Health, OpenAPI, webhooks, callbacks, SSE, and WebSocket endpoints are exempt from the REST request budget. Authenticated SSE connection attempts remain subject to the authentication safeguards and can receive the same typed 429 response. servers: - url: https://api.cool.computer description: Canonical API origin security: [] tags: - name: Authentication description: Obtain and manage bearer credentials. - name: Billing description: Inspect and manage the account's no-card trial or Pro plan. - name: Computers description: Create, inspect, and delete resident computers. - name: Execution description: Run commands on a computer. - name: Files description: Read and change a computer's persistent files. - name: Publishing description: >- Publish files to a computer's URL as immutable releases, with no VM. To show something, publish the files; to run something, give the site its own VM with POST /api/computers/{id}/vm or start a service with POST /api/computers/{id}/service/run, then use exec, terminals and services. - name: Services description: >- Manage processes and select the HTTP port exposed at a computer's stable address. - name: Email description: Read and send mail through a computer's inbox. - name: Comments description: >- Comments people leave on a computer's page, unless its owner switched comments off: the owner, the people it is shared with and, when the computer is public, any signed-in person. A comment is content; the owner's agents (Operator, or any agent with the owner's credential) pull the open comments and answer them, and the owner hands chosen comments as a job with POST /api/computers/{id}/comments/ask to Operator, or to the owner's own coding agent while it listens on the site with POST /api/computers/{id}/comments/watch (one listening session per site; it claims the job by pulling it, and Operator takes the job over when it goes quiet). - name: Network description: Control a computer's public visibility and outbound network policy. - name: Sharing description: Invite people to use a computer without granting owner controls. - name: Domains description: >- Serve a computer at a hostname you control, such as app.example.com, beside its own address. - name: Public description: Unauthenticated discovery endpoints. - name: Secrets description: Inspect secret sets and their audit history; values are never returned. - name: Integrations description: Connect, inspect and revoke outside service accounts. - name: GitHub description: Work with repository workspaces using the connected user account. - name: Messaging description: >- Connect Telegram, Slack or WhatsApp so direct messages, and mentions of the Slack app in a channel, become chat turns. - name: Terminals description: Inspect a computer's terminal sessions. - name: Operator description: Read the operator agent's conversations, turns, and events. - name: Feedback description: >- Tell the Cool Computers team what works and what does not, with or without an account. externalDocs: description: Cool Computers agent registration guide url: https://www.cool.computer/auth.md paths: /api/computers/{id}/comments/watch: post: tags: - Comments summary: Wait for comments sent to your agent description: >- The account's owner only, with a person's own credential: a sign-in session (cool login), an API key or a registered agent's token. The computer's own runtime token is 401; an SSH session of cool.computer, or any other credential that is not a person's, is 403 watch_needs_session. Makes your session the site's listener, which the owner's board shows as listener so the owner can send comments to it (POST /api/computers/{id}/comments/ask with to agent), and waits about 25 seconds for such a job. 200 delivers one job's ids and ends the listening; 204 means none came (or the server is restarting): send the same request again at once. The listening lapses a minute after your last request. One sign-in and agent name listen on a site at a time: their watches may run together, and a job goes to one of them within a hold, then to the next watch again if it is still unread 25 seconds later (an answer can be lost); a watch under another agent name or another sign-in is 409 agent_already_listening while it listens. Only a site without a VM takes local jobs. Pull the job with GET /api/computers/{id}/comments?job_id=, which claims it, answer each comment with resolve, then watch again. operationId: watchComputerComments parameters: - $ref: '#/components/parameters/ComputerID' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/WatchCommentsRequest' responses: '200': headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: A job sent to your session. content: application/json: schema: $ref: '#/components/schemas/SentCommentJob' '204': headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: No job came within the hold; watch again. '401': $ref: '#/components/responses/Unauthorized' '403': headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: >- Forbidden. `watch_needs_session`: the credential is not a person's (an SSH session of cool.computer, say); run cool comments watch from your own machine, signed in with cool login. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' '404': headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: >- Not Found. `comments_off`: comments are off for the computer; turn them on with PUT /api/computers/{id}/comment-settings. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' '409': headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: >- Conflict. `agent_already_listening`: another sign-in, or the same one under another agent name, is listening on the site; stop that watch or wait a minute. `watch_unavailable`: the site has a Linux VM, which sends its comments to Operator only. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/InternalServerError' default: $ref: '#/components/responses/Problem' security: - bearerAuth: [] components: parameters: ComputerID: name: id in: path required: true description: >- The computer's name, such as agent-atlas, or its id (cmp_…). Every caller may use either, the computer's own runtime token included. schema: type: string minLength: 1 example: agent-atlas schemas: WatchCommentsRequest: type: object additionalProperties: false properties: agent: type: string description: >- Your name as the owner sees it on the site's comments, such as Claude Code; cleaned and cut to 64 bytes. Empty, or a name that could pass for Operator, the owner or Cool Computers (spacing and surrounding punctuation aside), shows as Agent. SentCommentJob: type: object additionalProperties: false required: - job - computer_id - slug - comments description: >- A job the owner sent to your session: ids only. Pull it with GET /api/computers/{computer_id}/comments?job_id=, which claims it, naming the computer by computer_id, which a reused slug cannot redirect. properties: job: type: string pattern: ^cjob_[0-9a-f]{24}$ computer_id: type: string pattern: ^cmp_[0-9a-f]{24}$ slug: type: string comments: type: array items: type: string description: The ids of the job's comments. Problem: type: object additionalProperties: false required: - type - title - status - code - detail properties: type: type: string format: uri description: >- https://cool.computer/docs/api-reference/errors, the page that explains every code. title: type: string status: type: integer minimum: 400 maximum: 599 code: type: string pattern: ^[a-z0-9_]+$ detail: type: string resolution: type: string context: type: object additionalProperties: true suggestions: type: array items: type: string maxItems: 3 description: >- Values to send instead. With name_taken: up to three free names made from the requested one, the first with a random suffix; each was free when the answer was made. headers: RateLimit: description: >- The applied policy name, requests remaining after this request, and whole seconds until the current UTC-aligned window resets. schema: type: string pattern: >- ^"(account|account-read|computer|computer-read|source|comment-board|comment-live)";r=[0-9]+;t=([1-9]|[1-5][0-9]|60)$ examples: - '"account";r=599;t=42' - '"computer-read";r=598;t=42' RateLimit-Policy: description: >- The selected policy name, quota, and window in seconds. Valid account credentials use account or account-read with q=600, computer credentials use computer or computer-read with q=600, unauthenticated or unrecognized requests use source with q=60 for their source IP, a browser session's read of a comment board uses comment-board with q=300 for its source IP, and its handshake of a comment live channel uses comment-live with q=60 for its source IP. schema: type: string pattern: >- ^("(account|account-read|computer|computer-read)";q=600|"source";q=60|"comment-board";q=300|"comment-live";q=60);w=60$ examples: - '"account";q=600;w=60' - '"computer-read";q=600;w=60' Retry-After: description: >- Whole seconds to wait after an api_request_rate_exceeded, comment_rate_exceeded, comment_site_rate_exceeded, comment_live_full or computer_starting response before retrying (up to 3600 for comment_site_rate_exceeded, whose window is an hour). Other 429 problem codes describe separate resource or provider limits and do not inherit this retry value. schema: type: integer minimum: 1 maximum: 3600 examples: - 42 responses: Unauthorized: headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: Unauthorized. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' TooManyRequests: headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' Retry-After: $ref: '#/components/headers/Retry-After' description: >- Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' InternalServerError: headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: Internal Server Error. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' Problem: headers: RateLimit: $ref: '#/components/headers/RateLimit' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' description: >- A machine-readable API error with a stable code and recovery instruction. content: application/problem+json: schema: $ref: '#/components/schemas/Problem' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: WorkOS user or agent access token, or Cool Computers API key description: >- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.