tbenandClaude Opus 5.5
380d3ebb2f
Bots get list_hooks, pause_hook and delete_hook, which act directly since they only take away. A new hook, or a new name, brief or filter, or switching a paused one back on, goes through propose_hook: it stores a hook_proposals row and puts a [hook-proposal:ID] card in the reply, which the user it was proposed to confirms or rejects. The card is read from what Confirm saves, with the bot's reason labelled as its own; confirming checks everything again and saves through the Hooks modal's helpers. A new hook's URL is shown on the card once, to the user only, never in the outcome the bot is told. What calls a hook, its computers and its signing are never proposed. Only chat replies propose, and a hook call's own run gets no hook tools, so a caller's payload can't reach them. Co-Authored-By: Claude Opus 5.5 <[email protected]>
29 lines
880 B
TypeScript
29 lines
880 B
TypeScript
import BunSQLite from "@moduletrace/bun-sqlite";
|
|
import { AppData } from "@/src/data/app-data";
|
|
import AppError from "@/src/utils/app-error";
|
|
|
|
type Params = {
|
|
user_id: number | string;
|
|
bot_id: number | string;
|
|
bot_name?: string | null;
|
|
};
|
|
|
|
/**
|
|
* Throws when the user's hooks for this bot are at
|
|
* `AppData.BotHookMaxPerBot`.
|
|
*/
|
|
export default async function assertHookRoom({ user_id, bot_id, bot_name }: Params) {
|
|
const count = Number(
|
|
(
|
|
await BunSQLite.sql<{ n: number }>({
|
|
sql: `SELECT COUNT(*) AS n FROM bot_hooks WHERE bot_id = ? AND user_id = ?`,
|
|
values: [bot_id, user_id],
|
|
})
|
|
).payload?.[0]?.n || 0,
|
|
);
|
|
|
|
if (count >= AppData.BotHookMaxPerBot) {
|
|
throw new AppError(`${bot_name || "This bot"} already has ${AppData.BotHookMaxPerBot} hooks. Delete one first.`);
|
|
}
|
|
}
|