Let bots manage their hooks, with the user confirming what widens them

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]>

src/harness/tools/bot/grab-bot-tools.ts

@@ -1,5 +1,6 @@
 import type { BUN_SQLITE_COBBLE_COMPUTERS } from "@/db/types/db";
 import type { HarnessTool } from "../../types";
+import grabBotHookTools from "./hooks/grab-bot-hook-tools";
 import grabBotTaskTools from "./tasks/grab-bot-task-tools";
 import createScheduleTool from "./create-schedule-tool";
 import deleteScheduleTool from "./delete-schedule-tool";
@@ -42,12 +43,22 @@ type Params = {
      * set from one.
      */
     scopes?: StorageScope[];
+    /**
+     * The run is a hook call, so it gets no hook tools.
+     */
+    hooked?: boolean;
+    /**
+     * In a chat reply: called with each hook proposal's ref, so the reply
+     * carries its card. Without it the bot can't propose hooks.
+     */
+    onPropose?: (params: { ref: string }) => void;
 };
 
 /**
  * The tools a bot works with on every run, bound to that bot and where it
- * works: its memory and instructions, its schedules, and in a workspace
- * with several computers switching the default one.
+ * works: its memory and instructions, its schedules, its hooks
+ * (`grabBotHookTools`), and in a workspace with several computers
+ * switching the default one.
  */
 export default async function grabBotTools({
     user_id,
@@ -58,6 +69,8 @@ export default async function grabBotTools({
     is_coordinator,
     admin_workspace_ids,
     scopes = [],
+    hooked,
+    onPropose,
 }: Params): Promise<HarnessTool[]> {
     return [
         setPictureTool({ user_id, bot_id, scopes, is_coordinator }),
@@ -67,6 +80,7 @@ export default async function grabBotTools({
         listSchedulesTool({ user_id, bot_id }),
         updateScheduleTool({ user_id, bot_id }),
         deleteScheduleTool({ user_id, bot_id }),
+        ...grabBotHookTools({ user_id, bot_id, session_id, workspace_id, computers, hooked, onPropose }),
         ...(session_id ? [reactToMessageTool({ bot_id, user_id, session_id })] : []),
         ...(workspace_id && computers.length > 1
             ? [setWorkspaceComputerTool({ user_id, workspace_id, computers })]