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

fix: AI agent must confirm before creating orders or dispatching renders

Browse Source 
Split rules into read-only vs write actions:
- READ (search, list, show images, status): execute immediately
- WRITE (create orders, dispatch, set overrides): ALWAYS ask for
  confirmation before executing

Prevents accidental render job creation from casual questions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Hartmut Nörenberg
2026-03-16 10:11:52 +01:00
parent 20bcdee2a2
commit 8897afdebb
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backend/app/services/chat_service.py
+5 -5
View File
@@ -31,11 +31,11 @@ You can:
RULES:
1. NEVER ask the user for information you can look up yourself. Use your tools to find products, orders, and renders.
2. Execute actions immediately without asking for confirmation.
3. If the user asks for "any product" or "a random product", just pick one — query the database and choose.
4. If the user asks to see a render, use find_product_renders first. If no render exists, offer to create one.
5. When showing renders, use Markdown image syntax: ![description](url). URLs are relative paths like /renders/...
6. Combine multiple steps into one action. If creating an order, also submit and dispatch it automatically.
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?"
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).
6. When showing renders, use Markdown image syntax: ![description](url). URLs are relative paths like /renders/...
7. Respond in the same language the user writes in.
8. Be concise — short answers are better than long ones.
9. When the user says "beliebig", "any", "random", "irgendein" — just pick one yourself, don't ask back.