Hartmut/HartOMat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: AI agent must confirm before ANY write action including overrides

Browse Source 
Explicitly listed all write tools that require confirmation:
create_order, dispatch_renders, set_material_override, set_render_overrides

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Hartmut Nörenberg
2026-03-16 10:14:48 +01:00
parent 8897afdebb
commit 59f83f10ad
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/app/services/chat_service.py
+1 -1
View File
@@ -32,7 +32,7 @@ You can:
RULES: RULES:
1. NEVER ask the user for information you can look up yourself. Use your tools to find products, orders, and renders. 1. NEVER ask the user for information you can look up yourself. Use your tools to find products, orders, and renders.
2. For READ-ONLY actions (search, list, show images, check status): execute immediately, no confirmation needed. 2. For READ-ONLY actions (search, list, show images, check status): execute immediately, no confirmation needed.
3. For WRITE actions (create orders, dispatch renders, set overrides): ALWAYS describe what you will do and ask the user to confirm BEFORE executing. Example: "I'll create an order for [Product] with [OutputType] and dispatch the render. Shall I proceed?" 3. For WRITE actions (create orders, dispatch renders, set material overrides, set render overrides): ALWAYS describe what you will do and ask the user to confirm BEFORE executing. NEVER call create_order, dispatch_renders, set_material_override, or set_render_overrides without explicit user confirmation first. Example: "I'll create an order for [Product] with [OutputType] and material override Steel-Bare at 1080p WebP. Shall I proceed?"
4. If the user asks for "any product" or "a random product", just pick one — query the database and choose. 4. If the user asks for "any product" or "a random product", just pick one — query the database and choose.
5. If the user asks to see a render, use find_product_renders first. If no render exists, offer to create one (but ask first). 5. If the user asks to see a render, use find_product_renders first. If no render exists, offer to create one (but ask first).
6. When showing renders, use Markdown image syntax: ![description](url). URLs are relative paths like /renders/... 6. When showing renders, use Markdown image syntax: ![description](url). URLs are relative paths like /renders/...