You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 2, 2025. It is now read-only.
- If the output of a function is empty, try the same function again with different arguments or try using a different function
97
+
- ALWAYS call a function, DO NOT answer the question directly, even if the query is not in English
98
+
- DO NOT call a function that you've used before with the same arguments
99
+
- DO NOT assume the structure of the codebase, or the existence of files or folders
100
+
- Call functions to find information that will help answer the user's query, until all relevant information has been found
101
+
- Only call functions.proc with path indices that are under the PATHS heading above
102
+
- If the output of a function is empty, try calling the function again with different arguments OR try calling a different function
103
+
- If functions.code or functions.path did not return any relevant information, call them again with a SIGNIFICANTLY different query. The terms in the new query should not overlap with terms in your old one
104
+
- Call functions.proc with paths that you have reason to believe might contain relevant information. Either because of the path name, or to expand on code that's already been returned by functions.code
105
+
- DO NOT pass more than 5 paths to functions.proc at a time
106
+
- In most cases call functions.code or functions.path functions before calling functions.none
107
+
- When you have enough information to answer the user call functions.none. DO NOT answer the user directly
108
+
- If the user is referring to information that is already in your history, call functions.none
98
109
- When calling functions.code or functions.path, your query should consist of keywords. E.g. if the user says 'What does contextmanager do?', your query should be 'contextmanager'. If the user says 'How is contextmanager used in app', your query should be 'contextmanager app'. If the user says 'What is in the src directory', your query should be 'src'
99
-
- In most cases respond with functions.code or functions.path functions before responding with functions.none
100
-
- If the user is referring to information that is already in your history, respond with functions.none
101
-
- Do not assume the structure of the codebase, or the existence of files or folders
102
-
- Do NOT respond with a function that you've used before with the same arguments
103
-
- When you have enough information to answer the user's query respond with functions.none
104
-
- Only refer to path aliases that are under the PATHS heading above
105
-
- Respond with functions to find information related to the query, until all relevant information has been found
106
-
- Only call functions.none with paths that contain code that might help answer the user's query, or which answer it directly
107
-
- If you have already called functions.code or functions.path but they did not return any relevant information, try again with a substantively different query. The terms in your new query should not overlap with terms in previous queries
108
-
- Use functions.proc on paths that you suspect might contain relevant information, or to expand on code that's already been returned by a code search. Do not pass more than 10 paths to functions.proc at a time
110
+
- Only call functions.none with paths that might help answer the user's query
109
111
- If after attempting to gather information you are still unsure how to answer the query, respond with the functions.none function
110
112
- If the query is a greeting, or not a question or an instruction use functions.none
111
-
- Always use a function, even if the query is not in English
112
-
- Always respond with a function call. Do NOT answer the question directly"#);
113
+
- ALWAYS call a function. DO NOT answer the question directly"#);
0 commit comments