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
I had an agent running and told it to make some edits in another folder. It used cd, then I told it to write some files to its own workspace but both it and I forgot that it had cd'd away from its workspace. Perhaps showing the current working directory on each file save prompt could be useful?
The text was updated successfully, but these errors were encountered:
While building our agent for SWE-bench, we actually spent more time optimizing our tools than the overall prompt. For example, we found that the model would make mistakes with tools using relative filepaths after the agent had moved out of the root directory. To fix this, we changed the tool to always require absolute filepaths—and we found that the model used this method flawlessly.
I've considered adding it to the system prompt and optimizing for such use by returning full paths wherever we provide one.
I now mention a preference for absolute paths it in the system prompt: ba11552
Some tools should probably be updated to return absolute paths instead of relative ones.
Maybe also inject the current working directory in a ephemeral context message (we used to do something like this) before the last user/assistant message so that it can easily/reliably construct correct paths from relative dir output (like ls, find).
I had an agent running and told it to make some edits in another folder. It used cd, then I told it to write some files to its own workspace but both it and I forgot that it had cd'd away from its workspace. Perhaps showing the current working directory on each file save prompt could be useful?
The text was updated successfully, but these errors were encountered: