Skip to main content
POST
Reopen computer comment

Authorizations

Authorization
string
header
required

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.

Path Parameters

id
string
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.

Minimum string length: 1
Example:

"agent-atlas"

commentID
string
required

Comment identifier returned by the comment board or the pull.

Minimum string length: 1
Example:

"comment_1a2b3c"

Body

application/json
version
integer
required

The version of the comment the owner saw.

Required range: x >= 1
text
string
required

The owner's answer, 1 to maxLength bytes.

Required string length: 1 - 1000
request
string

An id the client gives this answer, new for each answer, and sends again with the same answer and version when the answer was lost: an answer of yours with that request and the same text already in the thread returns the comment unchanged (200), although its version has moved since, so the answer is stored once, and other text under it is 400 invalid_comment: send new words with a new request. Leave it out to have the answer held to version alone.

Pattern: ^[0-9a-f]{24}$

Response

The reopened comment.

id
string
required
Example:

"comment_1a2b3c"

state
enum<string>
required

open waits for an agent to answer it, asked waits for the owner's answer, done is finished.

Available options:
open,
asked,
done
version
integer
required

Changes on every update; send the one you read when resolving.

Required range: x >= 1
release
integer
required

Release the computer served when the comment was left; 0 when it served none.

anchor
object
required

Where on the page a comment points. An element anchor names its element by selector, and may leave out rect: the page finds the element. An area anchor needs rect unless it carries ink; with ink its selector is the first mark's el, and it may leave out rect too, since the page finds each mark's element. The page shows an anchor's pin by its drawn marks, then by the element its selector finds exactly once, then by its stored rect; with none of them it shows no pin.

thread
object[]
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
fixed_in_release
integer

Release that fixed the comment, when a newer one was published.