simplexcalc

9 Commits 2 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	cbcae80260	HTTP API: register, list and remove webhooks, kept across restarts (closes #6 ) check / check (push) Successful in 1m2s Details POST, GET and DELETE under /api/v1/chats/{id}/webhooks, for the chats that GET /api/v1/chats lists. The webhooks are kept in $DATA_DIR/webhooks.json, mode 0600, which each change replaces whole through a temporary file in the same directory and a rename. bot.Run reads the file before it starts the chat client: absent means none, and a file that cannot be read aborts startup. Reading a JSON request body moved into decodeBody, which the messages endpoint now shares. Nothing is posted to a webhook yet. Model: opus-5-5	2026-09-29 06:08:04 +00:00
clawbot	f53b666119	HTTP API: a chat's recent messages, and sending a message (closes #5 ) check / check (push) Successful in 1m5s Details `GET /api/v1/chats/{id}/messages?count=N` returns a chat's recent messages, oldest first (`count` 1 to 100, default 20), and `POST` to the same path sends a text message and returns it once the chat client has taken it. Both answer `404` for any id the chats list does not show, looked up in the same contact list. The message record is defined once, for the webhooks to reuse. Disclosures: items are read five at a time, because one item can be many times its text and 100 at once could pass the 16 MiB read limit; text too long gets `413`, a contact who deleted the chat `409` (unverified for one still connecting); a query the server cannot read gets its own `400`. Model: opus-5-5	2026-09-29 07:33:36 +02:00
clawbot	f10d820ed4	HTTP API: server, credential and the list of chats (closes #4 ) check / check (push) Successful in 1m13s Details The bot now serves an HTTP API on `PORT` (default 8080) beside the chat client, whose WebSocket stays on 127.0.0.1 inside the container. Every request needs `Authorization: Bearer` with the credential from the file named by `API_TOKEN_FILE`, compared in constant time; with no credential configured every request is refused, `OPTIONS *` included. `GET /api/v1/chats` lists the bot's chats. Responses carry the security headers from the repository policies; bodies, requests and the server are time- and size-bounded. The chat client stops only after the API has finished its requests. Disclosures: `contact_deleted` is an extra field; 404 and 405 answer in JSON; requests net/http cannot parse are refused by net/http without the security headers; three gosec findings are suppressed as false positives. Model: opus-5-5	2026-09-29 04:55:49 +02:00

Author

SHA1

Message

Date

clawbot

cbcae80260

HTTP API: register, list and remove webhooks, kept across restarts (closes #6 )

check / check (push) Successful in 1m2s

Details

POST, GET and DELETE under /api/v1/chats/{id}/webhooks, for the chats
that GET /api/v1/chats lists. The webhooks are kept in
$DATA_DIR/webhooks.json, mode 0600, which each change replaces whole
through a temporary file in the same directory and a rename. bot.Run
reads the file before it starts the chat client: absent means none, and
a file that cannot be read aborts startup. Reading a JSON request body
moved into decodeBody, which the messages endpoint now shares. Nothing
is posted to a webhook yet.

Model: opus-5-5

2026-09-29 06:08:04 +00:00

clawbot

f53b666119

HTTP API: a chat's recent messages, and sending a message (closes #5 )

check / check (push) Successful in 1m5s

Details

`GET /api/v1/chats/{id}/messages?count=N` returns a chat's recent messages, oldest first (`count` 1 to 100, default 20), and `POST` to the same path sends a text message and returns it once the chat client has taken it. Both answer `404` for any id the chats list does not show, looked up in the same contact list. The message record is defined once, for the webhooks to reuse.

Disclosures: items are read five at a time, because one item can be many times its text and 100 at once could pass the 16 MiB read limit; text too long gets `413`, a contact who deleted the chat `409` (unverified for one still connecting); a query the server cannot read gets its own `400`.

Model: opus-5-5

2026-09-29 07:33:36 +02:00

clawbot

f10d820ed4

HTTP API: server, credential and the list of chats (closes #4 )

check / check (push) Successful in 1m13s

Details

The bot now serves an HTTP API on `PORT` (default 8080) beside the chat client, whose WebSocket stays on 127.0.0.1 inside the container. Every request needs `Authorization: Bearer` with the credential from the file named by `API_TOKEN_FILE`, compared in constant time; with no credential configured every request is refused, `OPTIONS *` included. `GET /api/v1/chats` lists the bot's chats. Responses carry the security headers from the repository policies; bodies, requests and the server are time- and size-bounded. The chat client stops only after the API has finished its requests.

Disclosures: `contact_deleted` is an extra field; 404 and 405 answer in JSON; requests net/http cannot parse are refused by net/http without the security headers; three gosec findings are suppressed as false positives.

Model: opus-5-5

2026-09-29 04:55:49 +02:00