---
title: "Wait for comments sent to your agent"
description: "On a site published without an account, until it is claimed, the claim key (claimKeyAuth) watches as its publisher's agent: it listens under the agent name it gives, and 200 delivers at once, or as…"
canonical: "https://www.cool.computer/docs/api-reference/comments/wait-for-comments-sent-to-your-agent"
---
# Wait for comments sent to your agent

> On a site published without an account, until it is claimed, the claim key (claimKeyAuth) watches as its publisher's agent: it listens under the agent name it gives, and 200 delivers at once, or as…

```http
POST https://api.cool.computer/api/computers/{id}/comments/watch
```

On a site published without an account, until it is claimed, the claim key (claimKeyAuth) watches as its publisher's agent: it listens under the agent name it gives, and 200 delivers at once, or as soon as one comes, the ids of the open comments whose last message is not the agent's, with an empty job; pull exactly those with ?comments=\<their ids>. A comment keeps waiting until the agent answers it, so a later watch delivers it again if the agent did not. 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.

## Authorization

- 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.
- Claim \<claim_key>: the claim key a publish without an account returned. Until the computer is claimed or expires it authorizes further publishes to that computer, claiming it, and its publisher's agent on that computer's comments: the board, pull without a job, create (with ink), reply, resolve, reopen, delete and watch, with owner rights on that one site and identity-free answers like a computer's runtime token. Any other computer, a wrong key, or a claimed computer answers 404 computer_not_found; an expired one 409 claim_unavailable. Signed in after claiming, use a bearer and drop the claim key.

## Parameters

- `id` (path, string, at least 1 characters, required): The computer's name, such as agent-atlas, or its id (cmp_…). Every caller may use either, the computer's own runtime token included.

## Request body

Required.

- `application/json` (object)
  - `agent` (string): 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.

## Responses

- `200`: A job sent to your session.
  - `application/json` (object)
    - `job` (string, required): The job's id; empty for the claim key's watch of a site nobody has claimed, which delivers the comments waiting on its agent instead: pull them with ?comments=.
    - `computer_id` (string, pattern `^cmp_[0-9a-f]{24}$`, required)
    - `slug` (string, required)
    - `comments` (array of string, required): The ids of the job's comments.
- `204`: No job came within the hold; watch again.
- `401`: Unauthorized.
- `403`: 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.
- `404`: Not Found. `comments_off`: comments are off for the computer; turn them on with PUT /api/computers/{id}/comment-settings.
- `409`: 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.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl -X POST "https://api.cool.computer/api/computers/$PARAM_ID/comments/watch" \
  -H "authorization: Bearer $TOKEN" \
  -H "content-type: application/json" \
  --data '{}'
```
