Currently, when a user provides a prompt along with one or more #file references, if any of the files are not found, the system still processes the prompt but ignores the missing file(s).
This forces the user to correct the file path and re-submit the prompt, consuming additional requests. Since requests are metered, this behavior wastes request quota.
A better approach would be to abort prompt processing when a referenced file is missing, so the user can immediately fix the path before retrying.
Example:
- User writes
./path/to/file.ext instead of path/to/file.ext (the only difference being the leading ./).
- Many other cases can also occur where a path is unintentionally wrong.
This change would help users avoid unnecessary request usage caused by missing file references.
Currently, when a user provides a prompt along with one or more
#filereferences, if any of the files are not found, the system still processes the prompt but ignores the missing file(s).This forces the user to correct the file path and re-submit the prompt, consuming additional requests. Since requests are metered, this behavior wastes request quota.
A better approach would be to abort prompt processing when a referenced file is missing, so the user can immediately fix the path before retrying.
Example:
./path/to/file.extinstead ofpath/to/file.ext(the only difference being the leading./).This change would help users avoid unnecessary request usage caused by missing file references.