helloparthshah commited on
Commit
8b86bcd
·
1 Parent(s): 084b549

prompt update

Browse files
Files changed (2) hide show
  1. main.py +1 -1
  2. src/models/system5.prompt +1 -0
main.py CHANGED
@@ -180,7 +180,7 @@ no_auth = args.no_auth
180
 
181
  with gr.Blocks(title="HASHIRU AI", css=css, fill_width=True, fill_height=True) as demo:
182
  model_manager = GeminiManager(
183
- gemini_model="gemini-2.5-flash-preview-04-17", modes=[mode for mode in Mode])
184
 
185
  def update_model(modeIndexes: List[int]):
186
  modes = [Mode(i+1) for i in modeIndexes]
 
180
 
181
  with gr.Blocks(title="HASHIRU AI", css=css, fill_width=True, fill_height=True) as demo:
182
  model_manager = GeminiManager(
183
+ gemini_model="gemini-2.0-flash", modes=[mode for mode in Mode])
184
 
185
  def update_model(modeIndexes: List[int]):
186
  modes = [Mode(i+1) for i in modeIndexes]
src/models/system5.prompt CHANGED
@@ -18,6 +18,7 @@ Your role involves the following steps:
18
  1. **Tool Creation (`ToolCreator`):** Before creating any new tool, you **must** first inspect existing toolsets. Use the `ListFiles` tool to check `src/tools/default_tools` and `src/tools/user_tools`, then `ReadFile` to understand schema on how to create a new tool.
19
  * Once you understand the schema, invoke `ToolCreator` to build a new one. New tools must be production-ready:
20
  * Use existing packages and libraries where possible ( you can use any python3 compatible library).
 
21
  * Implement full functionality (no stubs or placeholders).
22
  * Include robust input validation and error handling.
23
  * Provide clear logging or helpful runtime messages for debugging and monitoring.
 
18
  1. **Tool Creation (`ToolCreator`):** Before creating any new tool, you **must** first inspect existing toolsets. Use the `ListFiles` tool to check `src/tools/default_tools` and `src/tools/user_tools`, then `ReadFile` to understand schema on how to create a new tool.
19
  * Once you understand the schema, invoke `ToolCreator` to build a new one. New tools must be production-ready:
20
  * Use existing packages and libraries where possible ( you can use any python3 compatible library).
21
+ * Tools are defined as classes and all dependencies should be added to the `dependencies` list to automatically install them.
22
  * Implement full functionality (no stubs or placeholders).
23
  * Include robust input validation and error handling.
24
  * Provide clear logging or helpful runtime messages for debugging and monitoring.