Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: CodeAct repeatedly edits the wrong file #1890

Open
2 tasks done
rbren opened this issue May 18, 2024 · 2 comments
Open
2 tasks done

[Bug]: CodeAct repeatedly edits the wrong file #1890

rbren opened this issue May 18, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@rbren
Copy link
Collaborator

rbren commented May 18, 2024

Is there an existing issue for the same bug?

Describe the bug

I'm asking CodeAct to repeatedly switch between editing two related files. Often File A is open, then CodeAct sends an edit command intended for File B. This usually happens when I issue a new instruction.

It'd be neat to show/emphasize the currently open file in CodeAct's prompt.

Side note: maybe we should just stop making open a thing, and put filenames directly into the commands? The agent has to look back over previous commands to determine current state, instead of just having a deterministic instruction it can write.

Current Version

Main, as of `0ecba83e53c6f2abfb0fdbaf134842a0298234f6`

Installation and Configuration

docker run

Model and Agent

gpt-4-turbo, CodeAct

Reproduction Steps

repeatedly prompt codeact to edit different files

Logs, Errors, Screenshots, and Additional Context

Screenshot 2024-05-18 at 3 40 18 PM
@rbren rbren added the bug Something isn't working label May 18, 2024
@li-boxuan
Copy link
Collaborator

Side note: maybe we should just stop making open a thing, and put filenames directly into the commands?

I also had the same wonder when I saw SWE agent commands. Apparently LLM often forgets that it needs to open a file before edits it.

@xingyaoww
Copy link
Collaborator

Yep! I think we should plan for one major iteration of the existing file operations now that we have a good way of comparing the performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants