Executor-Tyrant-Framework commited on
Commit
a44acfc
·
verified ·
1 Parent(s): 85dba6c

Update app.py

Browse files
Files changed (1) hide show
  1. app.py +5 -4
app.py CHANGED
@@ -124,10 +124,11 @@ System Stats: {stats.get('total_files', 0)} files, {stats.get('conversations', 0
124
  Output Format: Use [TOOL: tool_name(arg="value")] for tools.
125
 
126
  ## CRITICAL PROTOCOLS:
127
- 1. **RECURSIVE MEMORY FIRST**: If the user asks about past context (e.g., "the new UI"), you MUST use `search_conversations` BEFORE you answer. Do not ask the user for context you already have.
128
- 2. **THINK OUT LOUD**: When writing code, output the full code block in the chat BEFORE calling `write_file`. This ensures a backup exists in memory if the write fails.
129
- 3. **CHECK BEFORE WRITE**: Before writing code, use `read_file` or `list_files` to ensure you aren't overwriting good code with bad.
130
- 4. **NO SILENCE**: If you perform an action, report the result.
 
131
  """
132
 
133
  def parse_tool_calls(text: str) -> list:
 
124
  Output Format: Use [TOOL: tool_name(arg="value")] for tools.
125
 
126
  ## CRITICAL PROTOCOLS:
127
+ 1. **DIRECT ACTION**: Do not say what you are *going* to do. JUST DO IT. Do not say "I will now search for the file." and stop. Output the `[TOOL: ...]` command immediately in the same response.
128
+ 2. **RECURSIVE MEMORY FIRST**: If the user asks about past context (e.g., "the new UI"), you MUST use `search_conversations` BEFORE you answer.
129
+ 3. **THINK OUT LOUD**: When writing code, output the full code block in the chat BEFORE calling `write_file`.
130
+ 4. **CHECK BEFORE WRITE**: Before writing code, use `read_file` or `list_files` to ensure you aren't overwriting good code with bad.
131
+ 5. **NO SILENCE**: If you perform an action, report the result.
132
  """
133
 
134
  def parse_tool_calls(text: str) -> list: