From e9f0a02f1fa4e1abfb00ed625596be3161f1fe41 Mon Sep 17 00:00:00 2001 From: Willem Jiang Date: Mon, 27 Oct 2025 07:21:41 +0800 Subject: [PATCH] docs: add tool-specific interrupts configuration to conf.yaml.example (#661) This allows users to configure which tools should trigger interrupts before execution, useful for reviewing sensitive operations. --- conf.yaml.example | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/conf.yaml.example b/conf.yaml.example index 543311e..23939cd 100644 --- a/conf.yaml.example +++ b/conf.yaml.example @@ -42,6 +42,23 @@ BASIC_MODEL: # OTHER SETTINGS: + +# Tool-specific interrupts configuration (Issue #572) +# Allows interrupting execution before specific tools are called. +# Useful for reviewing sensitive operations like database queries or API calls. +# Note: This can be overridden per-request via the API. +# TOOL_INTERRUPTS: +# # List of tool names to interrupt before execution +# # Example: interrupt before database tools or sensitive API calls +# interrupt_before: +# - "db_tool" # Database operations +# - "db_read_tool" # Database reads +# - "db_write_tool" # Database writes +# - "payment_api" # Payment-related API calls +# - "admin_api" # Administrative API calls +# # When interrupt is triggered, user will be prompted to approve/reject +# # Approved keywords: "approved", "approve", "yes", "proceed", "continue", "ok", "okay", "accepted", "accept" + # Search engine configuration (Only supports Tavily currently) # SEARCH_ENGINE: # engine: tavily